Skip to main content

Release 24.09.2025

Changelog​

Enhanced Customer Management​

The Create New Customer and Retrieve Customer Information endpoints have been expanded with additional customer profile fields:

  • affiliatedId: An optional identifier for customer. This field allows merchants to pass arbitrary values that will be stored in the customer record.
  • billingAddress: Complete billing address information for customer profiles.
  • birthDate: Customer's date of birth in ISO 8601 format (YYYY-MM-DD).

Cryptocurrency Payment Enhancements​

The Create Order endpoint now includes cryptocurrency payment support through the new cryptoPayment object:

  • walletTokenStandard: Specifies the token standard for the customer's wallet cryptocurrency (e.g., TRC20, ERC-20, BEP-20). Required for token-based cryptocurrencies but not for native cryptocurrencies like BTC or ETH.
  • accountCurrency: Configures the merchant account currency for cryptocurrency payments, including both the currency and its network token standard when applicable.
  • The cryptoTokenStandard field has been removed from the order creation request, with this functionality now handled through the dedicated cryptoPayment object.

The Create Crypto Wallet endpoint has been updated:

  • The tokenStandard field has been renamed to networkTokenStandart within the accountCurrency object for consistency.
  • The accountCurrency field is now nullable.

Expanded Payment Method Support​

New transfer types are now available across multiple endpoints for enhanced regional payment coverage:

  • rapipago: Support for Rapipago payment method in Argentina.
  • pse: Support for PSE (Pagos Seguros en Línea) in Colombia.

These new transfer types have been added to:

New payment entry modes for digital wallets:

  • apple_pay: Apple Pay integration.
  • google_pay: Google Pay integration.

Recurring Payments Configuration​

The Create Order endpoint's recurringPayments object has been refined:

  • billingIntervalQuantity and intervalType are now required fields when setting up recurring subscriptions.
  • The paymentCount field is now nullable, allowing for indefinite subscriptions.

Payout Enhancements​

The Create Payout Request endpoint has been updated with improved data organization:

  • Removed the paymentData field from both recipient and sender objects.
  • Added bankAccountUserId to the bankTransferData object for enhanced bank account identification.
  • Introduced payoutChannel field in the payoutData object to specify the channel used for payouts.
  • Personal data now includes an optional id field.

The Retrieve Required Payout Fields endpoint response has been streamlined:

  • Removed paymentData from the available categories.