Initiates Card Binding. To initiate the card binding process, send the customer’s full PAN within the payload. The response will include:
verificationId: A unique identifier for this binding attempt.code: The verification code for confirmation.
Ensure that the verification code is securely transmitted and not logged.Basic authentication header of the form Basic <encoded-value>, where <encoded-value> is the base64-encoded string username:password.
The request body MUST contain the customer's full PAN.
Full primary account number.
"5123888812341234"
Card binding process initiated successfully. The response contains the verificationId and code required to complete the binding via the /confirm endpoint, along with card metadata.
A unique identifier (UUID) representing this specific binding attempt. Store this ID and use it in the /confirm request.
The verification code generated for the cardholder. This code MUST be securely obtained from the cardholder (e.g., they enter it into your interface after receiving it via SMS/email) and sent in the /confirm request. Do not log or store this code.
The timestamp (ISO 8601 format) when the verificationId and code expire. The confirmation step must be completed before this time.
The card's PAN, masked for display purposes (e.g., showing only the first 6 and last 4 digits). Useful for showing the customer which card is being bound.
"545188******0110"
The cardholder's registered contact number (partially masked or full, depending on configuration), typically where the verification code is sent.
85260001235
A URL pointing to an image representing the card's brand (e.g., Visa, Mastercard logo).