Which export payment provider actually gives you a FIRC?

Which providers actually issue a realisation document?

Start with the split that matters, because it is binary before it is a matter of degree. Some providers hand you a realisation document as a normal part of getting paid. One does not hand you one at all.

Stripe is the outlier. Stripe's own support documentation states that it does not issue a FIRC or a FIRA for international transactions in India, and that what it provides instead is a payment advice from Standard Chartered, its settlement partner (source: Stripe support). A payment advice tells you a payment was made. It is not the certificate of realisation your AD bank works from. If you are on Stripe and you need a FIRC, you go to your own bank and ask for one, on your own bank's terms and at your own bank's price, every time.

PayPal sits in the middle. Its FIRA is issued in a Citibank format and PayPal states it complies with RBI PA-CB guidelines, with a free weekly digital FIRA available from February 2026 (source: PayPal India). That is a genuine bank-issued document. But it arrives on a weekly cadence keyed to the withdrawal batch, not to your invoices, which is a reconciliation problem rather than a validity problem. We come back to that in section six because it is the single most underrated variable in this whole comparison.

PingPong India makes a free digital FIRC available inside the dashboard, under the Withdraw area, and describes itself as an Online Payment Gateway Service Provider operating with an RBI-approved Liaison Office (source: PingPong India). Payoneer delivers an automated e-FIRA issued by its AD bank under Reports & Statements at no additional cost, but with an eligibility qualifier: only eligible payments are covered (source: Payoneer). That qualifier is not decoration. It means some of the money you receive may arrive without the paper, and you will only discover which payments those are after the fact unless you ask first.

Then there are the three that treat the document as a first-class part of the product. Skydo emails a FIRA on every settlement and states it is licensed under the RBI PA-CB framework, settling INR to an Indian bank account within twenty-four hours (source: Skydo). PayGlocal generates the FIRA automatically with no request needed, and holds RBI PA-CB-I&O and Online Payment Aggregator authorisation under Certificate of Authorisation No. 250/2025 (source: PayGlocal). Razorpay generates the FIRC within minutes of the INR credit and emails a One-Click FIRS within twenty-four hours of settlement (source: Razorpay).

What is the difference between a FIRC, a FIRA and a FIRS?

The vocabulary is genuinely confusing, and providers make it worse by naming the same underlying artefact differently in their marketing. Here is the structure underneath the words.

A FIRC , or Foreign Inward Remittance Certificate, is the classical certificate confirming that a specific sum in foreign currency was received into India and credited to a named beneficiary. It is issued by an Authorised Dealer bank. It is a banking instrument, and the authority behind it comes from the bank that signs it, not from the platform that surfaces it to you.

A FIRA , or Foreign Inward Remittance Advice, is the electronic sibling of that certificate. For most practical purposes in export documentation the two are used interchangeably, and providers use whichever term their partner bank prints on the artefact. PayPal calls its document a FIRA in a Citibank format. Payoneer calls its document an e-FIRA. Skydo and PayGlocal both call theirs a FIRA. PingPong calls its document a FIRC. The label follows the bank and the product team, not a substantive difference in what the paper proves.

A FIRS , or Foreign Inward Remittance Statement, is a different animal. A statement summarises remittances over a period rather than certifying one. Razorpay's product makes the distinction explicit: it generates the FIRC within minutes of the INR credit and separately emails a One-Click FIRS within twenty-four hours of settlement (Razorpay). Two artefacts, two jobs. The certificate is the per-credit proof; the statement is the periodic view your accountant will actually enjoy reading.

The point to hold onto through all of this: the FIRC or FIRA is always AD-bank issued . A payment service provider does not manufacture the document. It either surfaces the bank's document to you cleanly, or it does not surface it at all and you go and get it yourself. That is exactly the Stripe situation. Stripe substitutes a Standard Chartered payment advice, which is a record from a bank but not a certificate of realisation (Stripe support).

You will also encounter a NOC or a payee advice in this space. A no-objection certificate from a platform confirming it has no claim on the funds is sometimes bundled alongside a realisation document, particularly where money passed through an intermediary account. It supports the story; it does not replace the certificate. If your AD bank asks for a FIRC and you hand it a payee advice, you have not answered the question.

Which RBI framework is your provider actually under?

This section exists because your bank will ask, and because the answers are unusually uneven across the market. Some providers publish an authorisation number. Some publish a framework name. Some publish nothing at all. Below, we state what is documented and flag what is absent, rather than inferring a position for a provider that has not taken one publicly.

PayGlocal is the most specific. It cites PA-CB-I&O (Payment Aggregator Cross Border, import and export) together with Online Payment Aggregator authorisation, under Certificate of Authorisation No. 250/2025 (PayGlocal). A certificate number is the strongest form of this claim, because it is checkable.

PayPal states that its FIRA format is issued by Citibank and complies with RBI PA-CB guidelines (PayPal India). Note the shape of that statement carefully: it attaches compliance to the document format and names the bank, which is a narrower and more precise claim than a blanket assertion about the entity. Skydo states it is licensed under the PA-CB framework (Skydo).

PingPong India describes itself under the older OPGSP construct (Online Payment Gateway Service Provider) and publishes an RBI-approved Liaison Office UIN of BGLO19008226 and an FCRN of F0652 (PingPong India). Those are real, checkable identifiers, but they describe a liaison office registration rather than a payment aggregator authorisation, and it is worth asking the provider directly how it maps its current operations onto the PA-CB regime.

Payoneer, Stripe and Razorpay do not name a framework in the sources reviewed for this guide. Payoneer's digital FIRC page speaks in terms of FEMA compliance and an AD-bank-issued document without naming the bank. That is not a finding of non-compliance. It is an absence of a public statement, and the right response is to ask the provider in writing rather than to assume either way.

What does the realisation document cost you?

Most of these documents are free, which is exactly why the exceptions deserve attention rather than a shrug. When a cost is attached, it recurs on every payout, and recurring costs on a weekly cadence stop being rounding errors quickly.

PayPal's weekly digital FIRA is free. Its Custom FIRA is not: Rs 100 plus 18% GST per transaction for up to twenty transactions, or Rs 2,000 plus 18% GST for a bulk request above twenty transactions (PayPal India). Payoneer is free but only on eligible payments, which means the real cost is whatever you have to do about the ineligible ones. PingPong and Skydo are free. PayGlocal discloses no charge. Razorpay states setup of Rs 0.00 and annual maintenance of Rs 0.00 on its e-FIRA product, with no separate document charge (Razorpay).

Stripe costs whatever your own AD bank charges for a FIRC, on every payout, indefinitely. We deliberately do not put a number on that here, because bank FIRC charges vary by bank and by relationship and inventing a figure would be worse than leaving it open. What we can say with confidence is the structure: it is a per-document charge that you incur every settlement cycle and that no volume of FX savings automatically cancels.

Worked example (illustrative)

This is an illustrative calculation, not a real customer. Assume a seller on PayPal receiving one payout per week, fifty-two weeks a year, and assume the AD bank insists on transaction-level documents rather than accepting the weekly batch FIRA.

Case A. 15 transactions per week. That is under the twenty-transaction threshold, so the per-transaction rate applies. 15 × Rs 100 = Rs 1,500 base. GST at 18% on Rs 1,500 = Rs 270. Weekly total Rs 1,770. Annual total Rs 1,770 × 52 = Rs 92,040 .

Case B. 40 transactions per week. Above twenty, so the bulk rate applies. Rs 2,000 base plus 18% GST of Rs 360 = Rs 2,360 per weekly request. Annual total Rs 2,360 × 52 = Rs 1,22,720 .

Case C. The free weekly digital FIRA. Rs 0 per week, Rs 0 per year. But one document covering all forty orders, which pushes the work from the fee line onto your reconciliation team.

The gap between Case B and Case C is Rs 1,22,720 a year of pure document cost, decided entirely by whether your AD bank will accept a batch document plus a reconciliation, or insists on transaction-level paper. That is a question worth asking your bank before you pick a rail, not after.

How fast do the money and the paper arrive?

These are two clocks, and they are not the same clock. Providers market the first one loudly and the second one quietly, if at all. For your working capital, settlement speed is what matters. For your EDPMS position, document speed is what matters. A rail that settles in a day and documents in a week has left a gap you carry on your books.

Skydo settles INR to an Indian bank account within twenty-four hours and issues the FIRA on every settlement, so both clocks run together (Skydo). PayGlocal settles T+1 in INR with the FIRA generated automatically (PayGlocal). Razorpay settles within one business day, produces the FIRC within minutes of the INR credit and emails the FIRS within twenty-four hours. Which is the tightest published coupling of the two clocks among these providers (Razorpay).

PayPal's weekly FIRA necessarily lags the money, because it is cut on a weekly cadence regardless of when the individual settlements landed. Stripe's Standard Chartered advice arrives alongside the payout, which sounds fast until you remember it is not the certificate. The certificate clock does not start until you ask your own bank. For Payoneer and PingPong, settlement and document timing are not published in the sources reviewed here, and we would rather say so than invent a figure.

Does the document map to a shipping bill, or to a batch?

This is the section that should change how you choose. Everything above is comparable across providers on a spreadsheet. Granularity is the thing that quietly determines whether your EDPMS closure is a scheduled job or a monthly ordeal.

EDPMS works at the level of the shipping bill. Each shipping bill is an open item until realisation is attributed to it. So the question your reconciliation asks, over and over, is: which money closes which bill? The answer is easy when one document covers one bounded set of shipments and hard when one document covers an arbitrary week of activity.

A per-settlement document (Skydo's FIRA on every settlement, PayGlocal's automatic FIRA on a T+1 cycle, Razorpay's FIRC minutes after the INR credit) gives you a natural window. The shipments that fed that settlement are a small, identifiable set. You match within the window, and the match is one-to-few. That is automatable: you can write the rule, run it nightly, and only escalate the exceptions.

A weekly batch document is a different shape of problem. PayPal's free digital FIRA is issued weekly, so one document sits opposite every order settled in that week, and those orders may correspond to shipping bills filed across a much wider date range because shipping and settlement do not move in lockstep. You are now doing many-to-many attribution: apportioning one document across N shipping bills, with amounts that will not tie exactly because platform fees, refunds and FX conversion all sit between the invoice value and the settled value. Your alternative is to buy the transaction-level Custom FIRA, which is precisely the cost we modelled in section four.

A batch aligned to a withdrawal rather than to your commercial activity is the worst case for reconciliation, because the batch boundary carries no business meaning. Nothing about the set of transactions inside it corresponds to anything in your shipping records. You reconstruct the mapping from your own order data every single time.

And with Stripe, where no certificate is issued at all, the granularity question does not even arise at the provider level. You define it yourself when you ask your bank for a FIRC, which means you can in principle get exactly the granularity you want. And you pay for that granularity, per document, forever.

Which provider fits which kind of exporter?

There is no single winner, and any comparison that names one is selling something. What there is instead is a set of segments where the constraints are genuinely different.

Marketplace sellers often do not get a choice at all. Etsy and eBay route seller payouts for Indian sellers through Payoneer, and Walmart's marketplace supports Payoneer, PingPong or Hyperwallet. If your rail is chosen for you, the comparison above is not a purchasing decision. It is a briefing on what documentation you will and will not receive, so that you can plan the gap. For a Payoneer-locked seller the single most important action is establishing, in writing, which of your payment types count as eligible for the automated e-FIRA and what happens to the ones that do not.

Direct D2C sellers on their own storefront have real freedom, and should spend it on granularity rather than on the last twenty basis points. If you ship physical goods against shipping bills and settle frequently, a per-settlement document from a provider that names its RBI construct is worth more than a marginally cheaper rail that batches weekly.

Service exporters have a different problem entirely: purpose codes. Software, consulting and professional services fall in the P08 family, and the mechanism by which your provider assigns a purpose code (and whether more than one code can coexist on the same account) matters more to you than shipping bill granularity, because you have no shipping bills. Ask specifically whether the code is fixed at onboarding or selectable per transaction.

High-ticket B2B exporters run into ceilings. Stripe India applies a Rs 25 lakh per-transaction maximum (Stripe pricing), which simply disqualifies the rail for a single invoice above that line regardless of anything else on the comparison. If your average invoice is large, check the ceiling first and the fee second.

Product limits can disqualify a rail on their own. Razorpay's MoneySaver Export Account does not support refunds and cannot hold funds in foreign currency (Razorpay). If you sell physical goods with a meaningful return rate, no refund support is a hard constraint, not a preference. PayPal India supports international payments only and does not support domestic INR receipts (PayPal India), which is fine if you are purely an exporter and a problem if you wanted one rail for both books.

What actually rules a provider out

• No realisation document at all. You inherit a permanent per-payout cost at your own bank.
• Batch-only granularity when you file many shipping bills. Reconciliation labour that never amortises.
• Eligibility carve-outs on automatic issuance. A silent subset of payments arrives without paper.
• Per-transaction ceilings below your average invoice. The rail simply cannot carry your business.
• No refund support when you sell returnable physical goods.
• No foreign-currency balance when your treasury needs to time conversion.

Provider due-diligence checklist

Run this before you onboard, not after you have moved volume onto the rail and discovered what it does not give you.

Before you onboard

• Confirm the document type and the issuing bank in writing. FIRC, FIRA, FIRS or advice, and which AD bank signs it.
• Confirm whether any payments are excluded from automatic issuance, and get the exclusion criteria in writing rather than as a verbal assurance.
• Confirm the document's granularity against your actual shipment volume. Per transaction, per settlement, or per batch.
• Confirm the purpose code mechanism , and whether more than one purpose code can coexist on the same account if you sell both goods and services.
• Confirm per-transaction and annual ceilings against your largest expected invoice, not your average one.
• Confirm refund handling and whether a foreign-currency balance can be held.
• Confirm the stated RBI construct (PA-CB, PA-CB-I&O, PA-O, OPGSP) and any certificate or registration number backing it.
• Confirm your own AD bank will accept that provider's document before you move volume onto the rail. This is the one people skip and the one that hurts.

What else do exporters ask about provider FIRCs?

Which export payment provider issues a FIRC automatically without me raising a request?

PayGlocal states the FIRA is generated automatically with no request needed. Razorpay generates the FIRC within minutes of the INR credit and emails a One-Click FIRS within 24 hours of settlement. Skydo emails a FIRA on every settlement. Payoneer delivers an AD-bank-issued e-FIRA under Reports & Statements automatically, but only for eligible payments. PayPal issues a free weekly digital FIRA in a Citibank format, which is automatic but batched. PingPong makes a free digital FIRC available for download in the dashboard under Withdraw. Stripe does not issue a FIRC or FIRA at all and instead provides a Standard Chartered payment advice, so with Stripe you must approach your own AD bank for the certificate.

Is a PayPal FIRA enough to close a shipping bill in EDPMS?

The PayPal FIRA format is issued by Citibank and PayPal states it complies with RBI PA-CB guidelines, so it is a bank-issued realisation document rather than a platform statement. The practical problem is granularity, not validity. The free digital FIRA is issued weekly, so one document covers every transaction settled in that week and therefore spans many shipping bills. Your AD bank still has to attribute amounts to individual shipping bills, which means you supply a supporting reconciliation mapping each order to its shipping bill. PayPal also offers a Custom FIRA at transaction level for a fee if your bank insists on a per-transaction document. Confirm with your AD bank which of the two it will accept before you commit.

My provider does not say whether it is PA-CB or OPGSP. Does my bank care?

Banks care about it more than exporters expect, because the AD bank has to satisfy itself about the route the money took before it closes an EDPMS entry. PayGlocal names PA-CB-I&O and PA-O authorisation under Certificate of Authorisation No. 250/2025. Skydo states it is licensed under the PA-CB framework. PayPal states its Citibank FIRA format is PA-CB compliant. PingPong describes itself as an Online Payment Gateway Service Provider with an RBI-approved Liaison Office UIN BGLO19008226 and FCRN F0652. Payoneer, Stripe and Razorpay do not name a framework in the sources reviewed here. Absence of a public statement is not evidence of non-compliance, but it does mean you should ask the provider for its position in writing before your bank asks you.

I get one payout a week covering forty orders. Which provider's document is easiest to reconcile?

A provider that issues one document per settlement is easier than one that issues one document per week. Skydo issues a FIRA on every settlement and settles INR within 24 hours, PayGlocal generates the FIRA automatically on a T+1 INR settlement, and Razorpay produces the FIRC within minutes of the INR credit with the FIRS emailed within 24 hours. Those give you a bounded window of shipments per document. A weekly batch document such as PayPal's free digital FIRA covers everything settled that week, which forces a many-to-many match between one document and forty orders unless you buy the transaction-level Custom FIRA. Granularity, not fee percentage, is what decides whether EDPMS closure can be automated.

Can I use two payment providers for the same IEC without confusing EDPMS?

Yes, and many exporters do, because marketplaces force particular rails while a D2C storefront can use another. EDPMS tracks shipping bills against realisation, not against a provider, so multiple rails are not inherently a problem. The risk is double-attribution: two documents from two providers being applied to the same shipping bill, or a shipping bill left open because each provider's document was assumed to be covering it. Keep a single ledger keyed on shipping bill number that records which provider, which document reference and which amount was applied, reconcile it before you submit anything to the AD bank, and make sure your bank knows in advance that realisation will arrive on more than one rail.

Update history

• 2026-08-13 First published.