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. Specifics of working with the API

Retry policy

DCM platform places a strong emphasis on the reliability and stability of its business processes. The retry policy is an integral part of the platform's architecture, ensuring transaction continuity even in cases of temporary disruptions among network participants. This mechanism aims to minimize the risk of data loss and maintain high service standards.

Algorithm of Operation The retry policy is activated when a participant responds with a non-2xx status. The DCM platform employs an optimized retry scheme with exponentially increasing intervals to avoid overloading the system:

  • Intervals Between Attempts: 1, 2, 4, 8, 16, 32 seconds, followed by 1 minute (repeated several times).

  • Maximum Number of Attempts: 10.

  • Upon receiving a successful response (2xx), processing continues in accordance with the approved business logic.

  • If, after 10 attempts, the response remains invalid or absent, the operation is automatically escalated for manual processing by Transparent Network staff.

Benefits of the Mechanism for Participants

  1. Merchants The mechanism ensures timely transmission of payment status information, enabling immediate order processing or identification of problematic transactions.

  2. Banks The retry policy reduces system load during outages and ensures data exchange stability.

  3. DCM platform The mechanism enhances trust in the platform and guarantees payment processing even under exceptional circumstances.

PreviousData encryptingNextDesign guide
⚙️
🪃