Release 22.01.2026

Changelog

Crypto Wallets

Removed Endpoints:

• The following CryptoWallet endpoints have been removed from the API:
  • POST /customers/crypto-wallet — Create Crypto Wallet for a Customer
  • GET /customers/{customerId}/crypto-wallet — Retrieve Customer's Crypto Wallets

Orders

Customer and Payer Data Handling:

• Updated priority rules when both customer and payer objects are provided in the Create Order request. This behavior applies only when the company setting "Use customer data as payer information" is enabled:
  • Data from customer and payer objects will be merged
  • Fields from the payer object take priority over corresponding fields from customer
  • Missing fields in payer will be supplemented from customer data

Cryptocurrency Payments:

• Customer identification is now required for cryptocurrency payments (instrumentType: crypto_wallet). You must provide at least one of the following fields in the customer object:
  • customerId — to use an existing customer
  • email — to identify or create customer by email
  • phone — to identify or create customer by phone

Shop Hosted Integration:

• When using dataEntryMode: instruction with paymentPageDesign.format: shop_hosted, the payer object with required fields must be provided in the request. If payer data is insufficient, a validation error will be returned.
• Instruction parameters are returned in the operationReference object via webhook and Retrieve Order Details response.