Skip to main content
POST
Verify a PAN and record consent

How it works

  1. Show the buyer the consent statement below and get their agreement.
  2. Call this endpoint with the buyer’s pan and buyer_pan_consent: true.
  3. If verified is true, create the order within 24 hours on Create Order. Send the same PAN as buyer.pan_number, with business_model and purpose_code.
If verified is false, no consent is recorded. The buyer enters their PAN on the PAN page in Hosted Checkout. Send buyer_pan_consent: true only after the buyer has agreed to the statement Hosted Checkout shows on its PAN page.
  • LRS payments: “By continuing, I confirm that the PAN I entered belongs to the person paying for this purchase, that I have permission to share it, and that this payment is within their LRS limit for this financial year, and I agree to the Terms & Conditions and Privacy Policy.”
  • Other consumer payments: “By continuing, I confirm that the PAN I entered belongs to the person paying for this purchase, that I have permission to share it, and I agree to the Terms & Conditions and Privacy Policy.”
The consent lasts 24 hours and covers every order created with that PAN in that time. After 24 hours the buyer sees the PAN page again; call this endpoint again to renew it. For an LRS order, the time of this call is recorded as the buyer’s LRS declaration time.

Reasons

Errors

Consent missing

Authorizations

X-Client-ID
string
header
required

Client Application ID - Your unique application identifier used to authenticate API requests. You can find your Client ID in the Developer Settings section of the merchant dashboard.

X-Client-Secret
string
header
required

Client Secret Key - Your secret key used alongside the Client ID for secure authentication. Keep this confidential and never expose it in client-side code. Available in the Developer Settings section of the merchant dashboard.

X-Merchant-ID
string
header
required

Merchant Identifier - The unique ID for the merchant account. This is required for PSP (Payment Service Provider) merchants who manage multiple merchant accounts. You can find merchant IDs in the Merchant Management section of the dashboard.

Body

application/json
pan
string
required

Buyer PAN (AAAAA9999A format). Spaces around it are trimmed and letters are upper-cased.

Example:

"ABCPK1234F"

true when the buyer has agreed to the consent statement above. Any other value is refused.

Example:

true

Response

PAN checked. Read verified.

success
boolean
Example:

true

message
string
Example:

"PAN verified."

data
object