DCM Platform Guide
  • 🌐DCM platform
  • ⚙️Specifics of working with the API
    • 🔐Security stack
    • 🔑Key Generation
    • 🔐Data encrypting
    • 🪃Retry policy
  • 🎨Design guide
  • 🗂️DCM platform's artifacts
  • 🏦Bank
    • 📋Preparing for integration
    • 🏪E-commerce
      • 📦Order and payment
      • 📨Payment message
        • 1️⃣Validation
        • 2️⃣Сallback 1 “Pay-in”
        • 3️⃣Callback 3 “Pay-out”
        • 4️⃣Callback 4 "Credit callback"
      • 🎯Testing
      • 🖇️Merchant Onboarding
      • ⛔Error reference guide
    • 🗃️Alias database
      • 🗝️Adding alias
      • ↕️"Сallback "Alias updated"
      • ☑️Get alias status
    • 💸p2p transfers
      • 📲p2p by phone number
        • ⏺️p2p order (to pay)
        • 🔍Receiver search
        • 🗂️Get receiver's data
        • ⏪Callback "Pay request"
      • 🖇️p2p by deeplink or QR code
        • ⏺️p2p order (to request)
        • Pay request initiation
      • 📨Payment message
        • 1️⃣Validation
        • 2️⃣Сallback “Pay-in”
        • 3️⃣Callback "Pay-out"
    • 💲Gross settlement
      • 1️⃣Callback “Gross_Settlement”
      • 2️⃣Gross_settlement_list
      • 3️⃣Gross_settlement_by_id
      • 4️⃣Gross_settlement_pay
      • 5️⃣Gross_settlement_confirm
      • 6️⃣Gross_settlement_confirm_internal
      • 📧Email notification
    • ✔️Reconciliation
  • 🏢Merchant
    • 🏫DCM platform for Merchants
      • 🔠Integration options
    • 👨‍🏫Preparing for integration
      • ⚙️Working with the API
      • 🔑Key Generation
      • 🖥️Updating interfaces
    • 🏪E-commerce
      • 📦Order
        • 💵Payment through the DCM platform
        • 💳Payment on the Merchant's website
        • 📋Emitters
        • 📬Order status
      • 1️⃣Сallback "Pay-in"
  • 📑Document data
    • 🆕Version history
    • 📃Change log
Powered by GitBook
On this page
  1. Bank
  2. Gross settlement

Gross_settlement_list

PreviousCallback “Gross_Settlement”NextGross_settlement_by_id

Last updated 3 months ago

The GET/gross_settlement_list method retrieves a list of all gross settlement registers where the bank acts as the Initiating Bank. The response can be customized using query parameters.

Endpoint:

Query parameters:

  • offset: The starting position in the list of registers for the response.

  • limit: The number of registers to include in the response.

  • period: The time range during which the registers were created. If this parameter is not provided, the information for the last 7 calendar days is displayed.

Dates and times are transmitted in the RFC3339 ISO 8601 standard, including the time zone.

Example: 2024-09-03T23:59:59Z03:00

For URL encoding purposes, the plus sign (+) is noted as %2B.

  • role: The role of the requesting bank with the following options:

    • All - Includes registers where the requesting bank is both the Initiating Bank and the Receiving Bank.

    • Debtor - Includes registers where the requesting bank is the Initiating Bank.

Response

{
    "id": "STRING REGISTER_ID ddmmyy+increment_id", - Register ID
    "debtor_bic": "string", -  code of the paying bank
    "debtor_name": "string", -  Name of the paying bank
    "creditor_bic": "string", -  code of the receiving bank
    "creditor_name": "string", -  Name of the receiving bank
    "creditor_code": "string", - tax code of the receiving bank
    "charging_account": "string", - IBAN of the receiving bank for gross payments
    "purpose": "string", - Payment purpose
    "period_start": "date", - Start date of the register period
    "period_end": "date", - End date of the register period
    "total_amount": "string", - Total register amount
    "total_amount_to_pay": "string", - Total amount to be paid
    "total_fee_amount": "string", - Total fee amount
    "currency": "string", - Register currency
    "status": "enum", -  Register status
    "created_at": "date", -  Register creation date and time
    "updated_at": "date", - Register update date and time
    "deleted_at": "date" - Register deletion date and time
}

Status Reference:

  • Sent: The register has been sent to the bank.

  • Sent (no PM): An "empty" register (no payment messages) has been sent to the bank.

  • Sent (Interbank): An "internal" register (where the Initiating Bank and Receiving Bank are the same institution) has been sent to the bank.

  • Processing: Payment for the gross settlement register has been sent to the local payment rails (pacs.008).

  • Paid: Payment for the gross settlement register has been successfully processed via local payment rails (pacs.002) or funds have been transferred for internal registers.

🏦
💲
2️⃣
https://{bank-gateway-address.dcmapis.com}:443/api/v1/counterparty/{counterparty_guid}/gross-settlement?offset={offset}&limit={limit}&from=yyyy-mm-ddT00:00:00Z03&to=yyyy-mm-ddT23:59:59Z03:00&role={role}
https://datatracker.ietf.org/doc/html/rfc3339