Skip to main content
Live activation is controlled per company and capability. The public documentation is available while production activation is still being prepared.

​
Integration checks

  • Keep API keys and webhook secrets on your backend.
  • Verify that test and live keys use separate stored records.
  • Persist an idempotency key before sending each money-moving request.
  • Complete issuance, top-up, card-control, and reveal scenarios in sandbox.
  • Test lost responses, duplicate webhooks, pending operations, and failure handling.
  • Verify webhook signatures using raw request bytes and deduplicate event IDs.
  • Confirm that logs, analytics, and error reports exclude full card data and secrets.
  • Complete individual or corporate verification and the separate cardholder requirements. All API keys, including sandbox keys, require approval.
  • Enable an authenticator before using the Live wallet; each Live transfer requires a recent security confirmation.
  • Confirm the Live TRON wallet address on Mainnet and keep enough TRX for network fees before sending USDT.
  • Check the card-account invoice’s exact USDT amount, recipient, network, and expiry before authorizing a transfer.

​
Activate live access

Coordinate the production API address, card program, pricing, transaction limits, funding process, and support escalation with Plane. Create a separately scoped live key after approval; do not rename or reuse a sandbox key. Start with an agreed, limited pilot and reconcile the on-chain transfer, invoice settlement, company ledger movements, provider results, and card status before expanding traffic. Do not infer readiness from the existence of a DNS record or a live-key prefix.

​
Support

Contact Plane support with the environment, operation ID, timestamp, and sanitized error code. Never include a secret key, CVV, full card number, password, or recovery code.