> ## 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. # Quote LRS Amount > Quote the TCS due and the all-in total a buyer pays for a proposed LRS remittance. Requires a verified PAN. ## OpenAPI ````yaml POST /pg/lrs/quote/ 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/lrs/quote/: post: tags: - LRS summary: Quote TCS and all-in total for a remittance description: >- Given a verified PAN and a proposed remittance amount (INR), returns the TCS due and the all-in total the buyer pays. TCS is nil up to Rs.10,00,000 of cumulative LRS this financial year and applies only to the slice above it (for education from the remitter's own funds the rate is 2%); education-loan-funded remittances are exempt. This quotes against the LRS usage visible to us and reserves nothing. Requires a verified PAN and a `purpose_code` the sub-merchant is enabled for. **PSP callers must send `X-Merchant-ID`** naming the settling sub-merchant — LRS is always scoped to the settling entity, never the PSP. operationId: v3_post_pg_lrs_quote_ requestBody: required: true content: application/json: schema: type: object required: - pan - amount - purpose_code - tcs_threshold_breached properties: pan: type: string description: Verified buyer PAN. example: ABCDE1234F amount: type: number description: Proposed remittance amount in INR rupees. example: 1200000 purpose_code: type: string description: >- FEMA purpose code; must be one the sub-merchant is enabled for. example: S0305 tcs_threshold_breached: type: boolean description: >- Buyer's self-declaration that they have already crossed Rs.10L of LRS this FY elsewhere. When true, the full remittance is taxed. example: false example: pan: ABCDE1234F amount: 1200000 purpose_code: S0305 tcs_threshold_breached: false responses: '200': description: TCS and total quoted. content: application/json: schema: type: object properties: success: type: boolean example: true message: type: string example: LRS amount quoted data: type: object properties: financial_year: type: integer description: Financial year the quote applies to (start year). example: 2025 committed_inr: type: string description: Cumulative LRS already used this FY (INR). example: '0.00' remittance_inr: type: string description: The proposed remittance (INR). example: '1200000.00' taxable_inr: type: string description: Portion of the remittance subject to TCS (INR). example: '200000.00' tcs_inr: type: string description: TCS due on this remittance (INR). example: '4000.00' total_payable_inr: type: string description: All-in total the buyer pays (remittance + TCS). example: '1204000.00' tcs_threshold_breached_before: type: boolean description: >- Whether the Rs.10L threshold was already crossed before this remittance. example: false tcs_threshold_breached_after: type: boolean description: Whether this remittance crosses the Rs.10L threshold. example: true example: success: true message: LRS amount quoted data: financial_year: 2025 committed_inr: '0.00' remittance_inr: '1200000.00' taxable_inr: '200000.00' tcs_inr: '4000.00' total_payable_inr: '1204000.00' tcs_threshold_breached_before: false tcs_threshold_breached_after: true '400': description: >- Invalid request — validation error, unverified PAN, or purpose code not enabled. content: application/json: schema: $ref: '#/components/schemas/v3_ErrorResponse' '500': description: Unexpected error while quoting. 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 ````