To pay with a token, you need to send a request to the IPS Assist server in JSON format (swagger description: https://docs.belassist.by/swagger/).
The request URL for transfer the encrypted payment data block:
https://<SERVER_NAME>/pay/tokenpay.cfm ,
As <SERVER_NAME> you should use the received from support service value as the domain name.
List of request parameters:
Parameter | Mandatory field | Adopted values | Default value | Description | |
Merchant_ID | Yes | Number | The enterprise identifier in IPS Assist | ||
Login | Yes | 8-20 characters | Login in IPS Assist (Latin letters, digits and symbol _) | ||
Password | Yes | 8-20 characters | Password in IPS Assist (Latin letters and digits) | ||
OrderNumber | Yes | 128 characters | Order number in the merchant payments system | ||
OrderAmount | Yes | Number, 15 digits, two digits after the delimiter (delimiter '.') | Payment amount, in original currency (e.g., 10.34). | ||
OrderCurrency | No | 3 characters | Currency of legal entity/enterprise | Code of currency of the OrderAmount | |
OrderComment | No | 4000 characters | Comment. | ||
Delay | No | 0 – one-stage operation 1 – double-stage operation | 0 | Attribute of a bankcard authorization for the double-stage operation mode. | |
Language | No | RU – Russian, EN – English | Language of legal entity/enterprise | Language of authorized pages | |
ClientIP | No | Maximum of 15 digits, 4 delimiters «.» | IP-address of the customer | ||
TokenType | No | 1 – Apple Pay; | 1 | Payment Token Type Identifier 5 - payment token Assist is used for CIT COF operations | |
PaymentToken | No | JSON | For token types 1-3 - provider payment token (Apple Pay, Google Pay; Samsung Pay). For Assist payment token (token type 5) - {"Token": "<UUID>", "CustomerNumber": "<CustomerNumber>"} | ||
Lastname | No | 70 characters | Customer's last name. | ||
Firstname | No | 70 characters | Customer's first name. | ||
Middlename | No | 70 characters | Customer's middle name. | ||
No | 128 characters | Customer's e-mail. | |||
Address | No | 256 characters | Customer's address. | ||
HomePhone | No | 64 characters | Customer's home phone number. | ||
WorkPhone | No | 20 characters | Customer's work phone number. | ||
MobilePhone | No | 20 characters | Customer's mobile phone number. | ||
Fax | No | 20 characters | Customer's fax number. | ||
Country | No | 3 characters | Customer's country. | ||
State | No | 3 characters | Customer's region. | ||
City | No | 70 characters | Customer's city. | ||
Zip | No | 25 characters | Customer's post zip code. | ||
isConvert | No | 0 – do not convert to the base currency 1 - do not convert to the base currency if possible 2 – always convert to the base currency | 1 | Currency conversion indicator | |
Format | No | 4 – SOAP | 5 | Results format. | |
Signature | No | String | The string is joined from the following order parameters: Merchant_ID;OrderNumber;OrderAmount;OrderCurrency with semicolon as delimiter. Then the MD5 hash prepared from this string. Hash is signed by private RSA key of the merchant. Key length - 1024. Received bit sequence is a signature. Signature is transferred BASE64 coded string.
| ||
RecurringIndicator | No | 1 –recurring payment 0 – standard payment | 0 | Recurring payment indicator | |
RecurringMinAmount | No/Yes | Number, 15 digits, two digits after the delimiter (delimiter '.') | Minimum payment amount for recurring payments Mandatory when RecurringIndicator = 1 | ||
RecurringMaxAmount | No/Yes | Number, 15 digits, two digits after the delimiter (delimiter '.') | Maximum payment amount for recurring payments Mandatory when RecurringIndicator = 1 | ||
RecurringPeriod | No/Yes | 10 digits number | Recurring interval in days Mandatory when RecurringIndicator = 1 | ||
RecurringMaxDate | No/Yes | Date in string representation DD.MM.YYYY | Finish date of recurring payments Mandatory when RecurringIndicator = 1 |