Skip to main content

Release 06.11.2024

· 2 min read

Changelog​

General​

  • Update: Additional dataEntryModes options have been introduced, including instruction, iframe, and html, providing flexible methods for customer data entry in the Retrieve Payment Methods and Create Order endpoints.
  • Update: Expanded transferType options for payouts, adding the following new methods:
    • sbp - Russian System for Fast Payments
    • open_finance - Open banking options
    • virtual_account - Virtual account payments
    • spei - Mexican interbank electronic payments (SPEI)
    • vietqr - Vietnamese QR code payments
    • paysafecard - Prepaid voucher service
    • multibanco - Portuguese bank transfer method
    • bancontact - Belgian payment method
    • blik - Polish mobile payment system
    • p24 - Przelewy24, a Polish online payment system
    • rapidtransfer - Rapid Transfer for bank payments
    • upi - India’s Unified Payments Interface
    • thb_qr - Thai QR payments
    • sberbank - Sberbank Online for Russian transfers
    • account2card - Direct bank-to-card transfer

Cryptocurrency​

Initial support for cryptocurrency transactions has begun, but implementation is still ongoing. Below are the changes introduced so far, with further updates planned for upcoming releases. All modifications are backward-compatible.

  • Update: A new cryptoTokenStandard parameter has been added to the order object in the Create Order endpoint and to the payout in the Create Payout Request , required if the currency is set to a cryptocurrency. This allows specifying the blockchain standard for crypto payments, such as ERC20.
  • Update: The amount and currency fields in order -> cost object were modified to support cryptocurrency transactions, including the addition of decimal precision requirements for crypto and the need to specify cryptoTokenStandard in the Create Order endpoint and in payout -> cost in the Create Payout Request .
  • Update: The customer data container now allows customer details (firstName, lastName, middleName, phone, and email) from the order request to be automatically used on the payment page without re-entry, governed by the Use customer data as payer information setting. This behavior applies across all orders created using the Create Order endpoint.

Payouts​

  • New fields: Added ipAddress, beneficiaryName, and beneficiarySurname to RecipientPersonalData for enhanced payer identification in the Create Payout Request endpoint.
  • Update: Added RUT to RecipientDocuments to support Chilean taxpayer identification in the Create Payout Request endpoint.