Skip to content

Defined Fields

FieldTagRequiredDescription
Wallet01YesDestination TON address (10-48 characters)
Merchant02YesMerchant identifier (spaces replaced by _)
Amount03YesValue in cents (positive integer)
Currency04YesCurrency (fixed): USDT
TX ID05YesUnique transaction identifier (max 64 chars)
HMAC06NoHMAC-SHA256 signature (16 hex chars)
CRC99YesCRC16-CCITT (always 4 characters, always last)

Destination TON wallet address for the payment.

  • Format: alphanumeric string with _ and -
  • Length: 10 to 48 characters
  • Example: UQBJ6gU8gh_jRrzYDlfw9cpCwHaSn2mrK4O-1h8CDENehGYJ

Unique merchant/store identifier.

  • Format: alphanumeric string
  • Maximum length: 32 characters
  • Spaces: replaced by _ in the payload, restored on display
  • Example: store123 or My_Store

Payment value in cents (integer).

  • Format: positive integer as string
  • Maximum: 10000000 (= 100,000.00 USDT) — higher values are rejected by the server
  • Example: 1000 (= 10.00 USDT)

Currency code. Only USDT is currently supported.

  • Accepted value: USDT
  • Default: USDT

Unique transaction identifier. Used for tracking and status queries.

  • Format: alphanumeric string
  • Maximum length: 64 characters
  • Generation: can be provided by the merchant or generated automatically
  • Example: tx1709234567

HMAC-SHA256 signature to guarantee payload integrity. When present, the server validates that the payload was not altered.

  • Format: 16 hexadecimal characters (truncated from SHA256)
  • Calculation: HMAC-SHA256(payload_without_hmac_without_crc, secret_key)[:16]
  • Use: protects against tampering of values (wallet, amount, etc.)

CRC16-CCITT checksum for integrity validation.

  • Length: always 4 characters (uppercase hexadecimal)
  • Position: always the last field in the payload
  • Calculation: over payload_without_crc + "9904"