Page History
...
Field | Description | Type | |||
Meannumber | The encrypted card number* 1 has to be passed as following string: "IR_TOKEN=<irreversible token PAN> BIN=<6 first digits of PAN> POST==<4 last digits of PAN>". Alternatively, you can pass the payment mean number in unencrypted form, but this ability will be removed in the future. | String (70 chars) | |||
meanTypeGroup | Group of payment means: 1 - card (by default), 2 – E-wallet | Integer (1) | |||
meanType | Type of E-wallet (required for E-wallets). Available types of electronic wallets are presented in the table «Type of E-wallets». | String (3 chars) | |||
OutAmount | Payment amount in original currency | Decimal (15,2) | |||
OutCurrencyCode | Currency code (ISO 42 17) | String (3 chars) | |||
BillNumber | Bill number from external system | String (30 chars) | |||
OrderNumber | Order number for payment operation | String (128 chars) | |||
Customer Email | String (128 chars) | ||||
Firstname | Customer name | String (128 chars) | |||
Middlename | Customer middle name | String (70 chars) | |||
Lastname | Customer second name | String (70 chars) | |||
Regioncode | Customer region code | String (8 chars) | |||
Regionname | Customer region name | String (70 chars) | |||
City | City | String (70 chars) | |||
Countrycode | Country code (ISO 3166 alpha-2) | String (2 chars) | |||
Address | Customer postal address | String (256 chars) | |||
Postcode | Postal index | String (25 chars) | |||
Phone | Phone number | String (20 chars) | |||
Workphone | Work phone number | String (20 chars) | |||
Mobilephone | Mobile phone number | String (20 chars) | Fax | Fax number | String (20 chars) |
Cardholder | Card-holder name | String (130 chars) | |||
Bankname | Issuer-Bank name | String (100 chars) | |||
Acquirer | Acquirer name (unique within the external system). | String (10 chars) | |||
Date | Payment data (UTC data (GMT-0) or GMT+ hour-offset). If it is not provided then current date is used. | Data | |||
Expiredate | Card expire date (month, year). UTC data (GMT-0) or GMT+ hour-offset when time is including. | Data | |||
BillingNumberTag | Type of billing number in favor of which the payment is made as cell phone number, contract number for communication services, etc. Currently, the following types of billing are available for activation: · YBIL (Yota billing); · MTSBelBlN (MTS Belarussia BillNumber); · MTSBelPhN (MTS Belarussia PhoneNumber); · MTTPhN (MTT Phone Number); · MTTTel (MTT Telecommunication); · MTTInt (MTT Internet). | String (10 chars) | |||
BillingNumber | Billing number in favor of which the payment is made. | String (10 chars) | |||
TwoStepSchema | Double stage payment (separate authorization and charge operations are performed). If it is not provided then single stage (one operation assumes authorization and charge is performed). | Logical (true, false) | |||
Additional fields for payments by American Express cards | |||||
billingPostalCode | Customer postal index | String (9 chars) | |||
billingAddress | Customer postal address | String (20 chars) | |||
billingFirstName | Customer name | String (15 chars) | |||
billingLastName | Customer second name | String (30 chars) | |||
billingPhoneNumber | Customer phone number | String (10 chars) | |||
billingEMailAddress | Customer E-mail | String (60 chars) | |||
TestMode | Test payment indicator. | Logical (true, false) | |||
RecurringIndicator | Recurring payment indicator | Logical (true, false) | |||
usedCSC | Card Secure Code was used | Logical (true, false) | |||
3DSecAuthresult | 3DSecure authorization result (Y - success, N - fail, A - attempt, U –unknown) | String (1 char) | |||
AirData | XML with additional flight data (for air companies)**2 | Text | |||
BookingData | XML with additional booking data***3 | Text | |||
3DSecAuthrequired | Result of card 3dS involvement check (1 – involved, 0 – not involved, -1 – not-known, null – all rest) | Decimal (1) |
Anchor 1 1
1*To get access to the service for receiving irreversible token from ASSIST company, you have to contact technical support team (support@assist.ru).
...
E-wallet type | E-wallet name |
WM | WebMoney |
EP | EasyPay |
QW | QIWI |
QB | QIWIBeeline |
QM | QIWIMts |
QF | QIWIMegafon |
MB | Mobicon |
YM | YandexMoney |
Anchor 2 2
2 ** XML format for additional flight-data:
Code Block | ||
---|---|---|
| ||
<ad_pnr> <pnrdate>...</pnrdate> <!-- datetime 8 --> <email>...</email> <!-- varchar 128 --> <language>...</language> <!-- varchar 5 --> <phoneb>...</phoneb> <!-- varchar 32 (work)--> <phone>...</phone> <!-- varchar 32 (personal)--> <phonem>...</phonem> <!-- varchar 32 (mobile)--> <airline_rec_loc>...</airline_rec_loc> <!-- varchar 16 (usually is Record_locator)--> <record_locator>...</record_locator> <!-- varchar 16 (usually is PNR)--> <traveler_id>...</traveler_id> <!-- varchar 16 (customer code)--> <air_amount_1>...</air_amount_1> <!-- money 8 (amount in orig. currency)--> <air_amount_2>...</air_amount_2> <!-- money 8 (amount in currency of payment)--> <air_amount_with_serv_1>...</air_amount_with_serv_1> <!-- money 8 --> <air_amount_with_serv_2>...</air_amount_with_serv_2> <!-- money 8 --> <air_amount_without_tax_1>...</air_amount_without_tax_1> <!-- money 8 --> <air_amount_without_tax_2>...</air_amount_without_tax_2> <!-- money 8 --> <air_currency_code_1>...</air_currency_code_1> <!-- varchar 5 --> <air_currency_code_2>...</air_currency_code_2> <!-- varchar 5 --> <delivery_type>...</delivery_type> <!-- varchar 16 (code of delivery)--> <agent_code>...</agent_code> <!-- varchar 16 (agency code)--> <charge_type>...</charge_type> <!-- varchar 16 (agency code)--> <ticket_number>...</ticket_number> <!-- varchar 14 (ticket number)--> <restr_ticked_ind>...</restr_ticked_ind> <!-- varchar 1 (Restricted Ticked Indicator)--> <add_field1>...</add_field1> <!-- varchar 255 (Positioned extended record)--> <add_field2>...</add_field2> <!-- varchar 255 (Positioned extended record)--> <number>...</number><!-- varchar 16 (pnr number)--> <number>...</number><!-- varchar 16 (pnr number)--> ... <segment> <!-- маршрут --> <airline_code>...</airline_code> <!-- varchar 5 (company code)--> <airline_name>...</airline_name> <!-- varchar 64 (company name)--> <cabin>...</cabin> <!-- varchar 5 (class)--> <flight_number>...</flight_number> <!-- varchar 16 (flight number)--> <flight_time>...</flight_time> <!-- varchar 12 (flight time)--> <itinerary_numb>...</itinerary_numb><!-- int 4 (direction number)--> <orig_numb>...</orig_numb> <!-- int 4 (number)--> <equipment_code>...</equipment_code><!-- varchar 16 (class)--> <stop_over_code>...</stop_over_code><!-- varchar 1 (stop-over indicator)--> <from> <date>...</date> <!-- varchar 50 (time of departure)--> <code>...</code> <!-- varchar 5 (departure airport code)--> <name>...</name> <!-- varchar 64 (departure airport name)--> <terminal>...</terminal><!-- varchar 5 (departure terminal)--> <country>...</country> <!-- varchar 64 (departure country)--> <state>...</state> <!-- varchar 64 (state of departure)--> <city>...</city> <!-- varchar 64 (departure city)--> </from> <to> <date>...</date> <!-- varchar 50 (arrival time)--> <code>...</code> <!-- varchar 5 (arrival airport code)--> <name>...</name> <!-- varchar 64 (arrival airport name)--> <terminal>...</terminal><!-- varchar 5 (arrival terminal)--> <country>...</country> <!-- varchar 64 (arrival country)--> <state>...</state> <!-- varchar 64 (state of arrival)--> <city>...</city> <!-- varchar 64 (arrival city)--> </to> </segment> <segment> <!-- route --> ... </segment> ... <traveler> <!-- passenger --> <orig_numb>...</orig_numb> <!-- int 4 (number)--> <first_name>...</first_name> <!-- varchar 32 --> <last_name>...</last_name> <!-- varchar 32 --> <passenger_name>...</passenger_name> <!-- varchar 64 --> <rbd>...</rbd> <!-- varchar 5 (booking class)--> <status>...</status> <!-- varchar 32 (status)--> <ticket_number>...</ticket_number> <!-- varchar 14 (passenger ticket number)--> </traveler> <traveler> <!-- пассажир --> ... </traveler> ... <child> <orig_numb>...</orig_numb> <!-- int 4 --> <first_name>...</first_name> <!-- varchar 32 --> <last_name>...</last_name> <!-- varchar 32 --> </child> <child> ... </child> ... </ad_pnr> |
Anchor 3 3
3 *** XML format for additional booking data:
...