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. Merchant
  2. E-commerce
  3. Order

Order status

The DCM platform provides the ability to obtain information about the status of an order using a GET request.

Endpoint

{{url_host}}/api/v1/merchants/order/status?id={{order_id}}

The {url_host} of the DCM platform provided during integration is used.

The value of {url_host} differs between testing and production environments.

Response 200 (example)

{
    "amount": 11,
    "amount_matched": true,
    "callback_guid": null,
    "code": null,
    "currency": "UAH",
    "order_id": "aec38a4d-4adb-4b31-8edf-aea9f907e2e7",
    "payment_message_external_id": "",
    "payment_message_guid": "fff5eb70-9d2f-4f14-b064-fd8715d07a67",
    "purpose": "yar2prp75776557384",
    "reason": "Order is paid",
    "receiver_account_iban": "",
    "ref_found": null,
    "ref_number": "yar2ref34234654",
    "sender_account_iban": "",
    "status": "Success"
}

Response 400

{

}

Order Statuses in DCM platform:

  • Created: The order has been successfully created.

  • In Progress: A 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.

PreviousEmittersNextСallback "Pay-in"
🏢
🏪
📦
📬