How to Receive International Payments in India (Compliantly)

To receive international payments in India compliantly, route the money through your bank as an inward remittance against an RBI purpose code that names what you sold — for software and IT services that is usually P0802 — and keep the FIRC (Foreign Inward Remittance Certificate) your bank issues as proof. The same logic applies if you get paid in USDC, a digital dollar issued by Circle and redeemable 1:1 for US dollars: the inflow is clean only when it is off-ramped to INR on a rail that reports a purpose code and produces a paper trail, not when it is sold peer-to-peer from a personal wallet. The part most guides skip is that compliance is not about which currency arrives — it is about whether every rupee that lands in your account can be explained to your AD bank with a documented reason.

This is general information, not legal, tax, or financial advice. FEMA, RBI, and crypto-tax rules change; confirm current guidance with the RBI, your authorised-dealer (AD) bank, or a qualified advisor before relying on it. The compliance points below reflect official sources as of June 2026.

What is the compliant way to receive foreign payments in India?

The compliant route is an inward remittance through an authorised-dealer bank, recorded against a purpose code that matches the service you exported, with a FIRC as evidence.

Under FEMA, every foreign payment that lands in your account is supposed to carry a reason — the RBI purpose code — that tells your bank and the regulator what the money was for. For a freelancer exporting software or IT consultancy, that code is typically P0802. Your bank then issues a Foreign Inward Remittance Certificate (FIRC), which is the single document that proves the money came from abroad, in foreign currency, for a legitimate export. Per RBI's Master Direction on Export of Goods and Services, AD banks handle these receipts and the associated documentation.

Skip the purpose code, and you have rupees in your account with no story attached.

That is the difference between an export receipt and an inflow you cannot explain — and it is the same line whether the money arrives as a SWIFT wire or as a stablecoin you convert to INR.

Which RBI purpose code applies to my export?

Pick the purpose code that names what you actually sold; for most freelancers and software exporters that is P0802, the receipt code for software/IT consultancy services.

RBI publishes a list of receipt purpose codes, and your AD bank tags each inward remittance with one. Getting it right matters because the code is what classifies the inflow as export of services rather than an unexplained transfer. The codes most relevant to service exporters and stablecoin off-ramps are the ones StableCorp supports for compliant INR conversion.

The purpose code is not paperwork friction — it is the thing that turns a foreign inflow into a documented export receipt, which is exactly what your bank, your CA, and the tax department need to see. When in doubt about the exact code for your service, confirm it with your AD bank against RBI's purpose-code notification.

How long do I have to bring the money into India?

Export proceeds must generally be realised and repatriated to India within nine months from the date of export, under RBI's export regulations.

This is the rule freelancers most often miss: you cannot let foreign earnings sit indefinitely in an overseas account or wallet and bring them in whenever you feel like it. RBI's Master Direction on Export of Goods and Services sets the realisation and repatriation window, and your AD bank tracks it. If you are paid in USDC and let it accumulate in a personal wallet, you are not just sitting on an undocumented asset — you may be drifting past the repatriation window without realising it.

Convert and repatriate on a schedule, against a purpose code, and the clock takes care of itself.

Does the LRS limit cap how much I can receive?

No — the LRS USD 250,000 annual limit governs money Indian residents send out, not export earnings you receive.

This is a common mix-up. The Liberalised Remittance Scheme caps outward remittances by a resident individual at USD 250,000 per financial year — for investments, travel, education, and the like. Inward export receipts for services you actually delivered are a separate flow and are not throttled by the LRS. So a freelancer billing USD 300,000 a year in software exports is not breaking any inward cap; they simply need each receipt documented with a purpose code and FIRC.

Know which direction the money is moving before you worry about which limit applies.

Paid in USDC? Off-ramp to INR at 1% on a compliant purpose-code rail with a real FIRC-style paper trail — not peer-to-peer from a personal wallet. See pricing.

Where does USDC fit — and is it the grey area?

USDC is a digital dollar; receiving it is fine, but the compliance lives in how you convert it to INR — and the grey area is the DIY direct-wallet path, not a documented off-ramp.

USDC is issued by Circle, pegged 1:1 to the US dollar, and backed by reserves Circle reports on. For an Indian exporter, getting paid in USDC can settle in minutes instead of the days a SWIFT wire takes routing through correspondent banks. The risk is never the dollar-token itself — it is the off-ramp. Selling USDC to a stranger on a peer-to-peer exchange leaves you with rupees and no purpose code, no FIRC, and no explanation of why the money arrived. That undocumented route is the actual grey area.

The compliant solution is to off-ramp USDC to INR on a rail that reports a recognised RBI purpose code and gives you a paper trail — which is exactly what StableCorp's direct off-ramp does, at 1%, against codes like P0802, P1004, P1005, P1006, P1007, and P1009 (others on request). That converts each payment as export of services, not as an undocumented crypto transfer.

Separately, India taxes virtual digital assets at a flat 30% under Section 115BBH, with a 1% TDS on transfers under Section 194S and no set-off of losses. Those rules govern how you report the asset on your return; running the conversion on a compliant purpose-code rail is what keeps the inflow itself clean. The two are different problems — confirm both with a qualified advisor.

Bank wire vs. USDC off-ramp: what does each actually cost and document?

A bank wire and a compliant USDC off-ramp can both be FEMA-clean — the difference is speed and cost, where the off-ramp wins if it carries the same purpose-code documentation.

Conventional cross-border platforms advertise a headline rate around 2.9% but add roughly a 2% FX markup you never see itemized, so the effective cost lands near 5% on a typical payment. Because USDC is already a dollar, there is no FX conversion until you choose to off-ramp, and the only fee is that conversion.

On a USD 5,000 payment, a ~5% effective cost is about USD 250 gone; a 1% off-ramp is USD 50 — and you can see exactly where it went. If you also bill US clients, you can settle to a US bank balance at 0.5% when incorporated with StableCorp — see the full breakdown on pricing.

Should I receive payments personally or through an entity?

You can receive export earnings as an individual freelancer, but routing them through an entity often makes the paper trail and the off-ramp cleaner — especially at higher volumes.

As a sole freelancer, your inward remittances and FIRCs sit against your personal accounts, which is fine until volume or client expectations grow. An Indian LLP or Pvt Ltd, or a US entity if you bill American clients, gives you a clearer separation between business income and personal money — and a more legible export-of-services story. StableCorp forms Indian LLPs and Pvt Ltds, as well as US Wyoming LLCs and Delaware C-Corps, and can onboard your existing entity, then run the compliant off-ramp on top.

Match the structure to the volume, not the other way around.

If you are weighing a US versus an Indian setup for billing American clients, see how to form a US company from abroad; if your clients pay in stablecoins, see how to accept USDC payments.

The differentiated point: compliance is a documentation problem, not a currency problem

The non-obvious insight is that FEMA does not care whether you were paid in dollars, euros, or USDC — it cares whether each inflow has a purpose code, a paper trail, and a realisation within the window.

Most guides frame this as "crypto is risky in India," which is the wrong frame. A SWIFT wire with no clear purpose code is just as much of a problem as a peer-to-peer USDC sale; a USDC payment off-ramped on a purpose-code rail is just as clean as a documented wire. The variable that determines compliance is not the rail — it is whether the documentation exists at the moment the rupees land.

That is the StableCorp wedge: not "accept crypto," but off-ramp on rails that produce the export-of-services record your AD bank and the tax department already expect. When the off-ramp reports the purpose code and you keep the transaction hash, the contract, and the invoice together, the documentation is built at settlement instead of reconstructed at filing time.

The bottom line

Receiving international payments in India compliantly comes down to three things: a purpose code that names your export, a paper trail (FIRC or its equivalent), and repatriation within nine months.

Do that, and it does not matter whether the money arrives as a wire or as USDC — each rupee is explainable. Skip the DIY direct-wallet route, which is the real grey area, and convert stablecoins on a compliant purpose-code rail instead. StableCorp's direct off-ramp to INR is 1%, runs against supported codes like P0802, P1004, P1005, P1006, P1007, and P1009, and can sit on top of an Indian LLP, an Indian Pvt Ltd, a US entity, or your existing company — see pricing for the numbers.

Sources