Skip to main content
Your Indian buyer pays in rupees. You send us the compliance details. We settle the money to your account abroad. This page shows the whole flow. Read it once, then follow the linked pages to build.

​
The five steps

1

Create your merchants

PSPs create a sub-merchant for each business they collect for. Wait for approval before collecting.Create Merchant · Merchant Approved webhook
2

Set up a way to get paid

Two ways to collect: send the buyer to an EximPe-hosted payment page, or give them a virtual account to pay into directly.Hosted Checkout · Virtual Bank Accounts
3

The buyer pays

We create a payment and send you a webhook. Its status is ACTION_REQUIRED, because we do not have the compliance details yet.
4

Send the compliance details

Tell us who paid, what for, and attach the documents. The status becomes IN_REVIEW.For a B2C payment, the buyer, product, and invoice fields you already sent at Create Order are enough — there’s nothing further to send.A Virtual Account credit arrives with no Create Order call behind it, so those same basic facts get filled in afterward in the EximPe dashboard instead.For LRS and B2B services payments we tell you exactly what is needed, you send it, and it completes itself. An LRS payment (an individual paying for education or travel) verifies the buyer’s PAN and collects the tax figures — see LRS Verification. A B2B services payment (a business paying for a service) has no identity step and no tax at all — see B2B Services Verification.
5

Get your money

We convert the amount to be settled at the exchange rate on the settlement date and send it to your account abroad. Status becomes SETTLED. Our fee, the GST on it, and any tax were paid by the buyer on top, so the whole amount reaches you.What it costs you · Settlement APIs · Payment Settled webhook

​
How the buyer pays

Money can reach you by more than one Indian payment method.

Hosted Checkout

Create an order, send the buyer to EximPe’s payment page, and they pay by card, UPI, net banking, or QR. Nothing sensitive touches your servers.

Virtual Bank Accounts

An Indian account number we issue for you. The buyer pays into it by NEFT, RTGS, or IMPS, exactly as they would pay any local supplier. Give them the account number and the IFSC.

Subscriptions

The buyer approves a mandate once — by UPI or by card — and every debit after that is authorised by it. Use it for recurring fees rather than one-off collections.
The method only decides how the money arrives. Once a payment exists it behaves the same way whichever route it came by — same statuses, same webhooks, same compliance step, same settlement.

​
Who is who

One virtual account takes payments from many buyers. So a credit landing does not tell you who paid — you tell us, in step 4.

​
The two amounts

These are not the same number, and mixing them up is the most common way a payment stalls. Ask for the amount to be collected. Declare the amount to be settled. Collect the smaller of the two and the payment sits short until the buyer tops up.
Which flow this applies to. Declaring an amount_to_be_settled and quoting the tax on it belongs to the LRS flow. A B2B services payment declares invoice_amount to cross-check against the credit, but no amount_to_be_settled: what settles is the credit itself, read from the payment.

​
Payment statuses

Settlement is reported separately, by the settlement APIs and PAYMENT_SETTLED.
LRS payments work to a deadline. Each carries a verification expiry. Miss it and the payment expires — terminal, and the money goes back to the buyer. See The payment has a deadline.

​
When things go wrong

The buyer paid too little. The payment waits, and the outstanding entry on the event names the shortfall. Either have the buyer transfer the difference and link that credit as a top-up with linked_payment_id, or declare a smaller amount_to_be_settled for what actually arrived and submit again. A document was rejected. We tell you exactly what is wrong. Fix only that item and send it again. The money came from someone else’s account. This applies to LRS payments only. The name on the sending account did not match the PAN you gave us, so the payment stays in action_required with reason: SENDER_NAME_MISMATCH. Either we refund it and the buyer pays again from their own account, or you send us the PAN of whoever actually paid — the payment then settles against that person and counts against their LRS limit. You need to refund. Refunds go back to the buyer’s own account. You can refund part of a payment, more than once. If your balance does not cover it, the call fails — collect more and try again.
Where refund money comes from. A refund is netted against your upcoming settlements. We hold a balance for each merchant, and the refund comes out of money we have not settled to you yet. If that balance is too small the call is rejected, so retry once you have collected more.

​
Next

Hosted Checkout

Take your first payment on an EximPe-hosted page.

Virtual Bank Accounts

Create a virtual account and take your first payment.

Send compliance details

Read what the payment needs, send it, repeat until nothing is left.

B2B services

A business paying for a service: no identity step, no tax, plus a document step after settlement.