Page History
...
The initial operation is carried out using a conventional bankcard, or using a mobile device tokenization system, for example, Apple Pay, Samsung Pay or Google Pay.
In any case, The initial COF operation is carried out with verification by one of the possible ways (CVC2 and 3dS or using a mobile device) is required for the initial COF operation.
Subsequent operations can be carried out after the successful initial operation completion of the primary transaction with the obligatory consent of the payer to for the further use of card data. Subsequent operations are carried out without any verification.a re-verification procedure, if the processing protocol allows it.
| Note |
|---|
Note. If the initial operation is carried out using a mobile device tokenization system (Apple Pay, Samsung Pay or Google Pay), then the subsequent operations will be similar to the initial ones, without additional features. |
CIT COF operations
Subsequent operations can be initiated by the payer. These operations are called «Customer Initialized Transaction» (CIT).
The One Click program service is used to implement CIT COF operations in IPS Assist.
By participating in the program service, the company maintains its database of customers, giving them an unique number (CustomerNumber), while the Assist system stores the encrypted credit card data corresponding to those merchant customers (CustomerNumber).
While performing of order payment, the customer gets an offer to save the card for future payments using the One Click program service.
The One Click program (see the «One Click Program» document) allows service allows a regular customer of a merchant to make new purchases without entering card data. The payment requires only confirmation by the CVC2 code. However, if the initial COF operation is successful, the CVC2 code will not be requested in the subsequent operationsfor subsequent operations CIT COF with a saved card, CVC2 will usually not be requested (except the cases where special settings are made at the request of the merchant).
| Note |
|---|
To start use the COF operations the merchant should send request to support team support@assist.ru. The request should contain the merchant identifier (Merchant_ID). |
...
After the customer completes the payment for the order, a message with the payment parameters can be sent to the server of the merchant using the HTTP POST or SOAP method (for more details, see section 3.5 of the document «Setting up the technical interaction with IPS Assist») or the merchant can request the payment results by calling the orderresult web service.
...
When the merchant builds the next order, it is possible to redirect to the IPS Assist payment page to pay with the earlier saved card. In this case, the merchant must send order data with a unique customer number, i.e. in addition to the authorized request parameters, it is necessary to transfer the CustomerNumber.
| Note |
|---|
This parameter must not be transmitted simultaneously with the RecurringIndicator, RecurringMinAmount, RecurringMaxAmount, RecurringPeriod, RecurringMaxDate parameters. |
All actions related to payment by a saved card are performed on the Assist side.
If for any reason it is more convenient for the merchant to independently display an offer to the customer to pay the order with a previously saved card (on its website or in a specialized mobile application), then in order to use CIT COF, the merchant has to call the Token Pay payment web-service.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 (support@assist.ru) 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 (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
...
256 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
...
5 – Assist;
...
1
...
Payment Token Type Identifier
...
PaymentToken
...
No
...
JSON
...
Payment Token
{"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 – don't convert to the base currency
1 - don't convert to the base currency if possible
2 – always convert to the base currency
...
1
...
Currency conversion indicator
...
Format
...
No
...
4 – SOAP
5 – JSON
...
5
...
Results format.
...
Signature
...
No
...
String
...
The string is joined according to determined rules.
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.
...
Chequeitems
...
No/Yes**
...
String in JSON-format
...
Cheque items according to the section “Payment with cheque”.
...
GenerateReceipt
...
No
...
0 or 1
...
1
...
Permission to generate of a fiscal receipt. If the value of parameter is 0, the generation of a fiscal receipt is prohibited for this order.
...
Tax
...
No
...
10 characters
...
Parameter is determined by the “Default tax rate” option of the merchant and used in the mode without transfer of the cheque items (the entire amount must be paid with one rate).
...
...
ReceiptLine
...
No
...
128 characters
...
Parameter is determined by the “Default text of cheque item” option of the merchant and used in the mode without transfer of the cheque items.
...
Text description of the cheque item, if the cheque has one single item.
...
FPMode
...
No
...
Number
...
Parameter is determined by the “Default payment method” option of the merchant and used in the mode without transfer of the cheque items.
...
...
TaxationSystem
...
No/Yes*
...
Number
...
From the merchant’s or CRE settings
...
Note to the parameter TokenType, the value of which should be equal to 5, and also the value of the PaymentToken parameter, which must contain the unique customer number in the merchant database (CustomerNumber) and the unique identifier of the saved customer card received during the initial operation of this customer from the IPS Assist.
...
The list of response parameters is similar to the standard response of the Token Pay service.
| Note |
|---|
Payment will be made as a CIT COF operation only if the corresponding processing is set up for the merchant in the IPS Assist. Otherwise, the operation will fail. |
...
Parameter | Mandatory field | Adopted values | Default value | Description |
RecurringIndicator | NoYes | 1 –recurring payment | 0 | Recurring payment indicator |
...
| ||||||
RecurringMinAmount | Yes | Number, 15 digits, two digits after the delimiter (delimiter '.') | Min amount of recurrent payments. Mandatory if RecurringIndicator = 1
| |||
RecurringMaxAmount | Yes | Number, 15 digits, two digits after the delimiter (delimiter '.') | Max Amount of recurrent payments. Mandatory if RecurringIndicator = 1
| |||
RecurringCount | Yes | Number, 3 digits | Frequency of recurrent payments in days. Mandatory if RecurringIndicator = 1
| |||
RecurringMaxDate | Yes | Date as string in DD.MM.YYYY format | The end date of recurrent payments. Mandatory if RecurringIndicator = 1
|
| Note | ||
|---|---|---|
Payment will be made as a MIT COF operation only if the corresponding processing is set up for the merchant in the IPS Assist. Otherwise, the transaction will be carried out as a regular recurrent payment
|
...
List of response parameters:
Parameter | Value |
token | Token of stored card |
post | Last 4 digits of the card number |
bin | First 6 digits of the card number |
brand | Payment system of the card |
bank | Name of Bank-Issuer |
expire | Month and year of card expiration (MM.YYYY) |
active | Whether the card is valid |
needCVC | Entering of CVC is required for authorization |
assets* | Media data array of the card (determine the appearance of the card) |
*If IPS Assist does not have media data for the card, then this parameter is returned with an empty value in the response.
Contents of the media data array
Parameter | Adopted values | Description |
assetType | BRAND_LOGO | Type of card design graphic component |
altText | ||
paymentType | VISA | Payment system type |
assetData | ||
url | URL of the file containing the image of card design graphic component | |
mediaType | image/png | Image file format |
width | Image dimensions in pixels | |
height | ||
In case of an error, the service returns the error data in JSON format.
{"fault":{"detail":"<error message>","faultcode":<first tcode>,"faultstring":<second code >}}.
Example of the response when the customer has several cards:
| Code Block | ||
|---|---|---|
| ||
[{"expire":"12.2025","token":"49D902C6-1CCF-4605-9228-11D0E8115C77","bank":"","brand":"VISA","bin":412362,"active":true,"needCVC":false,"post":"0028","assets":[{"assetType":"ICON","altText":"cardSymbol","paymentType":"VISA","assetData":[
{"url":"https://emvts-test-assets.s3.amazonaws.com/A5/VISA/aa3dcd69e8e8407fa2a59a1956994610/w100_h100.png","mediaType":"image/png","width":100,"height":100}
]},{"assetType":"CARD_BACKGROUND","altText":"digitalCardArt","paymentType":"VISA","assetData":[
{"url":"https://emvts-prod-assets.s3.eu-north-1.amazonaws.com/B5/VISA/fa0ff42cfa9e41b09ae8c2899d61394a/w1536_h969.png","mediaType":"image/png","width":1536,"height":969}
]}]},{"expire":"12.2025","token":"4D7F0B0D-B701-47B0-779A-BB0CB5F25A14","bank":"","brand":"MasterCard","bin":518615,"active":true,"needCVC":false,"post":"1030","assets":[{"assetType":"BRAND_LOGO","altText":null,"paymentType":"MC","assetData":[
{"url":"https://emvts-test-assets.s3.amazonaws.com/A5/MC/3789637f-32a1-4810-a138-4bf34501c509/w0_h0.pdf","mediaType":"image/pdf","width":null,"height":null}
]},{"assetType":"ICON","altText":null,"paymentType":"MC","assetData":[
{"url":"https://emvts-prod-assets.s3.eu-north-1.amazonaws.com/B5/MC/a7556277-51e9-4ef1-b503-dd8989e7a8bf/w100_h100.png","mediaType":"image/png","width":100,"height":100}
]},{"assetType":"CARD_BACKGROUND_COMBINED","altText":null,"paymentType":"MC","assetData":[
{"url":"https://emvts-prod-assets.s3.eu-north-1.amazonaws.com/B5/MC/eb50276e-7e28-4cd1-9b95-c8dfbe595db6/w1536_h969.png","mediaType":"image/png","width":1536,"height":969}
]},{"assetType":"ISSUER_LOGO","altText":null,"paymentType":"MC","assetData":[
{"url":"https://emvts-prod-assets.s3.eu-north-1.amazonaws.com/B5/MC/de7ce012-641e-450c-8b4f-a65d78062999/w1372_h283.png","mediaType":"image/png","width":1372,"height":283}
]}]}] |
An example of the response when there is no media data for the card:
| Code Block | ||
|---|---|---|
| ||
[{"expire":"12.2025","token":"91720736-CF93-469C-63A0-E5859815D6BA","bank":"Bank USA","brand":"MasterCard","bin":546792,"active":true,"needCVC":false,"post":"4128","assets":[]}] |
Deleting a stored card (token) of a merchant customer
The web service allows a merchant to remove a card token by the unique identifier of its customer.
To access the web service send a request using the POST method to the request URL https://<SERVER_NAME>/pay/oneclick/v1/rem_token.cfm with parameters in JSON format.
List of request parameters:
Parameter | Mandatory field | Adopted values | Default value | Description | |
Merchant | Merchant_ID | Yes | Number | The enterprise identifier in IPS Assist | |
Login | Yes | 20 characters | Web service user login | ||
Password | Yes | 30 characters | Web service user password | ||
CustomerNumber* | Yes | 32 characters | Merchant's internal customer identification | ||
Language | No | RU - Russian, EN - English | Language of legal entity/enterprise | Language of authorized pages | |
Token | Yes | 36 characters | Token of stored card | ||
*The parameter is automatically validated according to the rules.
An example of request:
| Code Block | ||
|---|---|---|
| ||
POST https://<SERVER-NAME>/pay/oneclick/v1/rem_token.cfm
POST data:{"merchant":{"merchant_id":"452739","login":"LOGIN", "password":"PASSWORD"}, "token": "54F5A3DE-4B47-4B40-03B5-7FF992D6B401", "language": "RU", "customernumber":"1234"} |
The request result is sent in JSON format with the message «Token is remowed».
Example of the response:
| Code Block | ||
|---|---|---|
| ||
{"message":"Token 33479991-B4E5-40FE-D9ED-EDC94BA7FA14 is removed"} |
In case of an error, the service returns the error data in JSON format.
{"fault":{"detail":"<error message>","faultcode":<first tcode>,"faultstring":<second code >}}.