What's new: archive

• Added information about the recipient_day_of_birth parameter to the Parameters for opening the payment form article.
• Made minor edits to different articles.

• Made revisions pertaining to the day_of_birth parameter for working with the Visa payment system.
• Updated the Gate API specification: in version 3.32.11 included the day_of_birth parameter in the recipient object.

• Made revision to the article about payment link purchases and added updated illustrations.
• Updated the Gate API specification: in version 3.32.9 removed the installment_count and installment_plan parameters.

• Updated illustrations in Overview and Quickstart as well as in the articles of UX configuration.
• Made edits to articles describing working with the language_code parameter.

• Updated some illustrations in the article about using the ecommpay plugin for the BigCommerce CMS (details).
• Updated the Dashboard interface illustration used in the Specifying extended purchase data for subsequent merchant use article.

• Added the article about working with SDK React Native for Android and iOS.
• Revised examples of code in the articles about integration with SDK.

• Made minor edits to different articles.
• Updated the Dashboard interface illustrations used in different articles.

• Added an article about performing payouts via Payment Page (details).
• Updated several articles of the section: added information about performing payouts.

• Updated the Data API specification: in version 2.0.13 made revisions to descriptions of different parameters.
• Updated the article about retrieving data: made minor edits and added the information about the /financial-reporting/operations endpoint used to retrieve itemised operation data for financial reporting (including charged fees).

• Added an article about working with the Click to Pay payment method.
• Updated the structure of the section.

• Updated the article Paypal: added information about registering of COF purchases by using Payment Page.
• Removed materials about working with the Neteller (legacy) and Skrill Wallet (legacy) payment methods because these methods are no longer supported.

• Updated the Gate API specification: in version 3.32.4 updated the information about the parameters required for initiating card payments.
• Made minor edits to different articles.

• Updated the article about integration using a microframe solution: revised the description of the setup procedure and message handling.
• Made minor edits to the Different options to arrange payment methods on the page article.

• Updated the information about the parameters required for initiating card payments.
• Made minor edits to different articles.

• Removed articles about working with several payment methods because these methods are no longer supported.
• Updated the Gate API specification: in version 3.32.1 removed several irrelevant endpoints.

• Revised the articles about working with the following payment methods:
  • Open Banking in Austria
  • Open Banking in Belgium
  • Open Banking in Estonia
  • Open Banking in Finland
  • Open Banking in France
  • Open Banking in Germany
  • Open Banking in Greece
  • Open Banking in Hungary
  • Open Banking in Latvia
  • Open Banking in Lithuania
  • Open Banking in the Netherlands
  • Open Banking in Norway
  • Open Banking in Poland
  • Open Banking in Portugal
  • Open Banking in Romania
  • Open Banking in Spain
  • Open Banking in Sweden
  • Open Banking in the UK
• Added the article about working with the Open Banking payment method group.
• Removed the articles about working with Giropay and Hong Kong Virtual Account because these methods are no longer supported.

• Expanded the Boost Wallet, Coins.ph, GrabPay, Maya, Shopee, Touch&Go articles: added illustrations of customer payment scenarios via Payment Page.
• Added the information about working with the MoMo Wallet and TrueMoney payment methods.

• Added an article about checking payment method availability (details).
• Updated the Gate API specification: in version 3.32.0 added the /v2/info/available-methods/{payment_direction}/list endpoints that can be used for checking payment method availability.

• Updated article about working with the Klarna payment method: updated information about the required parameters used in requests.
• Updated the codes of preselecting the Direct Debit BACS and Direct Debit SEPA payment methods on Payment Page.

• Updated Glossary: added several terms related to working with payment cards.
• Added the Payment card codes reference with the information about these codes.
• Revised the Region codes for card payments reference: made textual edits and supported the option of reading the article in full or short version.
• Updated Language codes, Currency codes, and Country codes: made revisions and minor textual edits.

• Updated the article about payment processing by using the OVO Wallet payment method—added information about a new channel for purchase processing.
• Updated articles about working with the Indonesian Virtual Accounts and QRIS payment methods: updated information about the required parameters used in requests.

• Updated information about iDeal, Sofort and Klarna payment methods, as they are not currently supported.
• Removed the articles about working with several methods because these methods are no longer supported.

• Added the articles about working with the Shopee and Touch&Go payment methods.
• Updated the article about working with the GrabPay payment method: updated the list of available regions and currencies, as well as information about the required parameters used in requests.

• Updated SDK for C# on the .NET platform: removed information about testing because this capability is temporarily not supported.
• Made minor edits to the SDK for JavaScript article.

• Updated the title of the Payouts to bank accounts in other countries payment method to Payouts to bank accounts in different countries.
• Made minor edits to the Payouts to bank accounts in different countries article.

• Updated Specifying extended purchase data for subsequent merchant use: described the capability to specify booking information.
• Updated Parameters for opening the payment form: added the booking_info parameter used for specifying booking information.

• Updated Specifying extended purchase data for subsequent merchant use: described the capability to specify booking information.
• Updated the Gate API specification: in version 3.31.0 added the booking_info object that can be used in requests to a number of endpoints to pass booking data.

• Made revisions to the article about signature generation and verification.
• Made minor textual edits to different articles.

• Made revisions to the article about purchase refunds (details).
• Made minor textual edits to different articles.

• Open Banking in Hungary
• Open Banking in Poland
• Open Banking in Norway
• Open Banking in Romania

• Updated the ‘Callbacks’ article: added information about the recurring_retry object and its parameters related to debiting retry attempts (the object is inside the operation object).
• Updated the article ‘Information of operations performing’: added the 3186 response code used when the operation is declined because the identifier of the debit operation that requires cancelling retry attempts was not found.

• Expanded the COF purchase with automatic debiting article: added information about retry attempts of a declined scheduled automatic debiting.
• Updated the ‘Callbacks’ article: added information about the recurring_retry object and its parameters related to debiting retry attempts (the object is inside the operation object).
• Updated the article ‘Information of operations performing’: added the 3186 response code used when the operation is declined because the identifier of the debit operation that requires cancelling retry attempts was not found.
• Updated the Gate API specification: in version 3.30.0 added the /v2/recurring/retry_stop endpoint to cancel debiting retries and for endpoints /v2/payment/card/recurring/info added response parameters for debiting retry attempts.

• Alipay
• Bancontact
• Banks of Hong Kong
• Banks of the Philippines
• Blik
• Boost Wallet
• Coins.ph
• China UnionPay
• CUP Banks
• CUP P2P
• CUP Quickpay
• EPS
• GrabPay
• Hong Kong Virtual Account
• Multibanco
• Philippines Over the Counter & ATM
• Philippines Payment Centers
• Poli
• Przelewy24
• Trustly
• Payouts to bank accounts in SEPA
• Payouts to bank accounts in different countries
• Local payouts to bank accounts in the UK
• Mobile Commerce in the United Kingdom
• and other payment methods

• Updated the article about the payment retries functionality: added revisions and expanded illustrations of possible user scenarios.
• Removed the information about opening the payment form on several devices because this capability is no longer supported.

• Updated the Data API specification: in version 2.0.11 added the /currency-rates/get endpoint to retrieve reference information on currency conversion rates.
• Updated the article about Retrieving data: added the information about the /currency-rates/get endpoint to retrieve reference information on currency conversion rates.

• Added an article about specifying extended purchase information for subsequent use by the merchant (details).
• Updated the description of the merchant_data parameter in the table with the parameters for opening the payment form.

• Added an article about specifying extended purchase information for subsequent use by the merchant (details).
• Updated the Gate API specification: in version 3.26.2 made revisions to the description of the merchant object as well as the descriptor and data parameters contained in this object.

• Expanded the Indonesian Online Banking, Malaysian Online Banking, Singapore Online Banking, Thai Online Banking, Vietnamese Online Banking articles: added illustrations of customer payment scenario via Payment Page.
• Updated the Apple Pay article: added information about payout processing.

• Updated the article ‘Callbacks’: added information about the scheme_id parameter that can be passed in the callbacks when COF purchases are registered.
• Made minor textual edits to different articles.

• Updated the Banks of the Philippines article: updated illustrations of customer payment scenario via Payment Page.
• Expanded the GCash article: added illustrations of customer payment scenario via Payment Page.

• Updated the Data API specification: in version 2.0.10 for the endpoint /operatios/get, added the information about the time of request processing in certain cases.
• Made revisions related to the handling of a request for information about operations processed over a specified period, in the article Retrieving itemised operation data for general purposes.

• Amazon Pay
• Boleto
• Cash and online banking payments in Brazil
• Cash and online banking payments in Mexico
• Convenience stores in Indonesia
• pm_cup_qr.html
• DOKU Wallet
• Hong Kong FPS QR
• Neteller
• pm_oxxo.html
• pm_pago.html
• QRIS
• pm_rapipago.html
• Skrill Wallet
• Vietnamese QR banking
• Vietnamese OTC (cash payments)
• WeChat

• Expanded the Banks of the Philippines article: added illustrations of customer payment scenario via Payment Page.
• Made minor edits to the Klarna article.

• Apple Pay
• Giropay
• Google Pay
• GCash
• iDeal
• Indonesian Online Banking
• Indonesian Virtual Accounts
• Malaysian Online Banking
• OVO Wallet
• Paypal
• Promptpay
• Thai Online Banking
• Vietnamese Online Banking
• Vietnamese ATM cards (NAPAS)

• Updated the Data API specification: in version 2.0.9, for endpoints /chargeback/list and /chargeback/get, added request and response parameters for working with chargebacks, and for the /chargeback/get endpoint, added the filter object.
• Updated the information about retrieving chargeback information via the Data API (details).

• Added the 1415 response code used when operations are declined due to risk assessment performed by ecommpay.
• Added response codes 3618–3635 used in Mastercard MoneySend payment processing.
• Removed obsolete codes.
• Made minor textual edits.

• Updated the article ‘Information of operations performing’:
  • Added the 1415 response code used when operations are declined due to risk assessment performed by ecommpay.
  • Added response codes 3618–3635 used in Mastercard MoneySend payment processing.
  • Removed obsolete codes.
  • Made minor textual edits.
• Updated the Gate API specification: in version 3.26.0 added the merchant object that can be used in requests to a number of endpoints and revised the rules for specifying the pan parameter in the RecipientForCard model. In addition, made minor edits and removed obsolete models.

• Updated information about processing payment link purchases and registering COF purchases: added description of the capability to register COF purchases when processing payment link purchases.
• Updated the Gate API specification: in version 3.25.2, added the recurring object that can be used in requests to endpoints /v2/payment/invoice/create and/v2/payment/card/token/create.

• Updated the article Currency conversion: made revisions and added information about the option when the customer selects the payment currency.
• Updated the article ‘Information of operations performing’: added response codes 3362 used in Mastercard MoneySend payment processing and 10206 used when payments are declined due to risk assessment performed by the external provider.

• Made revisions to Currency conversion.
• Updated the article ‘Information of operations performing’: added response codes 3362 used in Mastercard MoneySend payment processing and 10206 used when payments are declined due to risk assessment performed by the external provider.
• Added the article on migrating information about COF purchases and payment card tokens from the services of other acquirers to the ecommpay payment platform (details).

• Added information about payment confirmation to several methods:
  • Open Banking in Austria
  • Open Banking in Belgium
  • Open Banking in Finland
  • Open Banking in France
  • Open Banking in Germany
  • Open Banking in Greece
  • Open Banking in Portugal
  • Open Banking in Spain
  • Open Banking in the Netherlands
• Made minor edits to the Open Banking in Estonia, Open Banking in Latvia, Open Banking in Lithuania, Open Banking in the UK articles.

• Updated the AVS response codes used when processing payments made with Visa cards (details).
• Updated the article ‘Information of operations performing’: added the 3617 response code used in decline messages for payments made with Visa cards that have product code F2.

• Updated the AVS response codes used when processing payments made with Visa cards (details).
• Updated the article ‘Information of operations performing’: added the 3617 response code used in decline messages for payments made with Visa cards that have product code F2.

Added the capability to display subject-specific selections of links to the sections and articles of the documentation compiled on the basis of answers to questions about relevant user and payment processing scenarios.

The survey and the resulting selections are currently available on the homepage and are expected to be available on every page of the documentation in the future.

• Updated the article ‘Information of operations performing’: added the 10114 response code used when the payment is declined following the 3‑D Secure authentication attempt.
• Added information about using Mastercard MoneySend and Visa Direct services to simplify transferring money between customers and merchants.
• Updated the Gate API specification: in version 3.25.0, added the recipient object that can be used in requests sent to the following endpoints: /v2/payment/card/sale, /v2/payment/card/sale/saved, /v2/payment/card/sale/token, /v2/payment/applepay/sale, and /v2/payment/googlepay/sale.
• Removed information about processing card-to-card money transfers because this functionality is now supported as part of using the Mastercard MoneySend and Visa Direct services.

• Open Banking in Estonia—online-estonian-banks
• Open Banking in Latvia—online-latvian-banks
• Open Banking in Lithuania—online-lithuanian-banks
• Open Banking in the Netherlands—online-netherlands-banks

• Made minor edits to the Sofort article.
• Updated information about available currencies for the Open Banking in Poland payment method.

Updated the articles about the 3‑D Secure authentication: made minor edits and added the short version of this article (details).

• Updated the article about checking current payment information: added the description of the capability to receive status information for an individual payment by its request id.
• Updated the Gate API specification: in version 3.24.5, added the /v2/payment/status/request endpoint to receive payment status of an individual payment by its request id.

• Updated information about supported regions and available currencies for the Sofort payment method.
• Made minor edits to several articles of the section.

• Updated the article about the monitoring balances: added the information about the monitoring of conversion rates and made minor edits.
• Updated the article about managing projects.

• Updated the article about signature generation and verification: updated code examples and supported JavaScript as an option to input data in the signature generation form.
• Updated information about using mobile SDKs: updated links in the articles about SDK UI & Core and code examples in the articles about SDK Core (details).

• Updated article about working with the Maya payment method: updated information about the required parameters used in requests.
• Updated the articles about working with the payment methods Coins.ph, GCash, and GrabPay: made revisions and minor edits to these articles

• Added the article about working with the 3‑D Secure authentication (details).
• Updated the articles about working with SDK UI & Core for Android and for iOS: added information about the parameters used in the 3‑D Secure authentication process.

• Updated the home page of the section: the page now contains an overview and a list of methods which has an introduction, logos of methods, and a statement about the number of methods that correspond to the filtering conditions.
• Removed the articles about working with the methods Dragonpay, Mcash Wallet, and Nganluong Wallet, since these methods are no longer supported.

• Made revisions to the information about payment card verification performed with the use of the Mail Order / Telephone Order capabilities (details).
• Revised the article about data formats used during the work with the payment platform via Payment Page (with the full and short versions of the article supported; details).
• Removed the page about payment methods that was used for redirecting to the Methods section after this section was introduced.

• Revised the article about data formats used during the work with the payment platform via Gate (with the full and short versions of the article supported; details).
• Removed the page about payment methods that was used for redirecting to the Methods section after this section was introduced.

• Added information about payment card verification made by using the Mail Order / Telephone Order capabilities (details).
• Revised the home page of the subsection ‘Integration using SDK’ and rearranged the articles in this subsection (details).
• Extended information about using the force_payment_group parameter: made revisions to the articles Preselecting payment methods and Managing payment methods availability and to the reference Payment method codes.

• Added information about using payment card verification made by using the Mail Order / Telephone Order capabilities (details).
• Updated the Gate API specification: in version 3.24.2, added the moto_type parameter for the endpoints /v2/payment/card/account_verification and /v2/payment/card/account_verification/token.

• Added the article about working with the Blik payment method.
• Updated the Gate API specification: in version 3.24.1, added the endpoints /v2/payment/blik/sale and /v2/payment/blik/refund.

• Updated the Test cards article: removed information about the cards for testing payment scenarios with the 3‑D Secure 1 authentication, since testing of scenarios with this protocol version is no longer supported.
• Updated the article Checking current payment information: added the operation_fee object to the code examples.
• Updated the Gate API specification: in version 3.24.0, added the operation_fee object in the parameters of the response to the payment status request /v2/payment/status.

• Removed the article about working with the SEPA payment method, since this method is no longer supported.
• Added information about the capability to make payouts via complementary methods during the work with the Open Banking payment methods.

• Added the article about working with the PIX payment method.
• Updated the Gate API specification: in version 3.23.3, added the endpoints /v2/payment/pix/sale and /v2/payment/pix/payout.

• Added information about working with SDK for C# on the .NET platform.
• Updated the file of the plug-in for WordPress CMS.

• Updated and extended the article about options for redirecting customers to the web service (details).
• Removed information about working with nopCommerce plug-in, because this plug-in is no longer supported.

• Added section on payment processing by using the Singapore Online Banking payment method.
• Updated information about payment processing by using the Indonesian Virtual Accounts payment method.
• Updated information about processing payments with the use of the Banks of South-East Asia methods:
  • Indonesian Online Banking
  • Malaysian Online Banking
  • Thai Online Banking
  • Vietnamese Online Banking

• Added section on payment processing by using the Singapore Online Banking payment method.
• Updated information about payment processing by using the Indonesian Virtual Accounts payment method.
• Updated information about processing payments with the use of the Banks of South-East Asia methods:
  • Indonesian Online Banking
  • Malaysian Online Banking
  • Thai Online Banking
  • Vietnamese Online Banking

• Added response codes from Risk Control System (RCS) 1409-1410.
• Updated the Credential-on-file (COF) purchases section: added information about the capability of registering and processing autopurchases with the use of the /v2/payment/card/account_verification/token endpoint.
• Updated the Gate API specification to version 3.23.2: the stored_card_type parameter is now available for the /v2/payment/card/account_verification/token endpoint.

• Sections with information about payment method codes for Payment Page and Dashboard are combined in a joint section—Payment method codes.
• Removed the materials about working with several methods because these methods are no longer supported.

• Updated information about data formats for obtaining customer's consent for Open Banking payment methods
• Removed section on payments processing by using the Bitcoin payment method. Payment processing by using this method is currently unavailable.

• Updated information about the required parameters for specifying in requests when making payments by using the method Payouts to bank accounts in different countries.
• Updated the article about options for redirecting customers to third-party services (the article is available in full-length and short version: learn more).

Updated the Gate API specification to version 3.23.0:

• Revised the constraint validation criteria of the payment_id parameter.
• Made changes to the format of the responses to the recipient-account requests.

• Changed the structure of the Gate section and updated the pages with the information provided in this section: the home page, additional capabilities, and auxiliary procedures.
• Updated the information about the BELKART payment cards (details).

• Added section on payment processing by using the Open Banking in Greece payment method.
• Updated information about payment processing by using several payment methods.
• Updated the Gate API specification to version 3.17.2: removed several endpoints, which are not relevant.

• Added section on payment processing by using the Open Banking in Romania payment method.
• Updated the codes of preselecting payment methods on Payment Page for separate Open Banking methods.

• Updated the Core capabilities and role-based access model section: added the Designer role for customising the design of Payment Page.
• Updated the Retrieving data: added information about endpoints to retrieve chargeback data and retrieve the list of operations deemed as fraudulent.
• Updated the Data API specification to version 2.0.5: added new parameters payment_provider_code and payment_provider_message for /operations/get-by-payment and /operations/get endpoints.

• Updated information about payment processing by using the KakaoPay payment method: updated information about required parameters in purchase requests.
• Made the changes in the structure of the subsection Additional capabilities and auxiliary procedures and updated its home page. For more information, see Auxiliary procedures and additional capabilities.

• Updated information about limits in the Two-step purchase and Purchase refunds sections.
• Added response code 3117. For more information, see ‘Information of operations performing’

• Minor edits made in various articles, and short versions of these articles are available now.
• Updated the Support role rights. Managing subscriptions is not available anymore, but managing technical support bot is available now.

Supported a new feature: readers can now switch between the full-length and the short versions of same article using the () button of the top menu.

It is planned to implement this feature throughout the documentation portal.

• Updated the Gate API specification to version 3.16.1.
• Removed the materials about working with several methods because these methods are no longer supported.

• Updated the integration steps information related to the compliance with the PCI DSS requirements in the Interaction concepts section.
• Updated the SDK for Android (legacy) and SDK for iOS (legacy) sections: added the information about purchase processing by using the European Open Banking methods and extended the list of supported languages on the payment form.
• In the sections, where relevant, updated the information about the payment form customised design.

• Updated the integration steps information related to the compliance with the PCI DSS requirements in the Interaction concepts section.
• Updated the information about the payment form customised design in the Payment link purchases section.

• Updated the request format description in the One-step purchase section: added the information about the return_url object.
• Updated the description of the request format for authorisation hold in the Two-step purchase section: added the information about the return_url object.

• Added sections on payment processing by using the YooMoney, Tinkoff, Cash payments in different Eastern European and Central Asian countries payment methods.
• Updated information about payment processing by using the WebMoney, Mobile Commerce payment methods.
• Added information about payment testing for the Sberbank Online payment method.

• Added sections on payment processing by using the YooMoney, Tinkoff, Cash payments in different Eastern European and Central Asian countries payment methods.
• Updated information about payment processing by using the WebMoney, Mobile Commerce payment methods.
• Added information about payment testing for the Sberbank Online payment method.
• Updated the Gate API specification to version 3.15-4: added the /v2/payment/webmoney-light/refund and /v2/payment/mobile/refund endpoints.

• Updated the description of the payout request format (more).
• Updated the Gate API specification to version 3.15-3: added the purpose parameter to the payment object.

• Updated information about supported currencies in sections on payment processing by using several payment methods.
• Updated information about payment processing by using the Indonesian Virtual Accounts payment method: removed section on payment processing via the first channel, as it is no longer available.

• Updated information about supported currencies in sections on payment processing by using several payment methods.
• Updated information about payment processing by using the Indonesian Virtual Accounts payment method: removed section on payment processing via the first channel, as it is no longer available.

• Updated information about parameters used in payout requests in sections on payment processing by using the GCash, GrabPay and Maya payment methods.
• Updated the section on payment processing by using the Coins.ph payment method—added information about payout processing.

• Updated information about parameters used in payout requests in sections on payment processing by using the GCash, GrabPay and Maya payment methods.
• Updated the section on payment processing by using the Coins.ph payment method—added information about payout processing.

• Added section on payout processing by using the Payouts to bank accounts payment method.
• Added the description of the merchant_data parameter to the table of Parameters for opening the payment form.

• Updated the plug-in file for CMS WordPress.
• Made minor edits in the section.

• Updated the section about payment processing by using the WebMoney payment method—added information about the use of the payment.description parameter in purchase and payout requests.
• Added general response codes 3106, 3108-3112, 3118, 3291, 3299, 3341, 3411-3419 and codes from Risk Control System (RCS) 1435, 1457, 1462-1463, 1499.

• Updated the section about payment processing by using the WebMoney payment method—added information about the use of the payment.description parameter in purchase and payout requests.
• Added general response codes 3106, 3108-3112, 3118, 3291, 3299, 3341, 3411-3419 and codes from Risk Control System (RCS) 1435, 1457, 1462-1463, 1499.
• Updated the Gate API specification to version 3.15-1: added the country parameter to the account object of /v2/payment/qiwi/sale and /v2/payment/qiwi/payout endpoints; made minor edits to the descriptions of parameters.

• Updated the description of the payout request format (more).
• Added the 3612 response code. For more information, see ‘Information of operations performing’.
• Updated the Gate API specification to version 3.14-1: added parameters to the card/payout and card/payout/token requests.

• Added section on payment processing by using the FreeCharge Wallet payment method.
• Made minor edits in the GrabPay and Maya sections.

• Added section on payment processing by using the FreeCharge Wallet payment method.
• Made minor edits in the GrabPay and Maya sections.

• Updated the Core capabilities and role-based access model section: updated rights to access the Manual payments section and added rights to the Analytics and Project sections.
• Updated the Retrieving data and Data API specification to version 2.0-3: for the /operations/get endpoint the type of the operation_type parameter was changed and new parameters operation_status, customer_id and customer_email were added.

• Added information about returning funds to the sender's card as part of partial money transfer processing.
• Added response codes 3609-3611. For more information, see ‘Information of operations performing’.
• Updated the Gate API specification to version 3.13-1: added a new endpoint /v2/payment/card/money_transfer/in/refund to return debited funds as part of the partial money transfer and made minor edits to the parameter descriptions.

• Added information about payment testing for the Apple Pay and Google Pay payment methods.
• Removed section on payout processing with redirection of the customer by using the Trustly payment method, as this functionality is no longer supported.
• Updated the section about payment processing by using the CashtoCode payment method—updated lists of supported regions and currencies.

• Added information about payment testing for the Apple Pay and Google Pay payment methods.
• Removed section on payout processing with redirection of the customer by using the Trustly payment method, as this functionality is no longer supported.
• Updated the section about payment processing by using the CashtoCode payment method—updated lists of supported regions and currencies.

• Added information about testing to the Payment methods section.
• Made minor edits in the ‘Callbacks’ section.
• Updated the Test card section (details).

• Added information about testing to the Payment methods section.
• Made minor edits in the ‘Callbacks’ section.
• Updated the Test card section (details).

• Added information about payment testing for the CUP Banks, Indonesian Online Banking, Malaysian Online Banking, Thai Online Banking, Vietnamese Online Banking payment methods.
• Made minor edits in the Mobile Commerce section.
• Updated the information about using signatures.

• Added information about payment testing for the CUP Banks, Indonesian Online Banking, Malaysian Online Banking, Thai Online Banking, Vietnamese Online Banking payment methods.
• Made minor edits in the Mobile Commerce section.
• Updated the information about using signatures.

Updated the sections about payment processing by using the European Open Banking methods (more):

• Updated description of payment flow by using these payment methods.
• Added information about the need for obtaining additional consent of the customer for payment processing.
• Updated the list of supported banks for payment processing by using the Open Banking in Estonia payment method.
• Updated information about parameters used in purchase requests.

Also, added section on payment processing by using the pm_luxembourg.html payment method.

Updated the sections about payment processing by using the European Open Banking methods (more):

• Updated description of payment flow by using these payment methods.
• Added information about the need for obtaining additional consent of the customer for payment processing.
• Updated the list of supported banks for payment processing by using the Open Banking in Estonia payment method.
• Updated information about parameters used in purchase requests.

Also, added section on payment processing by using the pm_luxembourg.html payment method.

• Added section on payment processing by using the Maya payment method.
• Updated the section about payment processing by using the GrabPay payment method—added information about payout processing.
• Updated the information about currency conversion: National Bank of Georgia and National Bank of Serbia have been removed from the list of sources providing currency exchange rates—now the exchange rates of these banks are not supported within the payment platform (details).
• Made minor edits in the Banks of India and CUP Quickpay sections.
• Made minor edits in the section about generating signatures.

• Added section on payment processing by using the Maya payment method.
• Updated the section about payment processing by using the GrabPay payment method—added information about payout processing.
• Updated the information about currency conversion: National Bank of Georgia and National Bank of Serbia have been removed from the list of sources providing currency exchange rates—now the exchange rates of these banks are not supported within the payment platform (details).
• Made minor edits in the Banks of India and CUP Quickpay sections.
• Made minor edits in the section about generating signatures.

• Added the information about the capability to specify the sender's card details as a token in case of the partial money transfer workflow.
• Updated the Gate API specification to version 3.12-1: made minor edits for the endpoint /v2/payment/card/money_transfer/in in order to support the capability of specifying the sender's card details as a token.

• Added sections about payment processing by using the Banks of Hong Kong, Hong Kong FPS QR and Hong Kong Virtual Account payment methods.
• Updated Gate API specification up to version 3.9-1.

• Removed section about payment processing by using the Thailand QR Banking payment method. This method has been merged with the Promptpay method.
• Updated information about required parameters in requests for crediting funds as part of the partial money transfer processing.

• Added information about formats of requests for payouts on Visa cards issued in Canada (details).
• Updated information about formats of requests for the partial money transfer processing workflow.

• Updated and extended the section about preselecting payment methods. For more information, see Preselecting payment methods.
• Added the section about managing payment methods availability for payment processing. For more information, see Managing payment methods availability.

• Adding criteria to whitelists using payment information tabs.
• Combining search conditions in whitelists and blacklists.
• Using bank identification number (BIN) as a criterion.
• Customising basic set of columns in the registers of Payments and Risks sections.

• Updated the SDK for Android (legacy) section—updated information about version of SDK for Android (legacy) and supported payment methods.
• Updated the SDK for iOS (legacy) section—updated information about version of SDK for iOS (legacy), supported payment methods and SDK for iOS (legacy) compatibility requirements for mobile applications for iOS.

• Updated Gate API specification up to version 3.7.
• Added response codes 3297 and 3298. For more information, see ‘Information of operations performing’.

• Updated Card-to-card money transfers: added information about using the recipient's saved payment data to perform money transfers.
• Added response codes 3432-3439. For more information, see ‘Information of operations performing’.

• Updated the ‘Splitting payment amount’ section. Added information about splitting payout amount.
• Updated the section about payment processing by using the Banks of the Philippines payment method—updated information on supported banks and parameters used in purchase requests.

• Added sections about payment processing by using the Paytm and MobiKwik payment methods.
• Updated information about purchase processing by using the UPI payment method.

• Added sections about payment processing by using the Paytm and MobiKwik payment methods.
• Updated information about purchase processing by using the UPI payment method.

• Added section about payment processing by using the Neosurf payment method.
• Updated section about payment processing by using the Open Banking in the UK payment method—updated information on purchase processing.

• Added section about payment processing by using the Neosurf payment method.
• Updated section about payment processing by using the Open Banking in the UK payment method—updated information on purchase processing.

• Added information about performing payment link purchases and updated description of Data API. For more information, see Performing purchases and Retrieving data.
• Made minor edits in the section.

• changed the OpenAPI version from 2.0 to 3.0
• made edits to the responses for the end points /v2/customer/saved_account/list and /v2/customer/card/bytoken
• made other minor updates

• Updated the Data API specification:
  • removed the contract_name parameter in the 200 OK response of the endpoint for retrieving information about balances
  • updated description of the tz parameter in the request of the endpoint for retrieving information about operations
  • added examples of a request and its 200 OK response to each endpoint
• Added information about payout retry functionality

• Added sections about payments performing by using Airtel and PhonePe payment methods.
• Updated the section about Banks of India payment method—updated information about payout mandatory parameters.

• Added information about the Chargebacks section in the role-based access model. For more information, see Core capabilities and role-based access model.
• Updated information about showing details of IN balances in the Finance section. For more information, see Monitoring balances.

• Decommissioned section Payments with payment cards. For the information about payments with payment cards, see Purchase processing, Authorisation hold, Payment instrument verification, COF purchase registration and Supported payment cards.
• Updated the list of test cards supporting 3‑D Secure 2 authentication. For more information, see Test cards.

• Updated the ‘Payment models and statuses’ and One-time purchases sections: added information about changing authorised amount in two-step purchases.
• Updated the list of test cards supporting 3‑D Secure 2 authentication. For more information, see Test cards.

Updated the SDK for Android (legacy) and SDK for iOS (legacy) sections:

• Added information about purchase processing by using the WebMoneyLight and WebMoneyClassic purchase scenarios of the WebMoney payment method.
• Updated information about the parameters used to manage display of the final payment page.
• Added information about receiving callbacks with information about purchase processing result.

Added the section about Payments by using Telegram bot

• Updated the sections about UPI payment method—added information about payout performing.
• Added the sections about payout performing by using Amazon Pay payment method.

• Updated the sections about Mobile Commerce in the United Kingdom payment method—added information about resending the confirmation code.
• Updated the sections about purchase performing by using Indonesian Online Banking and Indonesian Virtual Accounts payment methods.

• Added information about Using Data API which allows retrieving information about balances and operations processed in the platform.
• Added References for country, currency, language, ECI, and regions codes.
• Updated the Data API specification up to version 2.0, and added the fields parameter to the endpoint for retrieving information about operations performed in the payment platform.

• Updated Gate API specification up to version2.31.0:
  • added the endpoints for the card payments via a partners
  • added the endpoints for the wallet payments via a partners
  • added the endpoints for the customer actions
  • made other minor updates
• Added the response code 30401. For more information, see ‘Information of operations performing’

• Added sections on payment processing by using the Card payments via partner (India) and Wallet payments via partner (India) payment methods
• Updated information on payment processing by using the Banks of India payment method. Updated information on purchase processing and added information on refund processing
• Updated information on payment processing by using the UPI payment method. Updated information on purchase processing

• Added sections on payment processing by using the Card payments via partner (India) and Wallet payments via partner (India) payment methods
• Updated information on payment processing by using the Banks of India payment method. Updated information on purchase processing and added information on refund processing
• Updated information on payment processing by using the UPI payment method. Updated information on purchase processing

• Added information about onshowclarificationpage and onSubmitClarificationForm event handler functions. For more information, see Handling customer behaviour events on Payment Page
• Added information about validating the value of the payment amount parameter. For more information, see Parameters for opening the payment form
• Added information about passed parameters to control the display of the final payment page. For more information, see the sections SDK for Android (legacy) and SDK for iOS (legacy)

• Added section on payment processing by using the Card payments via partner (in different countries) payment method.
• Updated information about the awaiting 3ds result status. For more information, see ‘One-time one-step purchase’ and ‘One-time two-step purchase’.

• Added section on payment processing by using the Card payments via partner (in different countries) payment method.
• Updated information about the awaiting 3ds result status. For more information, see ‘One-time one-step purchase’ and ‘One-time two-step purchase’.

• Added section on payment processing by using the Promptpay payment method.
• Updated information on payment processing by using the Card payments via partner payment method. Updated information on purchase processing.

• Added section on payment processing by using the Promptpay payment method.
• Updated information on payment processing by using the Card payments via partner payment method. Updated information on purchase processing.

• Added information about ‘Splitting payment amount’
• Updated the SDK for Android (legacy) section: added information about import of libraries via JCenter.
• Updated the SDK for iOS (legacy) section: added information about import of libraries via CocoaPods.

• Added sections on payment processing by using the Argentina Online Banking, Brazil Online Banking, Card payments via partner (Argentina), Carga Virtual, Link, Loterica, Mexico Online Banking, payment methods.
• Updated information on payment processing by using the Boleto, Mobile Commerce, Pago, Oxxo, Rapipago payment methods. Updated information on purchase processing.

• Added sections on payment processing by using the Argentina Online Banking, Brazil Online Banking, Card payments via partner (Argentina), Carga Virtual, Link, Loterica, Mexico Online Banking, payment methods.
• Updated information on payment processing by using the Boleto, Mobile Commerce, Pago, Oxxo, Rapipago payment methods. Updated information on purchase processing.

• Updated and extended the section with information about limiting time for using Payment Page. For more details, see Limiting time for working with payment form.
• Updated and extended the Submission of additional payment information section.

• 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 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 (legacy) and SDK for iOS (legacy).

• 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 Thai Online Banking 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 Thai Online Banking 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 (legacy).
• Added section on payment processing by using the Indonesian Virtual Accounts payment method, payment processing by using this method was previously described in the Indonesian Online Banking 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 Indonesian Virtual Accounts payment method, payment processing by using this method was previously described in the Indonesian Online Banking 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 transfers.
• Updated description of response code 104 in ‘Information of operations performing’.

• Added sections on payment processing by using Coins.ph, GCash, GrabPay, Philippines Over the Counter & ATM, Philippines Payment Centers and other 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 (legacy).

• Added sections on payment processing by using Coins.ph, GCash, GrabPay, Philippines Over the Counter & ATM, Philippines Payment Centers and other 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 (legacy).

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

• 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 for card payments 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 for card payments 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’.

• 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

• 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:
  • Indonesian Online Banking
  • Malaysian Online Banking
  • Thai Online Banking
  • Vietnamese Online Banking
• Added information on iframe size settings when Opening Payment Page in an iframe element of an HTML 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:
  • Indonesian Online Banking
  • Malaysian Online Banking
  • Thai Online Banking
  • Vietnamese Online Banking

• 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 (legacy) and SDK for iOS (legacy)
• 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 Parameters for opening the payment form
• 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 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 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

• Updated sections on payment processing by using Gate: updated and expanded the One-time purchases, Payouts, 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 Payouts

• 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:
  • Indonesian Online Banking
  • Malaysian Online Banking
  • Thai Online Banking
  • Vietnamese Online Banking
• 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:
  • Indonesian Online Banking
  • Malaysian Online Banking
  • Thai Online Banking
  • Vietnamese Online Banking
• 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 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 Parameters for opening the payment form
• Updated the information about Options for redirecting customers to the web service

• 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 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 (legacy) and SDK for iOS (legacy)

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.