3.5. P2P transfer operations
This page contains a description of the operations of P2P transfers of the Procard.Pay dispatch system
P2P transfer operations include:
P2PCredit - direct crediting of funds to the card
P2PDebit - direct withdrawal of funds from the card
P2Pin - transfer operation from card to card (on the payment processing page)
P2PTransfer - transfer operation from card to card (card data is provided by the merchant)
GetBalance - getting information about the balance of under-limit transactions
Operation P2PCredit
Test url https://pay-test.procard-ltd.com/api (the client receives the production url in the project log)
To replenish the card, send a POST request with the following parameters:
На этой странице:
Parameter | Description | Value |
|---|---|---|
operation | Type of transaction | P2PCredit |
merchant_id | Merchant ID |
|
order_id | This is a unique transaction number. Generated on the side of the merchant. It must be unique throughout the work. |
|
amount | Transaction amount | Example: 100.50 |
card_number | The recipient's card number. |
|
token | Token, can be used instead of the recipient's card |
|
currency_iso | Transaction currency. | Example: UAH |
add_params [SenderAccount] | Unique number of the electronic wallet / account of the payer |
|
add_params [SenderName] | Data enabling the identification of the person who contracted the beneficiary to supply goods, perform work, provide services, provide credit The name of the payer |
|
add_params [ResidentCountry] | Place of residence of the payer
|
|
add_params [SenderPostalCode] | Place of residence of the payer |
|
add_params [ResidentCityInLatin] | Place of residence of the payer |
|
add_params [Address] | Place of residence of the payer |
|
add_params [passportNumber] | Payer's passport number |
|
add_params [identityNumber] | TIN of the payer |
|
add_params [SenderBirthday] | Date of birth of the payer |
|
add_params [SenderBirth\_locality] | Place of birth of the payer |
|
add_params [SenderName] | Full name of the payer |
|
add_params [ResidentCountry] | Location of the payer |
|
add_params [SenderPostalCode] | Location of the payer |
|
add_params [ResidentCityInLatin] | Location of the payer |
|
add_params [Address] | Location of the payer |
|
add_params [RecipientAccount] | Unique number of the recipient's e-wallet / account |
|
add_params [Descript] | Purpose of payment |
|
[RecipientName] | Name of the recipient |
|
add_params [RecipientName] | Full name of the recipient |
|
add_params [PayerAccount] | Unique number of the electronic payment instrument of the payer |
|
add_params [VisaPurchaseIdentifier] | Visa Request to Pay ID |
|
visa_alias | Instead of a card or token, VisaAlias can be specified | Example (phone number): |
visa_alias_type | Alias type. Required if visa_alias is specified |
|
signature | In order to confirm the validity of the data, a verification signature must be generated and transmitted in the SHA-512 request using the Merchant's private_key. |
|
| A string subject to SHA-512 is generated by concatenating merchant_id, order_id, amount, card_number, currency_iso parameters separated by “;” (semicolon) in UTF-8 encoding. |
|
| The order of the parameters when concatenating is important! |
|
The response is JSON with the following parameters:
Parameter | Description | Value |
|---|---|---|
code | Response code. (See below for a list of response codes) | Code: 0 - successful |
message | Text message with query result |
|
status | Transaction Statuses |
|
| APPROVED - transaction successful |
|
| DECLINED - transaction failed |
|
| ON-PAYMENT - Application for transfer is being processed, you must additionally request the status |
|
transactionID | Transaction ID in the payment system |
|
approvalCode | Authorization code |
|
Success response example:
{
"code":0,
"message":"OK",
"status":"APPROVED",
"transactionID":"2814211",
"approvalCode":"371623 A"
}"status":"APPROVED" - means that the operation was completed successfully
Request failure response example:
{
"code":-4,
"message":"Неверная подпись"
}Operation failure response example:
{
"code":12,
"message":58,
"status":"DECLINED"
}58 - operation failure code. The list of codes can be found in 4.2. Response code reference
Operation P2PDebit
Test url https://pay-test.procard-ltd.com/api (the client receives the production url in the project log)
To debit funds from the card, the user must be redirected to the payment gateway page using the POST method with the following parameters:
Parameter | Description | Value |
|---|---|---|
operation | Type of transaction | P2PDebit |
merchant_id | Merchant ID |
|
order_id | This is a unique transaction number. Generated on the side of the merchant. It must be unique throughout the work. |
|
amount | Transaction amount | Example: 100.50 |
currency_iso | Transaction currency. Currently available only “UAH” |
|
description | Purpose of payment |
|
approve_url | The URL to which the user will be redirected in case of a successful operation |
|
decline_url | The URL to which the user will be redirected in case of an unsuccessful operation |
|
cancel_url | The URL to which the user will be redirected if the operation is canceled |
|
add_params [SenderAccount] | Unique number of the electronic wallet / account of the payer |
|
add_params [SenderName] | Data enabling the identification of the person who contracted the beneficiary to supply goods, perform work, provide services, provide credit The name of the payer |
|
add_params [ResidentCountry] | Place of residence of the payer
|
|
add_params [SenderPostalCode] | Place of residence of the payer |
|
add_params [ResidentCityInLatin] | Place of residence of the payer |
|
add_params [Address] | Place of residence of the payer |
|
add_params [passportNumber] | Payer's passport number |
|
add_params [identityNumber] | TIN of the payer |
|
add_params [SenderBirthday] | Date of birth of the payer |
|
add_params [SenderBirth\_locality] | Place of birth of the payer |
|
add_params [SenderName] | Full name of the payer |
|
add_params [ResidentCountry] | Location of the payer |
|
add_params [SenderPostalCode] | Location of the payer |
|
add_params [ResidentCityInLatin] | Location of the payer |
|
add_params [Address] | Location of the payer |
|
add_params [RecipientAccount] | Unique number of the recipient's e-wallet / account |
|
add_params [Descript] | Purpose of payment |
|
[RecipientName] | Name of the recipient |
|
add_params [RecipientName] | Full name of the recipient |
|
add_params [PayerAccount] | Unique number of the electronic payment instrument of the payer |
|
signature | In order to confirm the validity of the data, a verification signature must be generated and transmitted in the SHA-512 request using the Merchant's private_key. |
|
| A string subject to SHA-512 is generated by concatenating merchant_id, order_id, amount, currency_iso, description, approve_url, decline_url, cancel_url parameters separated by “;” (semicolon) in UTF-8 encoding. |
|
| The order of the parameters when concatenating is important! |
|
Operation P2Pin
This operation is used to carry out a transfer by the client on the processing page.
Test url https://pay-test.procard-ltd.com/api (the client receives the production url in the project log)
To replenish the card, send a POST request with the following parameters:
Parameter | Description | Value |
|---|---|---|
operation | Type of transaction | P2Pin |
merchant_id | Merchant ID |
|
currency_iso | Transaction currency. | UAH |
amount | Transaction amount | Example: 100.50 |
order_id | This is a unique transaction number. Generated on the side of the merchant. It must be unique throughout the work. |
|
card_number2 | Recipient's card number |
|
token2 | Token, can be used instead of the recipient's card |
|
signature | In order to confirm the validity of the data, a verification signature must be generated and transmitted in the SHA-512 request using the Merchant's private_key. A string subject to SHA-512 is generated by concatenating merchant_id, order_id, amount, currency_iso, description, approve_url, decline_url, cancel_url parameters separated by “;” (semicolon) in UTF-8 encoding. The order of the parameters when concatenating is important! |
|
description | Purpose of payment. Displayed on the payment page when you enter payment details. Displayed on account statements and registers |
|
add_params | An array with additional parameters. Additional parameters are then returned to the merchant in the callback call |
|
approve_url | URL to redirect if payment is successful |
|
decline_url | URL to redirect in case the payment is unsuccessful |
|
cancel_url | URL for redirection if the user refuses to make a payment |
|
callback_url | URL to which information about the result of the payment will be sent |
|
short_link | Receive a short link in response |
|
secure_type | Transaction security pass type |
|
lifetime | Payment link lifetime in seconds (If the parameter is not passed, then 15 minutes) |
|
language | Payment page language |
|
Example request:
Example success response:
Example of a failure response:
Operation P2PTransfer
This operation is used to carry out a transfer by the client on the merchant page with transfering card data to processing API.
Test url https://pay-test.procard-ltd.com/api (the client receives the production url in the project log)
To replenish the card, send a POST request with the following parameters:
Parameter | Description | Value |
|---|---|---|
operation | Type of transaction | P2PiTransfer |
merchant_id | Merchant ID |
|
currency_iso | Transaction currency. | UAH |
amount | Transaction amount | Example: 100.50 |
order_id | This is a unique transaction number. Generated on the side of the merchant. It must be unique throughout the work. |
|
card_number1 | Sender's card number |
|
card_number2 | Recipient's card number |
|
card_exp_m | Validity period of the sender's card MM |
|
card_exp_y | Validity period of the sender's card YY |
|
signature | In order to confirm the validity of the data, a verification signature must be generated and transmitted in the HMAC_MD5 request using the Merchant's private_key. A string subject to HMAC_MD5 is generated by concatenating merchant_id, order_id, amount, card_number, currency_iso, card_number2 parameters separated by “;” (semicolon) in UTF-8 encoding. The order of the parameters when concatenating is important! |
|
description | Purpose of payment. Displayed on the payment page when you enter payment details. Displayed on account statements and registers |
|
add_params | An array with additional parameters. Additional parameters are then returned to the merchant in the callback call |
|
callback_url | URL to which information about the result of the payment will be sent |
|
Example request:
Example success response:
Example of a failure response:
GetBalance operation
Test url https://pay-test.procard-ltd.com/api/balance (the client receives the production url in the project log)
To get information about the balance, you need to send a POST request with the following parameters:
Parameter | Description | Value |
|---|---|---|
operation | Type of transaction | GetBalance |
merchant_id | Merchant ID |
|
date | Date and time of the request in a custom format |
|
signature | In order to confirm the validity of the data, a verification signature must be generated and transmitted in the SHA-512 request using the merchant's private_key. |
|
| A string subject to SHA-512 is generated by concatenating parameters merchant_id, data separated by “;” (semicolon) in UTF-8 encoding. |
|
| The order of the parameters when concatenating is important! |
|
The response is JSON with the following parameters:
Parameter | Description | Value |
|---|---|---|
mk_deposit | Mastercard limit |
|
visa_deposit | Visa limit |
|
mk_available | Available Mastercard balance |
|
visa_available | Available balance Visa |
|
signature |
|
|
Copyright © 2015-2023 PROCARD