What's new: archive

• Added information about payment testing for the ADVCash, Card payments via partner (Ukraine), DOKU Wallet, EcoPayz payment methods
• Updated information about payment testing for the WebMoney payment method
• Added section on payment processing by using Mobile Commerce in the United Kingdom payment method

• Added information about payment testing for the ADVCash, Card payments via partner (Ukraine), DOKU Wallet, EcoPayz payment methods
• Updated information about payment testing for the WebMoney payment method
• Added section on payment processing by using Mobile Commerce in the United Kingdom payment method

• Added the response codes 309, 3120, 3125 in the Information of operations performing section
• Updated and extended the Credential-on-file (COF) purchases section

• Added information about support for the Alipay and Neteller payment methods.
• Added information about the forcePaymentMethod and hideSavedWallets parameters.

• Added the following sections: Interaction concepts, Purchase processing, Authorisation hold, Payment instrument verification, COF purchase registration, Tokenization.
• Removed the Operation modes section. The information that was formerly provided in the Operation modes section is now available in the added sections.

• Added sections on payment processing by using the Open Banking in Estonia, Open Banking in Lithuania, Open Banking in the Netherlands, Payments by card-to-card money transfer via partner, Open Banking in the UK payment methods.
• Updated Gate API specification up to version 2.27.0:
  • added the endpoint for the card-to-card transfer method via a partner
  • added the card_product_type parameter to the endpoints for card purchases
  • added the customer.street parameter in response to a request for customer information
  • made other minor updates

• Removed sections "Payment types and statuses" and "Operation types and statuses". Information about types and statuses of payments and operations can be found in the section Payment models and statuses.
• Updated the Overview section: updated information about the interaction model and added Payment Page emulator. For more details, see Interaction model and Emulator.

• Changed the response code 3485 to 3472 in the section Information of operations performing.
• Added information about sending notifications in the section Sending notifications to customers.

• Added information on registering the ability to process payments by using the PayPal payment method
• Added the information about the merchant_refund_id parameter in the Callbacks
• Added the information about the response code 3230 in the section Information of operations performing
• Updated the Two-step purchase section: added information about time limit for authorization hold

• Added information about handling customer's biometric data and updated information about restrictions related to 3‑D Secure 2. For more details, see Frequently asked questions.
• Formed the Intermediate communication formats section with information about the formats of intermediate communication applicable to payment processing by using Gate.

• Updated information about the mandatory using of the customer_id parameter. Now it is required when requesting the payment form opening for payments performing by using any payment method.
• Updated information about payment methods supported by SDK for Android and SDK for iOS.

• The section about signing and signature verification in Gate is updated and extended to include signature generation and verification forms.
• Added the information about the possibility of making payments on expired cards in accordance with the recommendations of the Visa and Mastercard.
• Added new response codes 3029 in the section Information of operations performing.

• The section about signing and signature verification in Payment Page is updated and extended to include signature generation and verification forms
• Added the information about the possibility of making payments on expired cards in accordance with the recommendations of the Visa and Mastercard. For more information, see Supported payment cards
• Added new response codes 3029 in the section Information of operations performing.

• Updated the information about the code for pre-selecting the ADVCash payment method.
• Added section on payment processing by using the QIWI Push payment method.

• Updated the CMS WordPress plug-in file. The new version includes fixes of minor issues.
• Updated information on payment processing by using the Banks of Thailand payment method. Updated information on payout processing.
• Added section on payment processing by using the Thailand QR banking payment method.
• Added sections on payment processing by using the following methods: ADVCash, Flutterwave, M-Pesa, and Card payments via partner (Ukraine).

• Updated information on payment processing by using the Banks of Thailand payment method. Updated information on payout processing.
• Added section on payment processing by using the Thailand QR banking payment method.
• Added sections on payment processing by using the following methods: ADVCash, EcoPayz, EcoVoucher, Flutterwave, M-Pesa, and Card payments via partner (Ukraine).

• Added information about processing payment link purchases in sections Payment models and statuses and Payment link purchases.
• Updated Gate API specification: added the endpoints for payment link purchases.

• Added the event handler function onPaymentSubmitResult in the section Handling customer behaviour events on Payment Page.
• Updated and extended the section with the Overview of Payment Page.

• Added information about payment processing by using the Apple Pay payment method through SDK for iOS.
• Added section on payment processing by using the ATM & Bank Transfer in Indonesia (Virtual Accounts) payment method, payment processing by using this method was previously described in the Banks of Indonesia section.

• Added new response codes 3119, 3360, 3400, 3402-3410, 3431, 3450-3452, 3470-3471, 3480, 3485 in the section Information of operations performing.
• Added section on payment processing by using the ATM & Bank Transfer in Indonesia (Virtual Accounts) payment method, payment processing by using this method was previously described in the Banks of Indonesia section.

• Added new supported currencies and the mandatory purchase parameters for the China UnionPay payment method
• Updated section Checking current payment information: added information on response format and expanded the list of response examples. For more information, see Response format and Response examples

Updated section One-step purchase:

• removed information about transferring funds to the merchant's e-wallet
• added information about recommended parameters sent in the initial request for one-step purchase

For more details, see Request format.

• Added a new card type—Troy. The full list of supported card types, see in Supported payment cards
• Changed the maximum delay of callback sending. For information, see Callbacks

• Added a new card type—Troy. The full list of supported card types, see in Overview
• Changed the maximum delay of callback sending. For information, see Callbacks

• Updated information on payment processing by using the Mobile Commerce payment method. Updated information on payout processing.
• Added information about money transfer processing in sections Payment models and statuses and Card-to-card money transfer.
• Updated description of response code 104 in Information of operations performing.

• Added sections on payment processing by using Coins.ph, Crypto, GCash, GrabPay, Philippines Over the Counter & ATM, Philippines Payment Centers payment methods.
• Updated information on payment processing by using the Banks of the Philippines payment method. Added information on purchase processing.
• Updated information on integration by using SDK for Android (SDK version 1.4). For more information, see SDK for Android.

• Added sections on payment processing by using Coins.ph, Crypto, GCash, GrabPay, Philippines Over the Counter & ATM, Philippines Payment Centers payment methods.
• Updated information on payment processing by using the Banks of the Philippines payment method. Added information on purchase processing.
• Updated the Gate API specification:
  • added endpoints for new payment methods
  • removed endpoints for payment methods that are no longer supported

• Added information about payment testing for the Apple Pay payment method.
• Updated information on integration by using SDK for iOS (SDK version 1.4). For more information, see SDK for iOS.

• Added information about payment testing for the Apple Pay payment method.
• Updated and extended the section about purchase refund: Purchase refund.

• Added section about Card data encryption script
• Added information about payment testing for the Alfa-Click, Cash-in, Neteller, Skrill Wallet, WebMoney, Yandex.Money payment methods

• Added information about the customer redirection data format for one-step purchases by using cards. For more information, see One-step purchase.
• Added sections on refunds and card verification operations by using Apple Pay payment method, as well as the sections about purchases is updated .

• Updated information on payment processing by using the Trustly payment method. Added information on new way of payout processing
• Updated the section on payment processing by using the Card payments via partner (Uzbekistan) method. Updated information on payout processing
• Added the information about the payment.region parameter in the Callbacks instead of the previously used operation.region, and the new values are added in the Region codes reference

• Updated information on payment processing by using the Trustly payment method. Added information on new way of payout processing
• Updated the section on payment processing by using the Card payments via partner (Uzbekistan) method. Updated information on payout processing
• Added the information about the payment.region parameter in the Callbacks instead of the previously used operation.region, and the new values are added in the Region codes reference

• Removed section on payments processing by using the iWallet payment method. Payment processing by using this method is currently unavailable
• Updated API Gate specification:
  • added the endpoints for payment methods
  • updated the mandatory parameters for card tokenize request

• Updated the list of mandatory parameters for purchase processing in the Alipay section
• Updated the list of mandatory parameters for payout processing in the SEPA section

• Added the information about the recurring_update and recurring_cancel operation types. For more information, see, the COF purchase with automatic debiting.
• Added the information about the region_code parameter in the shipping and billing objects. For more information, see, the Payment request formats.

Updated the list of supported interface languages and added the information about the functionality that allows the customer to select interface language of Payment Page. For more information, see Interface language support

• Added sections on payment processing by using CepBank, GlobePay e-wallet, Hizli QR payment methods
• Updated sections on payment processing by using Kassa24 and Mobile Commerce payment methods
• Removed section on payments processing by using the LiqPay payment method. Payment processing by using this method is currently unavailable

• Added sections on payment processing by using CepBank, GlobePay e-wallet, Hizli QR payment methods
• Updated API Gate specification:
  • added the endpoints for new payment methods
  • updated the endpoints for the CUP payment methods
• Updated sections on payment processing by using Kassa24 and Mobile Commerce payment methods.
• Removed section on payments processing by using the LiqPay payment method. Payment processing by using this method is currently unavailable

• Added the Payment Page request formats section
• Updated the Payment request formats section. The key updates include the following:
  • The customer-related parameters are conveniently broken into groups.
  • The region_code parameter in the shipping object is hidden and may not be used until further notice
• Added the information about fallback to when the 3‑D Secure 2 authentication fails into the following sections: Frequently asked questions, 3‑D Secure 2 workflow in Payment Page, and 3‑D Secure 2 workflow in Gate

• Added response code 3288 in the section Information of operations performing
• Added test cards supporting 3-D Secure 2 for Challenge Flow in case the 3-D Secure 2 protocol is not supported by the issuer and authentication is performed using the 3-D Secure 1 protocol. For more information, see Test cards
• Removed section on payments processing by using Instant Banking payment method, since the method is no longer supported

• Added response code 3288 in the section Information of operations performing
• Added test cards supporting 3-D Secure 2 for Challenge Flow in case the 3-D Secure 2 protocol is not supported by the issuer and authentication is performed using the 3-D Secure 1 protocol. For more information, see Test cards
• Removed section on payments processing by using Instant Banking payment method, since the method is no longer supported

Removed sections on payments processing by using Rapid Transfer, Nordea Solo, and Paysafecard payment methods, since the methods are no longer supported

Removed sections on payment processing by using 7-Eleven, MOLPay, SafetyPay payment methods, since the methods are no longer supported

Removed sections on payment processing by using 7-Eleven, MOLPay, SafetyPay payment methods, since the methods are no longer supported

• Added the section with Test cards

• Added the section about payments by using Banks of Korea payment method
• Added purchase parameters with customer data for the following payment methods:
  • Banks of Indonesia
  • Banks of Malaysia
  • Banks of Thailand
  • Banks of Vietnam
• Added information on iframe size settings when Opening Payment Page embedded in a web page

• Added the section about payments by using Banks of Korea payment method
• Added the section about payouts processing by using CUP QuickPay payment method
• Deleted information on second channel for payouts processing by using CUP Banks and CUP P2P payment methods
• Added purchase parameters with customer data for the following payment methods:
  • Banks of Indonesia
  • Banks of Malaysia
  • Banks of Thailand
  • Banks of Vietnam

• Updated the API specification
• Added the information on purchases processing by using WeChat payment method
• Added the information on refunds processing by using Alipay payment method
• Added the 3183 code in Information of operations performing

• Removed sections on payment processing by using the Moneta.ru Wallet and Promsvyazbank payment methods. Starting from 01.11.2019 payment processing by using these methods is no longer available.
• Deleted the section on payment processing by using the China Banks payment method, as the payments using this method are supported in the framework of CUP Banks method.

• Removed section on payment processing by using the Moneta.ru Wallet payment method. Starting from 01.11.2019 payment processing by using this method is unavailable
• Added the information on COF payments processing by using Yandex.Money payment method
• Restored the information on refunds processing by using Alfa-Click and Yandex.Money payment methods
• Deleted the section on payment processing by using the China Banks payment method, as the payments using this method are supported in the framework of CUP Banks method

• Added test card numbers in the Frequently asked questions section.
• Extended notification format description in the Format of authentication result notification section.
• Updated the brief presentation that is provided a quick overview of 3‑D Secure 2 support by the ECommPay platform in the 3-D Secure 2 section.

• Updated the information on integration by using SDK version 1.2. For more information, see SDK for Android and SDK for iOS
• Updated the CMS OpenCart 3.0 plug-in file. The new version includes fixes of minor issues

• Added the descriptor and moto_type parameters in the list of Payment Page invocation parameters
• Added the information on the MO/TO Payment Processing

• Updated the information on the purchase request format for the Vietnamese QR banking and Card payments via partner (Russia) payment methods
• Added section on payment processing by using the Bancontact payment method

• Updated the information on the purchase and payout request formats for the Card payments via partner (Russia) payment method
• Added section on payment processing by using the Bancontact payment method

• Added the information on the WebMoneyClassic purchases by using the X20 interface. For more information, see WebMoney
• Removed section on payment processing by using the Kazpost and Sberbank Online payment methods. Payment processing by using these methods is currently unavailable.

• Updated sections on payment processing by using Gate: updated and expanded the One-time purchase processing, Payout, Payment instrument verification sections; added the Auxiliary procedures section containing information on procedures which may be required for payment processing.
• Removed section on payment processing by using the Sberbank Online payment method. Payment processing by using this method is currently unavailable.

Updated the information on data formats which are used in the 3‑D Secure 2 protocol.

1. The following parameter titles where updated in the Payment request formats section:
   • changes_date changed to hange_date,
   • pass_changes_date changed to pass_change_date,
   • acs_trans_ID changed to acs_operation_id,
   • prev_auth_method changed to authentication_flow,
   • prev_auth_timestamp changed to authentication_timestamp.
2. The following objects and parameters were added to the same section:
   • the mpi_result object,
   • parameters age_indicator, payment_age_indicator, change_indicator, pass_change_indicator in the account object,
   • parameter address_match in the customer object,
   • parameter address_usage_indicator in the shipping object,
   • parameters region_code in the shipping and billing objects.
3. The mandatory threeds_completion_indicator parameter was added to the Format of authentication initiation request section.
4. The authentication_flow parameter was added to the Format of callback with the payment result section. Additionally, the following parameter titles were updated:
   • mpi_id changed to mpi_operation_id,
   • ds_id changed to ds_operation_id,
   • acs_id changed to acs_operation_id.

• Added section on payout processing by using the African Banks payment method
• Added information on P2P payout processing in the section Payout

• Added section on purchase processing by using the China UnionPay payment method
• Updated lists of the mandatory parameters for payment processing by using CUP P2P and CUP Banks payment methods

• Added information about the merchant.descriptor parameter in the section Using optional parameters for payments processing
• Added the 20205 code in Information of operations performing

• Added the information about alternative way of bank selecting and updated the lists of mandatory parameters for the following payment methods:
  • Banks of Indonesia
  • Banks of Malaysia
  • Banks of Thailand
  • Banks of Vietnam
• Added callback parameters containing RCS responses, payment provider data and parameters in card, recurring objects. For more information, see in Callbacks
• Added the 20802 code in Information of operations performing

• Added the information about alternative way of bank selecting and updated the lists of mandatory parameters for the following payment methods:
  • Banks of Indonesia
  • Banks of Malaysia
  • Banks of Thailand
  • Banks of Vietnam
• Added callback parameters containing RCS responses, payment provider data and parameters in card, recurring objects. For more information, see in Callbacks
• Added the 20802 code in Information of operations performing

Added the hide parameter in the list of Payment Page invocation parameters

• Added sections on payment processing by using the Boleto, CashtoCode, Oxxo, Pago, Rapipago, Safetypay payment methods
• Updated sections on payment processing by using the eNets, EPS, Multibanco, Skrill Wallet payment methods

• Updated CMS plug-ins files. New versions provide opportunities for traffic analysis and further optimization of payment forms on the ECommPay side

• Added sections on payment processing by using the Boleto, CashtoCode, Oxxo, Pago, Rapipago, Safetypay payment methods
• Updated sections on payment processing by using the eNets, EPS, Multibanco, Skrill Wallet payment methods

• Updated CMS plug-ins files. New versions opportunities for traffic analysis and further optimization of payment forms on the ECommPay side

• Updated lists of the mandatory parameters for payment processing by using CUP QuickPay payment method
• Updated information on payment processing by using the CUP P2P and CUP Banks payment methods: added information on second channel for purchase processing

• Updated lists of the mandatory parameters for payment processing by using CUP QuickPay payment method
• Updated information on payment processing by using the CUP P2P and CUP Banks payment methods: added information on second channel for purchase processing

• Added new parameters for returning customers to project while payment performing. For more information, see Payment Page invocation parameters
• Updated the information about Options for returning customers to project after payment

• Added information in the Test cards section
• Added Information of operations performing: 3303, 3305-3340

• Added sections on payment processing by using the GiroPay and iDEAL payment methods
• Added Information of operations performing: 3303, 3305-3340

Updated list of the mandatory parameters for purchase processing by using the Przelewy24 payment method

• Updated lists of the mandatory parameters for purchase and payout processing in the CUP Banks section
• Updated list of the mandatory parameters for purchase processing in the CUP P2P section

• Updated overview in section on payment processing by using the Dragonpay payment method
• Updated information on integration by using SDK for SDK version 1.1. For more information, see SDK for Android and SDK for iOS

Published a new version of the Gate OpenAPI specification. Also, considerably improved the navigation experience by replacing endpoint descriptions with endpoint paths and breaking the list of endpoint paths in the left pane into groups.

For the specification of the Gate API, see API Reference.

• Added sections on payment processing by using the following payment methods: Klarna (Sofort), Multibanco
• Updated sections on payment processing by using the following payment methods: Alipay, GiroPay, iDEAL, Przelewy24

• Added sections on payment processing by using the following payment methods: Klarna (Sofort), Multibanco, SEPA
• Updated sections on payment processing by using the following payment methods: Alipay, GiroPay, iDEAL, Przelewy24

• Added sections on payment processing by using the JetonGo and Jeton Wallet payment methods
• Added sections on payment processing by using the Vietnamese OTC (over the counter) payment method

• Added sections on payment processing by using the JetonGo and Jeton Wallet payment methods
• Added sections on payment processing by using the Vietnamese OTC (over the counter) payment method

• Refactored sections about integration by using Gate, such as Overview, Interaction concepts, and Payment models and statuses
• Updated and extended section about One-time purchase processing

• Added section on payment processing by using the Vietnamese QR banking payment method.
• Updated information on payment processing by using the Vietnamese ATM cards (NAPAS) payment method: added information on second channel for purchase processing.
• Updated information on payment processing by using the Banks of Vietnam payment method: added information on second channel for purchase processing.

• Added section on payment processing by using the Vietnamese QR banking payment method.
• Updated information on payment processing by using the Vietnamese ATM cards (NAPAS) payment method: added information on second channel for purchase processing.
• Updated information on payment processing by using the Banks of Vietnam payment method: added information on second channel for purchase processing.
• Added information on the customer redirection data for the QIWI Wallet payment method.

• Convenience stores in Thailand
• Boost Wallet
• EPay
• MCash Wallet

• Convenience stores in Thailand
• Boost Wallet
• EPay
• MCash Wallet

Added section on payment processing by using the CUP QuickPay payment method

Added section on payment processing by using the CUP QuickPay payment method

Updated information on payment flow for the CUP QuickPay payment method

• Added the section about using addendum data in payment requests and the information about the parameters intended to pass addendum data. For more information, see Addendum with itinerary data in Payment Page and Payment Page invocation parameters
• Added the information on the callback parameters with the information on a card issuer bank. For more information, see Callbacks

• Added the section about using addendum data in payment requests and the information about the parameters intended to pass addendum data. For more information, see Addendum with itinerary data in Gate and Addendum parameters in the Gate API
• Added the information on the callback parameters with the information on a card issuer bank. For more information, see Callbacks

Added section on payment processing by using the Alipay payment method

Updated information about required for purchase requests by using the Alipay payment method

• Added section on payment processing by using the CUP Banks payment method
• Added information about removing limits to how deep JSON objects can be nested. For more information, see Signature generation and verification
• Updated information about supported banks on payout processing by using the CUP Banks payment method

• Added the information on the cascading_with_redirect callback parameter and receiving multiple callbacks when conducting 3D Secure authentication. For more information see Callbacks
• Added section on payment processing by using the CUP Banks payment method
• Updated information about supported banks on payout processing by using the CUP Banks payment method
• Added information about removing limits to how deep JSON objects can be nested. For more information, see Signature generation and verification

• Added sections on payment processing by using:
  • Convenience stores in Indonesia
  • DOKU Wallet
• Updated the section about payment processing by using the Banks of Indonesia payment method

• Added sections on payment processing by using:
  • Convenience stores in Indonesia
  • DOKU Wallet
• Updated the section about payment processing by using the Banks of Indonesia payment method

• SDK for Go
• SDK for JavaScript
• SDK for PHP
• SDK for Python

Added the information on supported mobile device resolution for applications made by using SDK for Android.

• Added the information on supported mobile device resolution for applications made by using SDK for Android.
• Added the information on mandatory parameters for Payment Page using Neteller payment method.

• Added the information on minimum size of the iframe. For more information, see Operation modes
• Added the section describing software development kits (SDK) for development of web services which are capable of integrating with the ECommPay payment solutions. For more information, see: SDK for Java

• Added a supported card type – Belcard
• Added the information on purchase from a customer card to a merchant wallet availability. For more information, see Purchase processing

• Added a supported card type – Belcard
• Added the information on purchase from a customer card to a merchant wallet availability. For more information, see One-time purchase processing
• Added the information on 10505 and 10204 unified response codes. For more information, see Information of operations performing

Added a section describing two software development kits (SDK) that allow you to build customer checkout experience right into your mobile apps you develop for Android and iOS:

• SDK for Android
• SDK for iOS

• Added the section about payments processing by using QIWI Kazakhstan payment method
• Added the information on 2701 and 2466 unified response codes. For more information, see Information of operations performing

• Added the information on bank card authorization. For more information, see One-time purchase processing
• Added the information on 10504 and 3020 unified response codes. For more information, see Information of operations performing

• Added new test card data. For more information, see Test cards.
• Added the sections about payments processing by using the following payment methods:
  • Alfa-Click
  • Cash-in
  • Yandex.Money

• Alfa-Click
• Cash-in
• Yandex.Money

• CUP Banks
• CUP P2P
• CUP QuickPay

• CUP Banks
• CUP P2P
• CUP QuickPay

• Nganluong Wallet
• Vietnamese ATM cards (NAPAS)

• Nganluong Wallet
• Vietnamese ATM cards (NAPAS)

• Klarna (Sofort)
• Przelewy24

• LiqPay

• Updated the information about JavaScript callback functions. For more information, see Handling customer behaviour events on Payment Page.
• Added dwescription of the identify_doc_number parameter. For more information, see Payment Page invocation parameters.

• Added of the section on payments by using CepBank payment method
• Added of the information on the interface_type parameter. For more information, see Payment Page invocation parameters
• Added of the information on the callback parameters in the redirect_data and interface_type objects. For more information, see Callbacks

• Added of the section on payments by using Dragonpay payment method
• Added of the information on the callback parameters in the redirect_data and interface_type objects. For more information, see Callbacks

• Banks of Indonesia
• Banks of Malaysia
• Banks of Thailand
• Banks of Vietnam
• China Banks

• Banks of Indonesia
• Banks of Malaysia
• Banks of Thailand
• Banks of Vietnam
• China Banks

• Banks of Indonesia
• Banks of Malaysia
• Banks of Thailand
• Banks of Vietnam
• China Banks

• Update the table of the general codes from Gate in the section Information of operations performing.
• Addition of the supported banks list for CepBank payment method.

• Update the table of the general codes from Gate in the section Information of operations performing.
• Addition of the supported banks list for CepBank payment method.

• Update the information in the section Information of operations performing.
• Addition of the sections on payments via:
  • EPS
  • GiroPay
  • iDEAL
  • Nordea Solo
  • Poli
  • Przelewy24
  • Rapidtransfer
  • Klarna (Sofort)
  • Trustly

• Update of the list of callback parameters. For more information, see Callbacks.
• Addition of the section with reference information about Electronic Commerce Indicator. For more information, see Electronic Commerce Indicator (ECI) codes.
• Addition of the section on payments via CepBank.

• Update of the list of callback parameters. For more information, see Callbacks.
• Addition of the section with reference information about Electronic Commerce Indicator. For more information, see Electronic Commerce Indicator (ECI) codes.
• Addition of the section on payouts via CepBank.

• Update of the list of parameters to pass Payment Page. For more information, see Payment Page invocation parameters.
• Update of the list of parameters to pass for gathering additional customer data to pass. For more information, see Collecting customer data.

• Addition of the section on payments via Apple Pay.
• Addition of the section on payouts via iWallet.

• Update the information about payments via Apple Pay.
• Addition of the section on payments via iWallet.

• Addition of information about receiving card data by token. For more information, see Using tokens.
• Addition of section on payments via iWallet.

• Addition of information about the clarification of parameters. For more information, see Submission of additional payment information.
• Addition of section on payments via CUP Banks.

• Addition of information about payouts on bank cards issued not in Russia. For more information, see Payout.
• Addition of section on payouts via CUP Banks.

• Update the Information of operations performing.

• Addition the information on COF payments. For more information, see COF purchase registration.
• Update of the list of callback parameters. For more information, see Callbacks.
• Addition of the list of result codes after checking with AVS. For more information, see Checking with Address Verification Service.

• Update of Swagger contract version. For more information, see API.
• Update of the list of callback parameters. For more information, see Callbacks.
• Addition of the list of result codes after checking with AVS. For more information, see Checking with Address Verification Service.

• Addition of Data API used for dowloading data from Old Dashboard. For more information, see Retrieving data with Data API, Data API Description, and Data API.
• Addition of the API Tokens block to My Account. For more information, see API Tokens.

• Alfa-Click
• ATF24
• Kassa24
• Kassa24
• RBK Bank KZ

• Update the section Information of operations performing.

• Addition of the information about sending a request for mass capture and cancel operations processing. For more information, see Bulk payments.
• Addition of the information about settings of regular reports. For more information, see Working with subsection tables.
• Addition of the section Information of operations performing.

• Update the section Information of operations performing.
• Update of Swagger contract version. For more information, see API.

• Update of Swagger contract version. For more information, see API.
• Exclusion of the Verification of Bank Cards section due to revision the functionality.

• Jeton Voucher
• Jeton Wallet

• Jeton Voucher
• Jeton Wallet

• Mobile Commerce
• QIWI Wallet

• Mobile Commerce
• QIWI Wallet
• Yandex.Money

• Addition of information about mass refunds in Bulk payments and specification of parameters mandatory.
• Addition of the subsection Balance.

• eNets
• WeChat

• Update of Swagger contract. For more information, see API.

• Update of the Swagger contract version. For more information, see API.

• Addition of section on choosing a payment system for the customer. For more information, Preselecting payment method.

• Change in validation of the customer.billing.country in the Swagger contract.

• Update of the list of supported parameters. For more information, see Payment Page invocation parameters.
• Addition of the section Verify Card Mode.

• Update of the list of supported parameters. For more information, see Payment Page invocation parameters.
• Update of the section Payments with payment cards in Payment methods.

• Update of the section Additional capabilities.
• Update of the Swagger contract version. For more information, see API.

• Addition of the sections Collecting customer data and Checking with Address Verification Service.
• Update of the list of supported parameters. For more information, see Payment Page invocation parameters.
• Update of the section Handling customer behaviour events on Payment Page.

• Addition of the sections Additional payment information submission and Checking with Address Verification Service.
• Update of the section Purchase refund.
• Update of the Swagger contract version. For more information, see API.

• Addition of the section Customers.
• Actualization of the section Payments.

• Update of the Options to open Payment Page section.
• Actualization of the list of supported payment systems. For more information, see Payment methods.

• Addition of revoking of bank card tokens. For more information, see Using tokens.
• Changes in the list of callback parameters after generating or revoking a token. For more information, see Callbacks.

• Elaboration of callback delivery periods. For more information, see Callbacks.
• Change of mandatory status of the customer_id parameter. For more information, see Payment Page invocation parameters.

• Change of the request URL in Gate. For more information, see Request format.

• Change of the request URL in Gate. For more information, see Request format.
• Support for limiting the maximum of saved payment accounts per customer. For more information, see One-time purchase processing.
• Addition of payments by using tokens. For more information. see One-time purchase processing and Using tokens.
• Removal of information about sandbox. The functionality is in development.
• Addition of unified response code for Gate. For more information, see Information of operations performing and Callbacks.

• Support for limiting the maximum of saved payment accounts per customer. For more information, see Saving customer payment data.
• Addition of payments to customers by using tokens. For more information, see Payments by using tokens.
• Updates in the Test cards section.
• Addition of unified response code for Payment Page. For more information, see Information of operations performing and Callbacks.
• Addition of Basic URLs to Payment Page API Description.

• Parameter payment_sum was renamed to payment_ammount.
• The following sections have been added: Callbacks, Errors messages, Formats and data types, Currency conversion, Test cards.

• Publication of API v.2.4.1.
• Addition of a section Callback processing.

• Changes in the set of the parameters that are sent in callbacks. For details, see Callbacks.
• Addition of statements about the changes in the sets of the response and callback parameters.

• Changes in the set of the parameters that are sent in callbacks. For details, see Callbacks.
• Addition of statement about the changes in the callback parameters.
• Added the ability for customers to repeat an attempt to perform a payment in the Purchase and Cashier modes. For details, see Try Again button: retry to perform payment.

• Parameter payment_sum was renamed to payment_amount.
• The following sections have been added: Callbacks, Errors messages, Formats and data types, Currency conversion, Test cards.