Skip to main content

Release 14.04.2026

Changelog​

Orders​

Cryptocurrency Payment Structure Unification (Breaking):

The cryptocurrency payment parameters in the Create Order request have been restructured for clarity and to group merchant-side data under a dedicated recipient object. See the updated Cryptocurrency Reference Guide for full details.

  • Removed the cryptoPayment object. Its fields have been moved and renamed as described below.
  • Added order.cost.tokenStandard — the token standard of the customer's wallet cryptocurrency (for example, TRC20, ERC20, BEP20). Replaces the former cryptoPayment.walletTokenStandard. Optional. Should be provided for token-based cryptocurrencies when using crypto_currency_code in order.cost.currency; not needed for native cryptocurrencies or when using asset_code format.
  • Added recipient object with the nested merchantBalance object, which declares the currency of the merchant's balance. The merchant balance currency may be fiat or crypto and is independent from order.cost.currency (the currency the customer pays in).
    • recipient.merchantBalance.currency — the merchant balance currency code (replaces the former cryptoPayment.accountCurrency.currency). Required when the merchantBalance object is provided.
    • recipient.merchantBalance.tokenStandard — the token standard of the merchant balance currency (replaces the former cryptoPayment.accountCurrency.networkTokenStandard). Optional. Should be provided when merchantBalance.currency is a token-based cryptocurrency; ignored for fiat currencies.

Migration example:

Before:

{
  "order": {
    "cost": {
      "amount": "20",
      "currency": "USDT"
    }
  },
  "cryptoPayment": {
    "walletTokenStandard": "TRC20",
    "accountCurrency": {
      "currency": "USDC",
      "networkTokenStandard": "TRC20"
    }
  }
}

After:

{
  "order": {
    "cost": {
      "amount": "20",
      "currency": "USDT",
      "tokenStandard": "TRC20"
    }
  },
  "recipient": {
    "merchantBalance": {
      "currency": "USDC",
      "tokenStandard": "TRC20"
    }
  }
}

E-wallet Payer Data Support:

  • Added walletData object to the payer field in the Create Order endpoint.
  • Use this object to pass the payer's e-wallet details for providers that accept payments via digital wallets.
  • Available fields (all optional): walletId, walletType, walletName, walletHolderName.

Added tokenStandard to cost for partial operations:

The tokenStandard field has been added to the cost object in the following endpoints, mirroring order.cost.tokenStandard for consistency across the order lifecycle:

P2P​

Added tokenStandard to cost:

  • Added p2p.cost.tokenStandard to the Create P2P Transaction request. Optional.
  • Should be provided for token-based cryptocurrencies when using crypto_currency_code in p2p.cost.currency; not needed for native cryptocurrencies or when using asset_code format.

Payouts​

Added tokenStandard to payout.cost:

  • Added payout.cost.tokenStandard to the Create Payout Request endpoint. Optional. Should be provided for token-based cryptocurrencies when using crypto_currency_code in payout.cost.currency; not needed for native cryptocurrencies or when using asset_code format.
  • The existing payout.cryptoTokenStandard field is unchanged.