Objects Wallet Data
{danger.fa-exclamation-triangle} NOTE: If you are unable to send correct customer details, which can be the case since different processors demand various specific items, there is a setting in the Praxis Backoffice which allows to redirect a user to the cashier page and fill in the missing information. Please contact your Customer Satisfaction Manager for more information.
STRUCTURE
✓ - required value
? - optional, value or null
✕ - always appears as null
| Variable | Type | Description |
|---|---|---|
| <Object> | <Object> | Generic wallet data object. The object structure differs through e-wallets and bank accounts |
EXAMPLE
{
"full_name": "John Johnson",
"bank_account": "11112222333344",
"bank_name": "Random Bank, London",
"bank_code": "AABBCC",
"iban": "GB999911112222333344"
}PAYMENT METHODS
Following in an example dummy wallet data format
| Variable | Type | Description |
|---|---|---|
| wallet_data.login | varchar(50) | Required. Login as specified in the e-wallet account |
{
"login": "johnjohnson1"
}Following in an example dummy bank account data format
| Variable | Type | Description |
|---|---|---|
| wallet_data.full_name | varchar(50) | Required. Full name as registered in the bank |
| wallet_data.bank_account | varchar(32) | Required. Customer's bank account number |
| wallet_data.bank_name | varchar(32) | Required. Customer's bank name |
| wallet_data.bank_code | varchar(32) | Required. Customer's bank code |
| wallet_data.iban | varchar(32) | Required. Customer's IBAN |
{
"full_name": "John Johnson",
"bank_account": "11112222333344",
"bank_name": "Random Bank, London",
"bank_code": "AABBCC",
"iban": "GB999911112222333344"
}