NAV

For any question, we are one click away

Contact us

P2P solution

P2P transaction

P2P functionality helps you to provide users (current or potential customers) with the ability to send money to each other, also it allows you to accept transfers to your cards without sending your data to anyone and earn commissions by providing a service to a wide range of users.

The P2P service is a service available for customization and integration into third-party websites, mobile applications, as well as Internet and mobile banks.

Users have access to a complete list of operations, sending/receiving transfers, registering/authorizing in the service, managing saved cards.

An important feature of the P2P service is the ability to make transfers by phone number, even if the user is not yet registered in the system.

P2P transaction flow can be displayed in the following main scenarios:

Inputting card data on the gateway side

Interaction flow

sequenceDiagram participant C as Client participant OS as Online store participant PG as Payment Gateway participant ACS as ACS C ->> OS: 1. Forming an Order OS ->> PG: 2. Registering the Order PG -->> OS: 3. orderId, formUrl OS -->> C: 4. Redirecting to the card data collection form C ->> PG: 5. Receiving the card data collection form PG -->> C: 6. The card data collection form C ->> PG: 7. Sending the data in the filled in form PG ->> PG: 8. Checking if the card belongs to 3-D secure PG -->> C: 9. Redirecting the client to ACS C ->> ACS: 10. Receiving the authorization form ACS -->> C: 11. The authorization form C ->> ACS: 12. Filling in the form ACS -->> C: 13. Redirecting the client to the Payment Gateway C ->> PG: 14. Completing the secure payment PG ->> PG: 15. Making the payment PG -->> C: 16. Redirecting the client to the online store C ->> OS: 17. Getting the page with the result OS ->> PG: 18. Checking the status PG -->> OS: 19. Status of the Order OS -->> C: 20. Showing the result
  1. On the merchant's site (e.g. an online store) a cardholder requests to perform a P2P money transfer.
  2. The online store system registers the order in the Payment Gateway via registerP2P.do. The registration parameters used include the amount of the transfer, the currency, the order number in the merchant's system, and the return URL for the client.
  3. In response to the registration request, the Payment Gateway returns a unique identifier of the order in the payment system and the URL to redirect the client to the form for card data collection.
  4. The online store system passes the redirect URL received on step 3 to the client’s Web browser.
  5. The client’s Web browser opens the URL.
  6. At the specified URL, the client’s Web browser receives the form for card data collection.
  7. Client fills in the form and the data is sent to the Payment Gateway server.
  8. The system checks if the card belongs to 3-D Secure (SecureCode).
  9. The Gateway sends the redirect link to the Access Control Server (ACS) page of the issuing bank to the client’s Web browser (this step is necessary for the implementation of 3DS).
  10. The client’s Web browser requests the user authorization form from ACS.
  11. ACS sends the authorization form to the client’s Web browser.
  12. Client fills in the form and the information is sent to ACS.
  13. ACS processes the form and, regardless of the result, sends the redirect URL of the pages of the Payment Gateway to the client’s Web browser. The encrypted parameters of the authorization result are sent together with this URL.
  14. The client’s Web browser requests the Payment Gateway page when passing the encrypted parameters of the authorization result.
  15. Payment Gateway transfers the money.
  16. When the money is transferred, the Payment Gateway sends the return URL to the client’s Web browser (the URL was specified during the registration of the order by the online store on step 2).
  17. The client’s Web browser requests the results of the money transfer from the online store.
  18. The online store system requests the information about the order status from the payment gateway - getP2PStatus.do.
  19. Payment Gateway returns the status of the order.
  20. The online store system shows payment result to client.

Inputting card data on the online store side

Interaction flow

sequenceDiagram participant C as Client participant OS as Online store participant PG as Payment Gateway participant 3DSS as 3DS Server participant ACS as ACS C ->> OS: 1. Forming an Order OS ->> PG: 2. Registering the Order PG -->> OS: 3. Response to order registration OS -->> C: 4. Redirecting to the card data collection form C ->> OS: 5. Submitting the data OS ->> PG: 6. Requesting the fee amount PG -->> OS: 7. Receiving the fee amount OS ->> PG: 8. Request for a card-to-card transfer PG -> 3DSS: 9. Checking 3DSv2 availability PG -->> OS: 10. Response to the request for card-to-card transfer OS ->> 3DSS: 11. Calling a hidden iframe (threeDSMethodURLServer) opt [if threeDSMethodURL is in response] OS ->> ACS: 12. Calling a hidden iframe (threeDSMethodURL) end OS ->> PG: 13. Second request for transfer of funds PG ->> 3DSS: 14. Authentication request 3DSS ->> ACS: 15. Authentication request ACS -->> 3DSS: 16. Response to the authentication request 3DSS -->> PG: 17. Response to the authentication request PG -->> OS: 18. Response to the second order payment request opt [Redirection to ACS is required] OS ->> ACS: 19. CReq (ChallengeRequest) ACS -->> C: 20. HTML form to pass authentication C ->> ACS: 21. Confirmation of authenticity ACS ->> ACS: 22. Data processing ACS -> 3DSS: 23. Data exchange ACS -->> C: 24. Result of data processing and redirecting the client to the store page OS ->> PG: 25. finishThreeDsVer2.do PG -->> OS: 26. Response to the request end OS ->> PG: 27. Order status request PG -->> OS: 28. Response to the order status request OS -->> C: 29. Showing the result
  1. A cardholder (client) interacts with the online store to create an order.
  2. The online store system registers the order in the Payment Gateway via registerP2P.do. The registration parameters used include the amount of the transfer, the currency, the order number in the merchant's system, and the return URL for the client.
  3. In response to the registration request, the Payment Gateway returns a unique identifier of the order in the payment system and the URL to redirect the client to the form for card data collection.
  4. The online store system passes the redirect URL received on step 3 to the client’s Web browser.
  5. Client fills in the form and submits the data.
  6. Optional. If the online store works with the fees, the online store sends to the Payment Gateway a request for the fee sum via verifyP2P.do / verifyP2PByBinding.do.
  7. Optional. Payment Gateway sends in response the fee amount.
  8. The online store sends a request for transfer of funds to the Payment Gateway via performP2P.do / performP2PByBinding.do.
    At this stage, the 3DS 2.0 operation is initiated.
  9. Payment Gateway checks on the 3DS server whether the client can authenticate using the 2.0 Protocol.
  10. Payment Gateway sends a response to the request made in the step 6. The response also returns the following parameters:
    • is3DSVer2 - 3DSv2 authentication capability flag (true/false)
    • threeDSServerTransId - transaction identifier assigned by the 3DS server
    • threeDSMethodURLServer - address of the 3DS server for collecting browser data
    • threeDSMethodURL - (optional) address of the ACS server for collecting browser data
    • threeDSMethodDataPacked - (optional) data for collecting browser data on ACS

    (See also request description).
  11. The online store calls threeDSMethodURLServer, in a separate "iframe" with the help of the POST method, using the value received from the response to the request for transfer of funds. This allows the 3DS server to collect data about the customer's browser.
  12. Optional step. If threeDSMethodURL and threeDSMethodDataPacked parameters were received in the response to the request for transfer of funds, the online store calls threeDSMethodURL in a separate iframe using the POST method.
  13. Transfer of funds - stage 2. The online store resends the request to make money transfer via performP2P.do / performP2PByBinding.do.
    You must pass threeDSServerTransId parameter - transaction identifier which was created by the 3DS server and returned in the step 10.
  14. Payment Gateway sends an authentication request to the 3DS server.
  15. 3DS server sends an authentication request (AReq) to the ACS server.
  16. ACS server sends an authentication request (ARes) response to the 3DS server.
  17. 3DS server sends the received data to the Payment Gateway.

    • If the client does not need to authenticate to the ACS, the Payment Gateway returns a response to the request for transfer of funds. In this case, go to the step 27 of this flow.
    • If the client needs to authenticate to the ACS, the Payment Gateway will send a response to the payment page with the data of redirection to the ACS.
  18. The payment page redirects to the acsUrl with the parameter creq=packedCReq.
  19. ACS displays the authentication page to the client ("challenge" page).
  20. Client is authenticated.
  21. ACS server verifies the authenticity of the authentication data.
  22. Data is exchanged between the ACS and 3DS servers and processing result is confirmed.
  23. The ACS server redirects the client to the store's page.
  24. The online store sends finishThreeDsVer2.do request to the Payment Gateway.
  25. Payment Gateway sends the online store a response to the request made.
  26. The online store sends getP2PStatus.do to the Payment Gateway to find out the order status.
  27. Payment Gateway sends a response to the request made.
  28. The online store displays the result page to the client.

AFT transaction

AFT (Account Funding Transaction) - a special type of operations for debiting of funds for the purpose of replenishing the client's internal account in the merchant’s system or banking account in bank’s system (often used as an alternative to the purchase operation).

AFT transaction flow scenario is the same as for P2P transaction. The difference is that only data of the card to be debited is specified in AFT transaction.

OCT transaction

OCT (Original Credit Transaction) - a special type of transactions for crediting funds to the recipient in real time.

Interaction flow

sequenceDiagram participant C as Client participant OS as Online store participant PG as Payment Gateway C ->> OS: 1. Forming an Order OS ->> PG: 2. Registering the Order PG -->> OS: 3. orderId, formUrl OS -->> C: 4. Redirecting to the card data collection form C ->> PG: 5. Sending the data in the filled in form PG ->> PG: 6. Transfer of funds PG -->> C: 7. Redirecting the client to the online store C ->> OS: 8. Getting the page with the result OS ->> PG: 9. Checking the status PG -->> OS: 10. Status of the Order OS -->> C: 11. Showing the result
  1. A cardholder (client) interacts with the online store to create an order.
  2. The online store system registers the order in the Payment Gateway via registerP2P.do. The registration parameters used include the amount of the transfer, the currency, the order number in the merchant's system, and the return URL for the client.
  3. In response to the registration request, the Payment Gateway returns a unique identifier of the order in the payment system and the URL to redirect the client to the form for card data collection.
  4. The online store system passes the redirect URL received on step 3 to the client’s Web browser.
  5. Client fills in the form and the data is sent to the Payment Gateway server.
  6. Payment Gateway makes the transfer of funds via performP2P.do.
  7. When the money is transferred, the Payment Gateway sends the return URL to the client’s Web browser (the URL was specified during the registration of the order by the online store on step 2).
  8. The client’s Web browser requests the results of the money transfer from the online store.
  9. The online store system requests the information about the order status from the payment gateway - getP2PStatus.do.
  10. Payment Gateway returns the status of the order.
  11. The online store system shows payment result to the client.
Categories
Search results