Bind physical card

Bind the received PAN to the application holder; irreversible. Query operation after ambiguous results.

Permission: card.physical.operate. Prerequisites: shipped application, actual receipt, end-user identity verification and eligible HTTPS activation-code webhook. Binding is irreversible. Encrypt ApiPhysicalBindPayload using CardDataEncryption (API Key-derived AES-256-GCM); send encrypted/iv/tag, no plaintext or challenge request. Next: query /cards/physical/operation and receive card.physical.activation.code. Both successful binding and the code are required before activation; do not rebind on pending/unknown.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params
string
required
length ≤ 4096

Hex AES-256-GCM ciphertext produced by the existing CardDataEncryption protocol. Encrypt the complete ApiPhysicalBindPayload or ApiPhysicalActivatePayload JSON; never send plaintext fields alongside this envelope.

string
required
length between 32 and 32

16-byte IV, encoded as 32 hexadecimal characters

string
required
length between 32 and 32

16-byte GCM authentication tag, encoded as 32 hexadecimal characters

Headers
string

Only white-label customer need to use it

Response

Language
Credentials
Bearer
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json