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

DCM platform's artifacts

The following key artefacts are formed in the process of implementing the DCM platform business flow:

1. Order

The Merchant creates an order after a customer selects a product or service on a website or at a physical point of sale and chooses to pay via the DCM platform. The order is initiated using the POST/create_merchant’s_order method.

Order Statuses:

  • Created: The order has been successfully created.

  • In Progress: Payment message with an assigned GUID has been successfully generated for the order.

  • Success: DCM platform has received confirmations from all participants (Initiating Bank, Receiving Bank, and Merchant) verifying that the order can be fulfilled.

  • Canceled: The order is automatically canceled once its validity period expires.

2. Payment message

Payment message is generated by the Initiating Bank after the customer confirms payment for the order.

Payment Message Statuses:

  • Pending: The payment message is in the process of being completed.

  • Success: The payment message has been successfully completed.

  • Reject: The payment process for the message has failed.

3. Gross settlement register

Gross settlement register is generated daily by DCM platform at 12:01 AM local time and includes all successful payment messages from the previous day.

Register Statuses:

  • Sent: Assigned to registers containing interbank payment messages after they’ve been sent to the Initiating Bank and Receiving Bank.

  • Sent (no PM): Used for registers that don’t include any payment messages after being sent.

  • Sent (Interbank): Assigned to registers containing intrabank payment messages after their dispatch.

  • Processing: Assigned to register with interbank payment messages once confirmation of payment is received via the local payment system.

  • Paid: Assigned to registers with either interbank or intrabank payment messages after funds have been successfully transferred.

PreviousDesign guideNextPreparing for integration

Last updated 1 month ago

🗂️