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:

• The cardholder’s data is input on the gateway side;
• The cardholder’s data is input on the online store side.

Inputting card data on the gateway side

Interaction flow

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

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.
18. 
    
    • 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.
19. The payment page redirects to the acsUrl with the parameter creq=packedCReq.
20. ACS displays the authentication page to the client ("challenge" page).
21. Client is authenticated.
22. ACS server verifies the authenticity of the authentication data.
23. Data is exchanged between the ACS and 3DS servers and processing result is confirmed.
24. The ACS server redirects the client to the store's page.
25. The online store sends finish3dsVer2Payment.do request to the Payment Gateway.
26. Payment Gateway sends the online store a response to the request made.
27. The online store sends getP2PStatus.do to the Payment Gateway to find out the order status.
28. Payment Gateway sends a response to the request made.
29. 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

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.

API calls

P2P integrations require API calls to be signed. Information about request signatures is available in our API Guide.

P2P order registration

To register an order for the card-to-card money transfer, use https://dev.bpcbt.com/payment/rest/api/p2p/registerP2P.do request.

When sending request, you should use header: Content-Type: application/json

Request parameters

Below are the parameters of the billingPayerData block (data about the client registration address).

Description of parameters in shippingPayerData object:

Description of parameters in preOrderPayerData object:

Description of parameters in orderPayerData object:

Response parameters

Examples

Request example

curl -X POST 'https://dev.bpcbt.com/payment/rest/api/p2p/registerP2P.do' 
   -H 'Content-Type: application/json' 
   --data-raw '{
  "username":"test_user",
  "password":"test_user_password",
  "amount" : 50000,
  "currency" : "978",
  "returnUrl" : "https://mybestmerchantreturnurl.com",
  "orderNumber": "1"
}'

Request example of AFT operation

curl -X POST 'https://dev.bpcbt.com/payment/rest/api/p2p/registerP2P.do'
-H 'Content-Type: application/json'
--data-raw '{
  "username":"test_user",
  "password":"test_user_password",
  "amount" : 50000,
  "currency" : "978",
  "returnUrl" : "https://mybestmerchantreturnurl.com",
  "orderNumber": "12",
  "clientId": "122313",
  "bindingId": "59aaf552-cdae-70de-a092-8f8c00a9fba0",
  "transactionTypeIndicator": "A",
  "features":{
      "feature":["FEATURE_1", "FEATURE_2", .. "FEATURE_N"]
   }
}'

Request example of OCT operation

curl -X POST 'https://dev.bpcbt.com/payment/rest/api/p2p/registerP2P.do'
-H 'Content-Type: application/json'
--data-raw '{
  "username":"test_user",
  "password":"test_user_password",
  "amount" : 50000,
  "currency" : "978",
  "returnUrl" : "https://mybestmerchantreturnurl.com",
  "orderNumber": "12",
  "clientId": "122313",
  "creditBindingId": "99ef0cee-34fe-7312-ad7c-78bc00b3236a",
  "transactionTypeIndicator": "A",
  "features":{
      "feature":["FEATURE_1", "FEATURE_2", .. "FEATURE_N"]
   }
}'

Response example

{
  "errorCode": 0,
  "errorMessage": "Successful",
  "orderId": "0a4eaae8-653a-71a9-8259-46fc00a8ea58",
  "formUrl": "https://dev.bpcbt.com/payment/merchants/ecom/payment.html?mdOrder=0a4eaae8-653a-71a9-8259-46fc00a8ea58&language=en",
  "orderNumber": "2009"
}

Fee amount

To obtain the fee amount for the money transfer, use https://dev.bpcbt.com/payment/rest/api/p2p/getP2PStatus.do request.

When sending request, you should use header: Content-Type: application/json

The structure of the verifyP2P.do request assumes the existence of the fromCard block to pass the attributes of the card to be debited and the toCard block to pass the attributes of the card to be credited.

Depending on the business processes of the bank and the online store, the following options are possible when carrying out a card-to-card money transfer:

• The online store passes the data of the card to be debited and of the card to be credited to the payment gateway. In this case both blocks of parameters — fromCard and toCard — must be presented in the request.
• If the money is transferred to the card by a third-party system, the online store passes only the data of the card to be debited to the payment gateway. In this case the request must include only one block of parameters — fromCard.
• If debiting is performed by a third-party system, the online store passes only the data of the card to be credited to the payment gateway. In this case the request must include only one block of parameters – toCard.

Request parameters

The fromCard block (if debiting is done by a third-party system, this block must be absent) includes the following possible parameters:

The toCard block (if crediting is done by a third-party system, this block must be absent) consists of the following possible parameters:

Response parameters

The feeDescriptionList block includes the following parameters:

Examples

Request example

curl -X POST 'https://dev.bpcbt.com/payment/rest/api/p2p/verifyP2P.do' -H 'Content-Type: application/json' --data-raw '{
  "username":"test_user",
  "password":"test_user_password",
  "orderId": "0a4eaae8-653a-71a9-8259-46fc00a8ea58",
  "fromCard": {
    "cardholderName": "TEST CARDHOLDER",
    "cvc": "123",
    "expirationMonth": 12,
    "expirationYear": 2030,
    "pan": "5000001111111115"
  },
  "toCard": {
    "pan": "4000001111111118"
  },    
  "amount" : 50000
}'

Response example

{
  "errorCode": 0,
  "errorMessage": "Successful",
  "feeDescriptionList: [ {
    "feeAmount": 500,
    "feeCurrency": "978",
    "feeDescription": "Acquirer fee"
  } ]
}

P2P transfer

To perform a card-to-card money transfer, use https://dev.bpcbt.com/payment/rest/api/p2p/performP2P.do request.

When sending request, you should use header: Content-Type: application/json

The structure of the performP2P.do request assumes the presence of the fromCard block to pass the attributes of the card to be debited and the toCard block to pass the attributes of the card to be credited. Depending on the business processes of the bank and the online store, the following options are possible when carrying out a card-to-card money transfer:

• The online store passes the data of the card to be debited and of the card to be credited to the payment gateway. In this case both blocks of parameters — fromCard and toCard — must be present in the request.
• If the money is transferred to the card by a third-party system, the online store passes only the data of the card to be debited to the payment gateway. In this case the request must include only one block of parameters — fromCard.
• If debiting is performed by a third-party system, the online store passes only the data on the card to be credited to the payment gateway. In this case the request must include only one block of parameters — toCard.

Request parameters

Below are the parameters of the billingPayerData block (data about the client registration address).

Description of parameters in shippingPayerData object:

Description of parameters in preOrderPayerData object:

Description of parameters in orderPayerData object:

The fromCard block (if debiting is done by a third-party system, this block must be absent) includes the following possible parameters:

When making payments using tokens (APPLE, SAMSUNG, GOOGLE), the fromCard block includes the following parameters instead of card details:

Below are the parameters of the threeDsAuthResult block (data related to 3 DS authentication).

The toCard block (if crediting is done by a third-party system, this block must be absent) consists of the following possible parameters:

Below are the parameters of the replacementData block (data used for replacement of the transfer destination in AFT transactions):

The following parameters are also passed during the authentication via the 3DS 2.0 protocol:

Response parameters

When authenticating via the 3DS 2.0 protocol, the following parameters are returned during the initial request:

Below are the parameters to be present in the response, after a repeated request for the payment and the need to redirect the client to the ACS during the authentication via the 3DS 2.0 protocol:

* Mandatory, if redirect to the ACS is needed.

Examples

Request example

Example of the first request:

curl -X POST 'https://dev.bpcbt.com/payment/rest/api/p2p/performP2P.do'
-H 'Content-Type: application/json'
--data-raw '{
  "username":"test_user",
  "password":"test_user_password",
  "orderId" : "38b7a9e0-7cfa-46f7-8655-f206a8898e7a",
  "amount" : 50000,
  "fromCard": {
    "vendor": "APPLE",
    "paymentToken": "eyJkZXZpY2VNYW51ZmFjdHVyZXJJZGVudGlmaWVyIjoiMDUwMTEwMDMwMjczIiwiY3VycmVuY3lDb2RlIjoiOTc4IiwiYXBwbGljYXRpb25FeHBpcmF0aW9uRGF0ZSI6IjI3MDEzMSIsInBheW1lbnREYXRhIjp7Im9ubGluZVBheW1lbnRDcnlwdG9ncmFtIjoiQUc5WW5Pak1YOUJXQUFSaElJOFBBb0FCRkE9PSJ9LCJwYXltZW50RGF0YVR5cGUiOiIzRFNlY3VyZSIsInRyYW5zYWN0aW9uQW1vdW50IjoxMDAsImFwcGxpY2F0aW9uUHJpbWFyeUFjY291bnROdW1iZXIiOiI1NTU1NTU1NTU1NTU1NTk5In0=",
    "decryptedToken":true,
    "protocolVersion":"ECv1"
  },
  "toCard" : {
    "pan" : "4111111111111111"
  },
  "params" : [
        {"name" : "recipientName", "Name" : "Surname"},
        {"name" : "payerName", "value" : "Name1 Surname1"},
        {"name" : "payerCity", "value" : "City"},
        {"name" : "payerCountry", "value" : "Country"},
        {"name" : "payerPostalCode", "value" : "777777"},
        {"name" : "payerState", "value" : "State"},
        {"name" : "payerAddress", "value" : "street, 18"
  },    
 ] 
}

Example of the second request:

curl -X POST 'https://dev.bpcbt.com/payment/rest/api/p2p/performP2P.do' -H 'Content-Type: application/json' --data-raw '{
  "username":"test_user",
  "password":"test_user_password",
  "orderId": "0a4eaae8-653a-71a9-8259-46fc00a8ea58",
  "fromCard": {
    "cardholderName": "TEST CARDHOLDER",
    "cvc": "123",
    "expirationMonth": 12,
    "expirationYear": 2030,
    "pan": "5000001111111115"
  },
  "toCard": {
    "pan": "4111111111111111"
  },    
  "amount" : 50000,
  "params" : [
        {"name" : "recipientName", "Name" : "Surname"},
        {"name" : "payerName", "value" : "Name1 Surname1"},
        {"name" : "payerCity", "value" : "City"},
        {"name" : "payerCountry", "value" : "Country"},
        {"name" : "payerPostalCode", "value" : "777777"},
        {"name" : "payerState", "value" : "State"},
        {"name" : "payerAddress", "value" : "street, 18"
  "threeDSServerTransId" : "3afc168a-94b4-4eb3-8e2e-80f6c186669d",
  "threeDSVer2FinishUrl" : "https://example.com/acs2/acs/3dsMethod"
}'

Response example

Example of the response to the first request:

{
  "errorCode": 0,
  "is3DSVer2": true,
  "threeDSServerTransId": "3afc168a-94b4-4eb3-8e2e-80f6c186669d",
  "threeDSMethodURL": "https://example.com/acs2/acs/3dsMethod",
  "threeDSMethodURLServer": "https://example.com/3dsserver/api/v1/client/gather?threeDSServerTransID=3afc168a-94b4-4eb3-8e2e-80f6c186669d",
  "threeDSMethodDataPacked": "eyJ0aHJlZURTTWV0aG9kTm90aWZpY2F0aW9uVVJMIjoiaHR0cHM6Ly9hY3F1aXJlci5jb20vM2Rzc2VydmVyL2FwaS92MS9hY3Mvbm90aWZpY2F0aW9uP3RocmVlRFNTZXJ2ZXJUcmFuc0lEPTNhZmMxNjhhLTk0YjQtNGViMy04ZTJlLTgwZjZjMTg2NjY5ZCIsInRocmVlRFNTZXJ2ZXJUcmFuc0lEIjoiM2FmYzE2OGEtOTRiNC00ZWIzLThlMmUtODBmNmMxODY2NjlkIn0="
}

Example of the response to the second request:

{
  "errorCode": 0,
  "info": "Your order is proceeded, redirecting...",
  "acsUrl": "https://example.com/acs2/acs/creq",
  "is3DSVer2": true,
  "packedCReq": "eyJ0aHJlZURTU2VydmVyVHJhbnNJRCI6IjNhZmMxNjhhLTk0YjQtNGViMy04ZTJlLTgwZjZjMTg2NjY5ZCIsIm1lc3NhZ2VUeXBlIjoiQ1JlcSIsIm1lc3NhZ2VWZXJzaW9uIjoiMi4xLjAiLCJhY3NUcmFuc0lEIjoiOWM3NTkxMmEtZTg0NC00ODgyLWI5YzctYzZmYmMzNjIyNGQ3IiwiY2hhbGxlbmdlV2luZG93U2l6ZSI6IjA1In0"
}

P2P transfer status

To obtain the status of a registered P2P order, use https://dev.bpcbt.com/payment/rest/api/p2p/getP2PStatus.do request.

When sending request, you should use header: Content-Type: application/json

Request parameters

Response parameters

Below are possible parameters of the operationList block.

Examples

Request example

curl -X POST 'https://dev.bpcbt.com/payment/rest/api/p2p/getP2PStatus.do' -H 'Content-Type: application/json' --data-raw '{ 
  "username": "test_user",
  "password": "test_user_password",
  "orderId" : "0a4eaae8-653a-71a9-8259-46fc00a8ea58"
}'

Response example

{
  "orderStatus": 0,
  "errorCode": 0,
  "errorMessage": "Successful",
  "orderNumber": "2009",
  "amount": 50000,
  "currency": "978",
  "creationDate": 1674137044330,
  "orderParams": [],
  "operationList": [],
  "resultCode": 0
}

Stored-credential P2P transfer

To perform a card-to-card transfer by binding, use https://dev.bpcbt.com/payment/rest/api/p2p/performP2PByBinding.do request.

When sending request, you should use header: Content-Type: application/json

Request parameters

The fromCard block (if debiting is done by a third-party system, this block must be absent) includes the following possible parameters:

The toCard block (if crediting is done by a third-party system, this block must be absent) consists of the following possible parameters:

Below are the parameters of the billingPayerData block (data about the client registration address).

Description of parameters in shippingPayerData object:

Description of parameters in preOrderPayerData object:

Description of parameters in orderPayerData object:

The following parameters are also passed during the authentication via the 3DS 2.0 protocol:

Response parameters

When authenticating via the 3DS 2.0 protocol, the following parameters are returned during the initial request:

Below are the parameters to be present in the response, after a repeated request for the payment and the need to redirect the client to the ACS during the authentication via the 3DS 2.0 protocol:

* Mandatory if the redirect to the ACS is needed.

Examples

Request example

curl -X POST 'https://dev.bpcbt.com/payment/rest/api/p2p/performP2PByBinding.do' 
-H 'Content-Type: application/json' 
--data-raw '{ 
  "amountInput" : 1000,
  "bindingId" : "03e9492a-536c-7ab4-85e6-b44000f26b04",
  "fromCard" : {
     "seToken": "ofVx1r3aIJ3Mlx3nkfeOIJgFOnwfsgFK+V6Yzm+KxJgsq19l74GChhX0We/LEFq78Rhn9uFAEZGdeyDhnIc/KfuvObf0EzoDA65Uj1Z8FjwWyjnEwTBHZL4KmdFBCSk8jLxHt70mXwyjiHYyCVH1fT/UVOnsrkZVGrqmEG4MTi5dX9Znzf24DwRg4iezvdT8vf0dUW5lJdvY1tgOsOnBulwy6kH/YbHVsnR6yxO6d6IsdnT5f8PxaB+7ZyUqgrd6VA88FGJKJgdoxk4721pqKSG5dYroLJG96s23EDJ2Hpi4e9wU2rP7E6dlFw+qzATqX/eaJbaQ9eakkdMWnkj7aQ=="
  },
  "toCard": {
        "cardholderName": "NAME SURNAME",
        "cvc": "123",
        "expirationMonth": 12,
        "expirationYear": 2024,
        "pan": "5555555555555599"
  },
  "orderId" : "3dbaf8bb-1d68-76b3-b4e6-784700f26b04",
  "password" : "test_user_password",
  "type" : "WITHOUT_TO_CARD",
  "username" : "test_user"
}'

Response example

{
  "errorCode" : 0,
  "errorMessage" : "Successful",
  "info" : "Your order is proceeded, redirecting...",
  "redirect" : "https://example.com/?orderId=47743354-be15-7c70-b9ef-4bfc482e68dc&lang=en",
  "is3DSVer2" : false
}

Request example with authentication via the 3DS 2.0 protocol

Example of the first request:

curl -X POST 'https://dev.bpcbt.com/payment/rest/api/p2p/performP2PByBinding.do' -H 'Content-Type: application/json' --data-raw '{ 
  "amountInput" : 1000,
  "currency" : "978",
  "fromCard" : {
    "bindingId" : "fd3afc57-c6d0-4e08-aaef-1b7cfeb093dc"
  },
  "orderId" : "38b7a9e0-7cfa-46f7-8655-f206a8898e7a",
  "password" : "test_user_password",
  "type" : "WITHOUT_TO_CARD",
  "username" : "test_user",
  "params" : {
    "name" : "payerAddress",
    "value" : "payer Address"
  }
}'

Example of the second request:

curl -X POST 'https://dev.bpcbt.com/payment/rest/api/p2p/performP2PByBinding.do' -H 'Content-Type: application/json' --data-raw '{ 
  "amountInput" : 1000,
  "currency" : "978",
  "fromCard" : {
    "bindingId" : "fd3afc57-c6d0-4e08-aaef-1b7cfeb093dc"
  },
  "orderId" : "38b7a9e0-7cfa-46f7-8655-f206a8898e7a",
  "password" : "test_user_password",
  "type" : "WITHOUT_TO_CARD",
  "username" : "test_user",
  "params" : {
    "name" : "payerAddress",
    "value" : "payer Address"
  },
  "threeDSServerTransId" : "f44d6d21-1874-45a5-aeb0-1c710dd6e134",
  "threeDSVer2FinishUrl" : "https://example.com/acs2/acs/3dsMethod"
}'

Response example with authentication via the 3DS 2.0 protocol

Example of the response to the first request:

{
  "errorCode": 0,
  "is3DSVer2": true,
  "threeDSServerTransId": "f44d6d21-1874-45a5-aeb0-1c710dd6e134",
  "threeDSMethodURLServer": "https://example.com/3dsserver/api/v1/client/gather?threeDSServerTransID=f44d6d21-1874-45a5-aeb0-1c710dd6e134",
}

Example of the response to the second request:

{
  "errorCode": 0,
  "info": "Your order is proceeded, redirecting...",
  "acsUrl": "https://example.com/acs2/acs/creq",
  "is3DSVer2": true,
  "packedCReq" : "eyJ0aHJlZURTU2VydmVyVHJhbnNJRCI6IjVmMzEyMjdlLTljZmQtNDQwYi1hNDNjLTE4NjljMzNhNGI5YiIsImFjc1RyYW5zSUQiOiI5YTQyYzQ4ZC1hNWRiLTQ3NjEtYmI4Mi05ZmY5MmM0NzZiM2QiLCJjaGFsbGVuZ2VXaW5kb3dTaXplIjoiMDQiLCJtZXNzYWdlVHlwZSI6IkNSZXEiLCJtZXNzYWdlVmVyc2lvbiI6IjIuMS4wIn0="
}

Stored-credential P2P fee amount

To get the amount of commission when transferring funds by a stored-credential transaction, use the https://dev.bpcbt.com/payment/rest/api/p2p/verifyP2PByBinding.do request.

When sending request, you should use header: Content-Type: application/json

Request parameters

The fromCard block (if debiting is done by a third-party system, this block must be absent) includes the following possible parameters:

The toCard block (if crediting is done by a third-party system, this block must be absent) consists of the following possible parameters:

Response parameters

Examples

Request example

curl --location --request POST 'https://dev.bpcbt.com/payment/rest/api/p2p/verifyP2PByBinding.do' \
--header 'Content-Type: application/json' \
--data-raw '{
    "username": "test_user",
    "password": "test_user_password",
    "orderId": "fa71bf70-7c81-484e-a6fc-7db7e4283b2a",
    "bindingId": "4d792471-cee0-742c-922d-a265072e6148",
    "fromCard": {
        "seToken": "ofVx1r3aIJ3Mlx3nkfeOIJgFOnwfsgFK+V6Yzm+KxJgsq19l74GChhX0We/LEFq78Rhn9uFAEZGdeyDhnIc/KfuvObf0EzoDA65Uj1Z8FjwWyjnEwTBHZL4KmdFBCSk8jLxHt70mXwyjiHYyCVH1fT/UVOnsrkZVGrqmEG4MTi5dX9Znzf24DwRg4iezvdT8vf0dUW5lJdvY1tgOsOnBulwy6kH/YbHVsnR6yxO6d6IsdnT5f8PxaB+7ZyUqgrd6VA88FGJKJgdoxk4721pqKSG5dYroLJG96s23EDJ2Hpi4e9wU2rP7E6dlFw+qzATqX/eaJbaQ9eakkdMWnkj7aQ=="
    },
    "toCard": {
        "cardholderName": "NAME SURNAME",
        "cvc": "123",
        "expirationMonth": 12,
        "expirationYear": 2024,
        "pan": "5555555555555599"
    },
    "amount": 1000,
    "currency": "978",
    "clientId": "123",
}'

Response example

{
  "errorCode" : 0,
  "errorMessage" : "Successful",
  "feeDescriptionList" : [ {
    "feeAmount" : 10,
    "feeCurrency" : "978",
    "feeDescription" : "Acquirer fee"
  } ]
}