> ## 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.

# Introduction

> EximPe is an API-only cross-border collection rail. Collect an Indian buyer's rupees into an EximPe-issued virtual account and have the funds settled to you abroad — with LRS compliance handled through the API. EximPe shows the buyer no screen.

<Button href="/integration-guide/v3/getting-started/steps-to-integrate" variant="primary" size="lg">
  Get Started with EximPe
</Button>

## Overview

This is a **headless, API-only** rail for collecting an Indian buyer's rupees into an EximPe-issued **Virtual Bank Account (VBA)** and settling the funds abroad under the RBI **Payment Aggregator – Cross Border (PA-CB)** framework. A bank partner (an **Authorised Dealer**, or "AD bank") performs the actual outward remittance. There is no hosted checkout, no card/UPI payment page — the buyer transfers money to a virtual account, and you assert the compliance details through the API.

You own the entire customer-facing experience and the customer relationship; EximPe is the embedded India collection and settlement engine underneath. You onboard the universities you serve as sub-merchants — collections, settlements, and balances are tracked **per university**.

## Who Uses It

<CardGroup cols={2}>
  <Card title="PSP" icon="sitemap">
    An integrator that calls the API on behalf of the **sub-merchants** it onboards. A PSP never holds a VBA or funds itself.
  </Card>

  <Card title="Sub-merchant" icon="store">
    A merchant created under a PSP. Holds VBAs and collected funds; is the entity that gets settled (the "settling entity").
  </Card>

  <Card title="Direct merchant" icon="building">
    A merchant with no parent PSP — holds its own VBAs and funds and is its own API caller.
  </Card>

  <Card title="Remitter (Buyer)" icon="user">
    The person in India paying, uniquely identified by **PAN**. LRS limits apply per person, platform-wide.
  </Card>
</CardGroup>

## How It Works

<Steps>
  <Step title="Onboard merchants">
    A PSP registers, then creates sub-merchants via the API. Each is approved before it can collect.
  </Step>

  <Step title="Issue a Virtual Bank Account">
    Create a VBA for the settling entity. Indian buyers transfer rupees into it — a single VBA can receive credits from many remitters.
  </Step>

  <Step title="Receive a credit">
    When money lands in the VBA, EximPe creates a payment in **Action Required** and notifies you by webhook.
  </Step>

  <Step title="Assert LRS compliance">
    Verify the buyer's PAN, quote the TCS, upload supporting documents, and submit the remitter / purpose / declarations. The payment advances to **Under Review**.
  </Step>

  <Step title="Settle abroad">
    Cleared funds are settled to the beneficiary and reported via the settlement APIs and the Payment Settled webhook.
  </Step>
</Steps>

## Why EximPe

<CardGroup cols={2}>
  <Card title="No Local Entity" icon="building">
    Collect in India without an Indian business entity or banking setup.
  </Card>

  <Card title="Compliance Built In" icon="shield-check">
    LRS limits, TCS, purpose codes, and documentation are handled through the API and by EximPe.
  </Card>

  <Card title="Multi-Currency Settlement" icon="money-bill">
    Rupees collected in India, settled to you abroad in your currency.
  </Card>

  <Card title="Fully API-Driven" icon="code">
    No buyer-facing screens — embed collection and compliance directly in your product.
  </Card>
</CardGroup>

## Regulatory Framework

EximPe operates under the RBI **PA-CB** guidelines. Key constraints to design for:

* **Per-transaction limit**: ₹25,00,000 per transaction.
* **LRS TCS threshold**: TCS is nil up to ₹10,00,000 of a remitter's cumulative LRS in a financial year, and applies only to the amount above it (per person, platform-wide, resets each 1 April).
* **Purpose codes**: every payment carries a FEMA purpose code from the settling entity's allowlist.
* **Documentation**: a digital invoice and supporting documents are required for each remittance; a full audit trail is maintained.

For the full rules — eligibility, the buyer declarations, TCS mechanics, and the education purpose codes and documents — see [LRS & Compliance](/integration-guide/v3/web-integration/lrs-compliance).

<Info>
  **Ready to start?** Follow [Steps to Integrate](/integration-guide/v3/getting-started/steps-to-integrate) to onboard, issue a VBA, and collect your first payment.
</Info>