Skip to main content

Debit

DEBIT request

Use debit actions to create debit transactions. When conducting a debit transaction, merchants can utilize commissions for payments by configuring the appropriate settings in the admin panel.

Debit transactions can be executed in two ways:

One-step debit

This option enables payment processing with a single request - DEBIT2VIRTUAL. If commissions are set for debits, they will be applied immediately upon payment. The commission amount can be viewed in the callback (commission parameter).

Two-steps debit

This option involves initiating the debit using the DEBIT2VIRTUAL_CALC request first, followed by confirming the operation through the DEBIT2VIRTUAL_COMPLETE request. In this scenario, if commissions are configured for debits, the commission amount will be returned in the response (commission parameter) after executing the DEBIT2VIRTUAL_CALC request.

DEBIT2VIRTUAL request parameters

Use DEBIT2VIRTUAL action to create debit transaction in one step.

ParameterDescriptionValuesRequired
actionAction that you want to perform. Fixed value.DEBIT2VIRTUAL+
client_keyUnique key (CLIENT_KEY)UUID format value+
order_idTransaction ID in the Merchants systemString up to 255 characters+
order_amountThe amount of the transactionNumbers in the form XXXX.XX+
order_currencyCurrency3-letter code+
order_descriptionDescription of the transaction (product name)String up to 1024 characters+
identifierExtra parameter for transaction.
It could be token, account information, additional descriptor etc.
String up to 255 characters+
brandBrand through which the transaction is performedString up to 36 characters+
payer_first_nameCustomer’s nameString up to 32 characters-
payer_last_nameCustomer’s surnameString up to 32 characters-
payer_middle_nameCustomer’s middle nameString up to 32 characters-
payer_birth_dateCustomer’s birthdayformat yyyy-MM-dd, e.g. 1970-02-17-
payer_addressCustomer’s addressString up to 255 characters-
payer_address2The adjoining road or locality (if required) of the customer’s addressString up to 255 characters-
payer_countryCustomer’s country2-letter code-
payer_stateCustomer’s stateString up to 32 characters-
payer_cityCustomer’s cityString up to 40 characters-
payer_zipZIP-code of the CustomerString up to 10 characters-
payer_emailCustomer’s emailString up to 255 characters-
payer_phoneCustomer’s phoneString up to 32 characters-
payer_phone_country_codeCountry calling code of the payer’s phone numberDigits, up to 10 characters. A hyphen is allowed for composite codes, for example 1-684-
payer_ipIP-address of the CustomerXXX.XXX.XXX.XXX+
payer_languageLanguage of the platform-hosted pages shown to the Customer during the payment, such as the interaction template and the Thank You page. The value is case-insensitive and is not validated: a code that is not on the list falls back to English.
If the parameter is omitted, the Checkout Default Language from the Protocol Mapping settings is used. If that is not set either, the language is taken from the Customer's browser.
One of: en, sp, ar, az, fr, nb, zh, zh-TW, kk, de, it, hr, cs, hu, pl, pt, ro, ja, nl, bg, ru-
payer_return_urlCustomer return URLString up to 256 characters+
hashSpecial signature to validate your request to Payment PlatformSee Appendix A, Debit signature+

Response parameters

You will get JSON encoded string with transaction result. If your account supports 3D-Secure, transaction result will be sent to your Notification URL.

Successful response

ParameterDescription
actionDEBIT2VIRTUAL
resultSUCCESS
status3DS / REDIRECT / SETTLED
order_idTransaction ID in the Merchant’s system
trans_idTransaction ID in the Payment Platform
trans_dateTransaction date in the Payment Platform
descriptorDescriptor from the bank, the same as payer will see in the bank statement
amountOrder amount
currencyCurrency
commissionCommission for transaction
total_amountTotal amount for transaction: total_amount = amount + commission

Unsuccessful response

ParameterDescription
actionDEBIT2VIRTUAL
resultDECLINED
statusDECLINED
order_idTransaction ID in the Merchant’s system
trans_idTransaction ID in the Payment Platform
trans_dateTransaction date in the Payment Platform
descriptorDescriptor from the bank, the same as payer will see in the bank statement
amountOrder amount
currencyCurrency
commissionCommission for transaction
total_amountTotal amount for transaction
decline_reasonThe reason why the transaction was declined

Undefined response

ParameterDescription
actionDEBIT2VIRTUAL
resultUNDEFINED
statusREDIRECT / PREPARE
order_idTransaction ID in the Merchant’s system
trans_idTransaction ID in the Payment Platform
trans_dateTransaction date in the Payment Platform
descriptorDescriptor from the bank, the same as payer will see in the bank statement
amountOrder amount
currencyOrder currency
commissionCommission for transaction
total_amountTotal amount for transaction: total_amount = amount + commission

Callback parameters

Successful response

ParameterDescription
actionDEBIT2VIRTUAL
resultSUCCESS
statusREDIRECT / 3DS / SETTLED
order_idTransaction ID in the Merchant’s system
trans_idTransaction ID in the Payment Platform
trans_dateTransaction date in the Payment Platform
descriptorDescriptor from the bank, the same as payer will see in the bank statement
amountOrder amount
currencyCurrency
commissionCommission for transaction
total_amountTotal amount for transaction: total_amount = amount + commission
connector_name *Connector's name (Payment Gateway)
rrn *Retrieval Reference Number value from the acquirer system
approval_code *Approval code value from the acquirer system
gateway_id *Gateway ID – transaction identifier provided by payment gateway
extra_gateway_id *Extra Gateway ID – additional transaction identifier provided by payment gateway.
merchant_name *Merchant Name
mid_name *MID Name
issuer_country *Issuer Country
issuer_bank *Issuer Bank
hashSpecial signature, used to validate callback, see Appendix A, Callback signature

* The parameters are included if the appropriate setup is configured in the admin panel (see “Add Extended Data to Callback” block in the Configurations -> Protocol Mappings section).

Unsuccessful response

ParameterDescription
actionDEBIT2VIRTUAL
resultDECLINED
statusDECLINED
order_idTransaction ID in the Merchant’s system
trans_idTransaction ID in the Payment Platform
trans_dateTransaction date in the Payment Platform
descriptorDescriptor from the bank, the same as payer will see in the bank statement
amountOrder amount
currencyCurrency
commissionCommission for transaction
total_amountTotal amount for transaction: total_amount = amount + commission
decline_reasonDescription of the cancellation of the transaction
hashSpecial signature, used to validate callback, see Appendix A, Callback signature

Undefined response

ParameterDescription
actionDEBIT2VIRTUAL
resultUNDEFINED
statusREDIRECT / PREPARE
order_idTransaction ID in the Merchant’s system
trans_idTransaction ID in the Payment Platform
trans_dateTransaction date in the Payment Platform
descriptorDescriptor from the bank, the same as payer will see in the bank statement
amountOrder amount
currencyOrder currency
commissionCommission for transaction
total_amountTotal amount for transaction: total_amount = amount + commission
hashSpecial signature, used to validate callback, see Appendix A, Callback signature

DEBIT2VIRTUAL_CALC request parameters

Use DEBIT2VIRTUAL_CALC action to initiate DEBIT transaction and to get commission value.

ParameterDescriptionValuesRequired
actionAction that you want to perform. Fixed value.DEBIT2VIRTUAL_CALC+
client_keyUnique key (CLIENT_KEY)UUID format value+
order_idTransaction ID in the Merchants systemString up to 255 characters+
order_amountThe amount of the transactionNumbers in the form XXXX.XX+
order_currencyCurrency3-letter code+
order_descriptionDescription of the transaction (product name)String up to 1024 characters+
identifierExtra parameter for transactionIt could be token, account information, additional descriptor etc.+
brandBrand through which the transaction is performedString up to 36 characters+
payer_first_nameCustomer’s nameString up to 32 characters-
payer_last_nameCustomer’s surnameString up to 32 characters-
payer_middle_nameCustomer’s middle nameString up to 32 characters-
payer_birth_dateCustomer’s birthdayformat yyyy-MM-dd,
e.g. 1970-02-17
-
payer_addressCustomer’s addressString up to 255 characters-
payer_address2The adjoining road or locality (if required) of the customer’s addressString up to 255 character-
payer_countryCustomer’s country2-letter code-
payer_stateCustomer’s stateString up to 32 characters-
payer_cityCustomer’s cityString up to 40 characters-
payer_zipZIP-code of the CustomerString up to 10 characters-
payer_emailCustomer’s emailString up to 255 characters-
payer_phoneCustomer’s phoneString up to 32 characters-
payer_phone_country_codeCountry calling code of the payer’s phone numberDigits, up to 10 characters. A hyphen is allowed for composite codes, for example 1-684-
payer_ipIP-address of the CustomerXXX.XXX.XXX.XXX+
payer_languageLanguage of the platform-hosted pages shown to the Customer during the payment, such as the interaction template and the Thank You page. The value is case-insensitive and is not validated: a code that is not on the list falls back to English.
If the parameter is omitted, the Checkout Default Language from the Protocol Mapping settings is used. If that is not set either, the language is taken from the Customer's browser.
One of: en, sp, ar, az, fr, nb, zh, zh-TW, kk, de, it, hr, cs, hu, pl, pt, ro, ja, nl, bg, ru-
payer_return_urlCustomer return URLString up to 256 characters+
hashSpecial signature to validate your request to Payment PlatformSee Appendix A, Debit signature+

Response parameters

You will get JSON encoded string with transaction result.

Successful response

ParameterDescription
actionDEBIT2VIRTUAL_CALC
resultSUCCESS
statusPREPARE
order_idTransaction ID in the Merchant’s system
trans_idTransaction ID in the Payment Platform
trans_dateTransaction date in the Payment Platform
descriptorDescriptor from the bank, the same as payer will see in the bank statement
amountOrder amount
currencyCurrency
commissionCommission for transaction
total_amountTotal amount for transaction: total_amount = amount + commission

Unsuccessful response

ParameterDescription
actionDEBIT2VIRTUAL_CALC
resultDECLINED
statusDECLINED
order_idTransaction ID in the Merchant’s system
trans_idTransaction ID in the Payment Platform
trans_dateTransaction date in the Payment Platform
descriptorDescriptor from the bank, the same as payer will see in the bank statement
amountOrder amount
currencyCurrency
commissionCommission for transaction
total_amountTotal amount for transaction
decline_reasonThe reason why the transaction was declined

Callback parameters

Successful response

ParameterDescription
actionDEBIT2VIRTUAL_CALC
resultSUCCESS
statusPREPARE
order_idTransaction ID in the Merchant’s system
trans_idTransaction ID in the Payment Platform
trans_dateTransaction date in the Payment Platform
descriptorDescriptor from the bank, the same as payer will see in the bank statement
amountOrder amount
currencyCurrency
commissionCommission for transaction
total_amountTotal amount for transaction
connector_name *Connector's name (Payment Gateway)
rrn *Retrieval Reference Number value from the acquirer system
approval_code *Approval code value from the acquirer system
gateway_id *Gateway ID – transaction identifier provided by payment gateway
extra_gateway_id *Extra Gateway ID – additional transaction identifier provided by payment gateway.
merchant_name *Merchant Name
mid_name *MID Name
issuer_country *Issuer Country
issuer_bank *Issuer Bank
hashSpecial signature, used to validate callback, see Appendix A, Callback signature

* The parameters are included if the appropriate setup is configured in the admin panel (see “Add Extended Data to Callback” block in the Configurations -> Protocol Mappings section).

Unsuccessful response

ParameterDescription
actionDEBIT2VIRTUAL_CALC
resultDECLINED
statusDECLINED
order_idTransaction ID in the Merchant’s system
trans_idTransaction ID in the Payment Platform
trans_dateTransaction date in the Payment Platform
descriptorDescriptor from the bank, the same as payer will see in the bank statement
amountOrder amount
currencyCurrency
commissionCommission for transaction
total_amountTotal amount for transaction
decline_reasonDescription of the cancellation of the transaction
hashSpecial signature, used to validate callback, see Appendix A, Callback signature

DEBIT2VIRTUAL_COMPLETE request parameters

Use DEBIT2VIRTUAL_COMPLETE action to confirm initiated debit transaction.

ParameterDescriptionValuesRequired field
actionAction that you want to perform. Fixed value.DEBIT2VIRTUAL_COMPLETE+
client_keyUnique key (CLIENT_KEY)UUID format value+
trans_idInitiated transfer transaction ID in the Payment PlatformUUID format value+
hashSpecial signature to validate your request to Payment PlatformSee Appendix A, Complete Debit signature+

Response parameters

You will get JSON encoded string (see an example on Appendix B) with transaction result. If your account supports 3D-Secure, transaction result will be sent to your notification_url.

Successful response

ParameterDescription
actionDEBIT2VIRTUAL_COMPLETE
resultSUCCESS
status3DS / REDIRECT / SETTLED
order_idTransaction ID in the Merchant’s system
trans_idTransaction ID in the Payment Platform
trans_dateTransaction date in the Payment Platform
descriptorDescriptor from the bank, the same as payer will see in the bank statement
amountOrder amount
currencyCurrency
commissionCommission for transaction
total_amountTotal amount for transaction

Unsuccessful response

ParameterDescription
actionDEBIT2VIRTUAL_COMPLETE
resultDECLINED
statusDECLINED
order_idTransaction ID in the Merchant’s system
trans_idTransaction ID in the Payment Platform
trans_dateTransaction date in the Payment Platform
descriptorDescriptor from the bank, the same as payer will see in the bank statement
amountOrder amount
currencyCurrency
commissionCommission for transaction
total_amountTotal amount for transaction
decline_reasonThe reason why the transaction was declined

Undefined response

ParameterDescription
actionDEBIT2VIRTUAL_COMPLETE
resultUNDEFINED
statusREDIRECT / PREPARE
order_idTransaction ID in the Merchant’s system
trans_idTransaction ID in the Payment Platform
trans_dateTransaction date in the Payment Platform
descriptorDescriptor from the bank, the same as payer will see in the bank statement
amountOrder amount
currencyOrder currency
commissionCommission for transaction
total_amountTotal amount for transaction: total_amount = amount + commission

Callback parameters

Successful response

ParameterDescription
actionDEBIT2VIRTUAL
resultSUCCESS
status3DS / REDIRECT / SETTLED
order_idTransaction ID in the Merchant’s system
trans_idTransaction ID in the Payment Platform
trans_dateTransaction date in the Payment Platform
descriptorDescriptor from the bank, the same as payer will see in the bank statement
amountOrder amount
currencyCurrency
commissionCommission for transaction
total_amountTotal amount for transaction
connector_name *Connector's name (Payment Gateway)
rrn *Retrieval Reference Number value from the acquirer system
approval_code *Approval code value from the acquirer system
gateway_id *Gateway ID – transaction identifier provided by payment gateway
extra_gateway_id *Extra Gateway ID – additional transaction identifier provided by payment gateway.
merchant_name *Merchant Name
mid_name *MID Name
issuer_country *Issuer Country
issuer_bank *Issuer Bank
hashSpecial signature, used to validate callback, see Appendix A, Callback signature

* The parameters are included if the appropriate setup is configured in the admin panel (see “Add Extended Data to Callback” block in the Configurations -> Protocol Mappings section).

Unsuccessful response

ParameterDescription
actionDEBIT2VIRTUAL
resultDECLINED
statusDECLINED
order_idTransaction ID in the Merchant’s system
trans_idTransaction ID in the Payment Platform
trans_dateTransaction date in the Payment Platform
descriptorDescriptor from the bank, the same as payer will see in the bank statement
amountOrder amount
currencyCurrency
commissionCommission for transaction
total_amountTotal amount for transaction
decline_reasonDescription of the cancellation of the transaction
hashSpecial signature, used to validate callback, see Appendix A, Callback signature

Undefined response

ParameterDescription
actionDEBIT2VIRTUAL
resultUNDEFINED
statusREDIRECT / PREPARE
order_idTransaction ID in the Merchant’s system
trans_idTransaction ID in the Payment Platform
trans_dateTransaction date in the Payment Platform
descriptorDescriptor from the bank, the same as payer will see in the bank statement
amountOrder amount
currencyOrder currency
commissionCommission for transaction
total_amountTotal amount for transaction: total_amount = amount + commission
hashSpecial signature, used to validate callback, see Appendix A, Callback signature