> ## Documentation Index > Fetch the complete documentation index at: https://docs.eximpe.com/llms.txt > Use this file to discover all available pages before exploring further. # Verify PAN > Verify a buyer's PAN against income-tax records. A verified PAN is the gateway to the LRS buyer flow. ## OpenAPI ````yaml POST /pg/pan/verify/ openapi: 3.0.0 info: title: Eximpe Payment Gateway API description: >- API for payment processing and order management through Eximpe payment gateway. This specification is for v3 API version. license: name: Proprietary version: 3.0.0 servers: - url: https://api-pacb-uat.eximpe.com description: Payment Gateway Sandbox URL security: - clientAuth: [] clientSecretAuth: [] apiVersionHeader: [] tags: - name: Card Tokens - name: Merchants - name: Orders - name: Payment Links - name: Payments - name: Refunds - name: Settlements - name: Subscriptions - name: Virtual Bank Accounts description: Create and manage ICICI virtual accounts and read collected payments. paths: /pg/pan/verify/: post: tags: - LRS summary: Verify a buyer's PAN description: >- Verify a buyer's PAN against income-tax records — validity, individual-vs-company, active-vs-inoperative, and whether the supplied name and date of birth match. The result is recorded against the PAN. This is the gateway to the LRS buyer flow: a verified PAN is required before you can quote or submit LRS verification details. A non-matching or rejected PAN returns `verified: false` with a `reason` to resolve with the buyer. operationId: v3_post_pg_pan_verify_ requestBody: required: true content: application/json: schema: type: object required: - pan - name - dob properties: pan: type: string description: Buyer PAN (AAAAA9999A format). example: ABCDE1234F name: type: string maxLength: 255 description: Buyer's full name as per PAN. example: John Doe dob: type: string format: date description: Buyer's date of birth (YYYY-MM-DD). example: '1990-01-01' example: pan: ABCDE1234F name: John Doe dob: '1990-01-01' responses: '200': description: PAN verification processed (check the `verified` flag). content: application/json: schema: type: object properties: success: type: boolean example: true message: type: string example: PAN verified data: type: object properties: pan_id: type: string example: PAN_8f3a2b1c9d verified: type: boolean example: true pan_status: type: string enum: - VALID - INVALID - INOPERATIVE nullable: true example: VALID entity_type: type: string enum: - INDIVIDUAL - COMPANY - OTHER nullable: true example: INDIVIDUAL reason: type: string enum: - INVALID_PAN - NON_INDIVIDUAL_PAN - INOPERATIVE_PAN - NAME_MISMATCH - DOB_MISMATCH nullable: true example: null examples: verified: summary: Verified value: success: true message: PAN verified data: pan_id: PAN_8f3a2b1c9d verified: true pan_status: VALID entity_type: INDIVIDUAL reason: null not_verified: summary: Name mismatch value: success: true message: PAN verification did not pass data: pan_id: PAN_8f3a2b1c9d verified: false pan_status: VALID entity_type: INDIVIDUAL reason: NAME_MISMATCH '400': description: Invalid request — bad PAN format or missing fields. content: application/json: schema: $ref: '#/components/schemas/v3_ErrorResponse' '500': description: Unexpected error during PAN verification. content: application/json: schema: $ref: '#/components/schemas/v3_ErrorResponse' '502': description: PAN verification provider error. content: application/json: schema: $ref: '#/components/schemas/v3_ErrorResponse' security: - clientAuth: [] clientSecretAuth: [] merchantAuth: [] apiVersionHeader: [] components: schemas: v3_ErrorResponse: type: object required: - success - error properties: success: type: boolean description: Indicates if the request was successful error: $ref: '#/components/schemas/v3_ErrorDetails' v3_ErrorDetails: type: object required: - code - message properties: code: type: string description: Error code (e.g., ERR_ORDER_002) message: type: string description: Error message details: type: object description: Detailed validation error information with field-specific errors additionalProperties: type: string description: Error message for the specific field securitySchemes: clientAuth: type: apiKey name: X-Client-ID in: header description: >- **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-displayName: Client ID x-example: your-client-id clientSecretAuth: type: apiKey name: X-Client-Secret in: header description: >- **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-displayName: Client Secret x-example: your-client-secret apiVersionHeader: type: apiKey name: X-API-Version in: header description: >- **API Version** - Specifies which version of the API to use (e.g., '1.X.X', '2.X.X', or '3.X.X'). This header allows you to control which API version your integration uses. Default version information is available in the Developer Settings. x-displayName: API Version x-example: 3.0.0 merchantAuth: type: apiKey name: X-Merchant-ID in: header description: >- **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. x-displayName: Merchant ID x-example: your-merchant-id ````