Stripe FIRC in India: payment advice, SCB email, and what your bank may ask for
Stripe is useful for Indian SaaS founders selling globally, but the export-compliance trail still lives outside the checkout. The important detail: Stripe does not directly issue your FIRC. You receive payment advice and use it with your bank.
If you are an Indian founder using Stripe for international card payments, the payout hitting your bank account is only one part of the export workflow. Your CA or bank may still ask for proof that the foreign money came in against an export invoice. That is where payment advice, FIRC, purpose codes, e-BRC, and EDPMS start to overlap.
If you are still choosing between an Indian Stripe account, Stripe Atlas, Dodo Payments, Paddle, Lemon Squeezy, Razorpay, Cashfree, or bank-transfer rails, start with our Indian SaaS international payments guide first. This page goes deeper on the Stripe-specific FIRC and SCB payment-advice trail.
If the alternative you are evaluating is Dodo Payments or another Merchant of Record, the proof question changes. We separated that into a Dodo/MoR FIRA/FIRC guide so the Stripe-specific SCB flow does not get mixed with MoR payouts.
This guide is deliberately practical. It is not legal advice, and it does not try to replace your CA or Authorized Dealer bank. It tells you what Stripe publicly says it provides, what the FIRC trail usually means for an Indian service exporter, and what to collect before your next payout becomes quarterly cleanup work.
01 · What Stripe gives Indian exporters
Stripe's India documentation is clear on two things that matter for export payments. First, Stripe accounts in India are currently invite-only and export transactions require additional export setup. Second, for Indian users processing international transactions, Stripe says Standard Chartered Bank (SCB) sends a payment or payee advice to the registered Stripe email address.
The important distinction: Stripe/SCB provides payment advice. Stripe does not directly issue your FIRC.
Stripe's India FIRC/payment-advice support page says the payment advice is evidence of export payments received from outside India, and that you present it to your bank to obtain a Foreign Inward Remittance Certificate.
For a founder, this means the useful record is not only the Stripe Dashboard payout. It is the whole chain: customer charge, export invoice, Stripe export payout, SCB payment advice, bank inward-remittance proof, and then whatever your CA needs for GST or FEMA reconciliation.
02 · Payment advice vs FIRC
A payment advice is a bank-issued record that evidences an export payment. In Stripe's India flow, the payment advice comes from SCB for export payouts processed through Stripe. It may show payment references, payout details, and export transaction information that helps your bank map the remittance to your business.
A FIRC is the certificate or bank proof that verifies inward foreign remittance into India. Stripe's own support wording points exporters back to their bank for this step: the payment advice is presented to the bank to obtain the FIRC. That makes payment advice a key input, not the final compliance answer by itself.
The practical mistake is treating the Stripe payout as the end of the export trail. Your bank and CA may still need to connect the payout to the right invoice, purpose code, customer country, and GST treatment. If that chain is not clean, the pain usually appears later: during GST refund filing, e-BRC self-certification, or a bank compliance query.
03 · Documents to collect before asking your bank
Before you ask your bank for FIRC or inward-remittance evidence, collect the records that let the trade-services desk understand the transaction without a long back-and-forth. For each Stripe export payout, keep:
- Export invoice. Invoice number, client name, country, service description, currency, and amount.
- Stripe payout record. Payout ID, date, gross export charges included, fees, and net amount.
- SCB payment/payee advice. The advice email or attachment sent for the export payout.
- Bank credit proof. The bank statement line, UTR/reference where available, date of credit, and INR amount.
- Purpose-code context. The service category used for export onboarding and any bank declaration you filed.
- GST/LUT context. Whether the invoice was raised under LUT without IGST, or with IGST paid and refund expected.
The goal is not to drown your bank in files. The goal is to make the match obvious: this invoice, this Stripe payout, this SCB advice, this bank credit, this purpose code.
04 · Purpose codes and export onboarding in Stripe
Stripe's India export documentation says Indian businesses accepting international payments must declare those transactions as exports and provide export-related details during onboarding or API flows. It also says Stripe supports a subset of purpose codes because of partner-bank requirements.
This is where service founders should slow down. The purpose code is not a decorative field. It describes the nature of the foreign receipt: software services, consultancy, business services, travel, goods, and so on. A generic or mismatched purpose code can make the later FIRC/e-BRC/GST trail harder to explain.
Stripe's docs also use conditional language around IEC. For Visa/Mastercard export transactions, Stripe says IEC is required for physical goods; for services it is optional unless specific conditions apply, such as accepting Amex international payments or taking benefits under India's Foreign Trade Policy. Confirm your exact setup with Stripe, your bank, and your CA before relying on a blanket rule.
For primary-source purpose-code context, use RBI's Report of the Working Group on Balance of Payments Manual for India, Attachment IV: New Purpose Codes for Reporting Forex Transactions (FETERS). It includes receipt codes such as P0802 for software consultancy/implementation and P1006 for business and management consultancy/public-relations services. Verify the exact code with your bank because the bank's reporting is what downstream systems see. If the Stripe receipt is for SEO or digital-marketing work, the SEO services purpose-code guide gives a more specific operating checklist.
05 · FIRC vs e-BRC vs EDPMS
These terms are related, but they are not interchangeable:
- FIRC / FIRA / payment advice is the bank-side proof that foreign money came into India. In the Stripe flow, SCB payment advice is an input to the FIRC request with your bank.
- e-BRC is the DGFT-side realization certificate that exporters self-certify against bank-transmitted inward remittance data. It often matters for GST refund and export-benefit evidence.
- EDPMS is the RBI-side monitoring system for export realization and closure. Your AD bank operates the closure workflow; exporters typically work through the bank.
The Stripe payout touches all three indirectly. The payout generates payment proof. The payment proof helps the bank and exporter establish realization. The realization trail then matters for e-BRC and EDPMS closure. If any link is vague, the issue usually does not show up on payout day; it shows up when you file, refund, or reconcile.
06 · Common founder mistakes
Most Stripe export issues are not dramatic. They are small mismatches that become expensive when a CA has to rebuild the file months later.
- Saving only the Stripe payout screenshot. Keep the SCB payment advice and bank credit proof too.
- Using an invoice description that does not match the purpose code. If the invoice says consulting and the reporting says software, expect questions.
- Ignoring LUT status. If you export services without paying IGST, your LUT and realization proof need to stay in sync for refund work.
- Assuming FIRC automatically becomes e-BRC. The FIRC/payment-advice trail and e-BRC self-certification are connected, but they are not the same task.
- Waiting until the quarter ends. By then the email thread, payout batch, invoice, and purpose-code context are scattered across tools.
07 · Check your setup before the next payout
The best time to fix the Stripe/FIRC trail is before your next export payout lands. At minimum, you want to know whether your invoices, LUT, purpose-code choice, bank documentation, e-BRC workflow, and EDPMS closure route are internally consistent.
If you are already receiving foreign payments, do not wait for a GST deficiency memo or a bank query to discover the missing link. Run a quick readiness check, then send the report to your CA or bank before the next payout cycle.
Check your Stripe export-payment readiness.
NiryatBox's free readiness checker asks a few questions about your export setup and flags LUT, e-BRC, EDPMS, purpose-code, and bank-handoff gaps. No bank login, no signup, and it gives you a shareable report for your CA.
Use it before the next Stripe payout, not after the quarter is already messy.
Run the readiness checker →Made in India. Questions: support@niryatbox.com.
Sources / further reading: Stripe support on FIRC/payment advice for international transactions in India; Stripe docs for accepting international payments from India; RBI Master Direction on Export of Goods and Services; RBI Report of the Working Group on Balance of Payments Manual for India, Attachment IV: New Purpose Codes for Reporting Forex Transactions (FETERS). Confirm your exact bank process, purpose code, IEC requirement, and GST treatment with your CA / AD bank.