Skip to main content

BDT Merchant API v2 changelog

Customer IP support — 2026-09-29​

  • Added fields.merchant_user_ip to PayIn and PayOut examples and request tables.
  • The field maps to the operation's customer IP. IPv4 and IPv6 are supported; required status follows the selected shop's input schema.

Merchant integration clarification — 2026-09-29​

  • Restored the v1 navigation, tabbed reference tables, and side-by-side request/response examples while retaining the v2 contract.

  • Restored the BDT customer mobile number in the deposit request table and full example as fields.mobile_number.

  • Added the v1-to-v2 request-field mapping, including customer ID/IP limitations and recipient-number formats.

  • Clarified the create → status → callback flow and safe retries with the original order ID.

  • Documented POST body-only input, URL validation, customer-field types, and mobile-account length.

  • Explained PayIn preparation, signed link expiry, and status-based browser returns.

  • Corrected v2 callback acknowledgement to HTTP 200 and documented retries, result corrections, and signing-key rotation.

  • Clarified optional PayIn payer-account data and its current mapping limitations.

This documentation update is not a backend release or confirmation that every channel is available. Confirm the deployed contract and the supported fields for your assigned shops before live integration.

Initial merchant guide — 2026-09-24​

Documented the implemented v2 deposit, withdrawal, individual transaction status, and terminal callback contracts. The v2 API does not currently provide balance or transaction-list endpoints. This guide is based on the hrs-core implementation and does not assert that a particular production environment has deployed v2; confirm availability during merchant onboarding.