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. p2p transfers

p2p by phone number

Previousp2p transfersNextp2p order (to pay)

Last updated 3 months ago

The payment by phone number is initiated by the client using the functionality of the initiating bank's mobile application. The client can choose the recipient's phone number from their "Contacts" or enter it manually.

After the client confirms the entered details, the initiating bank contacts the DCM platform to create a payment order.

Based on the order, the DCM platform queries the alias database to find the recipient by phone number:

If the alias is in the database

  • The DCM platform sends a request to the recipient's bank to obtain encrypted data about the recipient.

  • The obtained data is transmitted to the initiating bank, which decrypts it and displays limited information about the recipient to the payer for payment confirmation.

  • After verifying the payment parameters and debiting (or blocking) funds from the client's account, the initiating bank sends a payment notification to the DCM platform.

  • The DCM platform validates the accuracy of the notification data and generates a "pay-in" callback to the recipient's bank with payment details.

  • The recipient's bank validates and confirms the successful processing of the callback and credits the recipient's account.

  • The initiating bank receives the final "pay-out" callback, which allows it to generate a payment instruction for the final settlement of funds.

If the alias is not in the database

  • The DCM platform sends a request to participating banks to check the number in their customer database. If the client is not found, the banks notify the DCM platform accordingly.

  • If the number is found, the recipient's bank notifies the DCM platform and initiates a request in the client's mobile application to confirm the use of this number for receiving P2P payments.

  • If the client agrees, the bank notifies the DCM platform.

  • Based on the received confirmation, the phone number and IBAN are added to the alias database. The subsequent process proceeds in the same way as for an alias that is already in the database.

As mentioned above, the DCM platform provides the capability to exchange payment information. The actual movement of funds between banks is carried out through the existing internal banking instrument. Banks that are registered participants of the DCM platform receive real-time payment notifications.

The main integration points for the bank are shown below:

  • POST/p2p_order

  • Callback "Pay_request"

  • POST/Payment-message

  • Callback "Pay-out" Depending on the clearing model:

  • Callback "Gross_Settlement" (optional)

  • GET/Gross_settlement_list

  • GET/Gross_settlement_by_id

  • POST/Gross_settlement_pay

  • POST/Gross_settlement_confirm

  • POST/link_creditor

  • Callback "Linked_creditor"

  • GET/creditor's_data

  • Callback "Pay-in" Depending on the clearing model:

  • Callback "Gross_Settlement"(optional)

  • GET/Gross_settlement_list

  • GET/Gross_settlement_by_id

When integrating the two roles, it is additionally necessary to integrate the method:

  • POST/Gross_settlement_confirm_internal

🏦
💸
📲
313KB
TPN e2e p2p phone.drawio.png
image