Dodo Payments FIRA/FIRC for Indian SaaS founders: what to collect before payouts

This guide is for Indian SaaS founders, indie hackers, AI-tool makers, plugin sellers, template creators, and digital-product businesses considering Dodo Payments or another Merchant of Record. It is not legal, tax, GST, FEMA, ODI, or banking advice. It is a practical checklist for the payout-proof questions to answer before moving real revenue.

If you are still comparing Dodo with Stripe Atlas, Paddle, Lemon Squeezy, Razorpay, Cashfree, Skydo, Xflow, or direct bank rails, start with the broader Indian SaaS international payments guide. This page goes narrower: Dodo/MoR payouts, FIRA/FIRC-style proof, GST/LUT caution, and the bank handoff.

01 · MoR checkout vs export proof

A Merchant of Record can simplify the sale side. The MoR is the seller shown to the customer, runs the checkout, collects payment, handles refunds or disputes, and manages tax obligations in supported markets. That is useful if you want to sell a SaaS product globally without building the whole billing and tax machine yourself.

But checkout success is not the same as India-side export proof. Your Indian bank and CA may still ask a different set of questions: who paid you, what was the nature of the receipt, what did the bank statement show, is there foreign inward remittance evidence, what is the invoice trail, and how does GST/LUT apply?

02 · What Dodo says about MoR and payouts

Dodo's Merchant of Record documentation says Dodo becomes the legal seller of your digital products and handles payment, tax, fraud, compliance, disputes, and billing support. That is the core MoR promise: your product is sold through Dodo's seller-of-record layer rather than your business acting as the direct merchant for every customer transaction.

Dodo's payout documentation also separates payout activation from payment acceptance. It says businesses can start accepting payments after sign-up, but payouts require payout details and a compliance review before payouts are enabled. That is a normal payment-platform reality: accepting money and receiving payouts are related, but not identical, steps.

The Dodo payout process page says the payout section consolidates eligible earnings, accounts for fees, refunds, and taxes, and generates payout records. For Indian businesses, Dodo's own disclaimer says INR payouts and global-currency payouts are handled separately, with separate invoices and balance-ledger entries.

03 · The FIRA/FIRC question to ask first

The question Indian founders are really asking is not just "can Dodo accept cards?" It is: when Dodo pays my Indian business, will my bank treat that credit as foreign inward remittance evidence, and what document can I use for FIRA/FIRC or similar bank proof?

Do not assume the answer from a dashboard screenshot. Ask Dodo for the exact payout trail for an Indian seller: remitter name, payout currency, settlement path, payout invoice, ledger entry, bank reference, fees, tax withheld or collected where relevant, and whether the platform provides any document intended for bank or export-compliance follow-up.

Then ask your bank or relationship manager the matching question: if this payout hits my account in this form, with these platform documents and my SaaS invoices, can you issue or support FIRA/FIRC-style inward-remittance evidence? If the bank cannot answer, test with a small payout before moving volume.

04 · INR and global-currency payout trails

Dodo's India-specific payout note matters because it points to more than one trail. An INR wallet payout and a global-currency payout may create different bank statement lines, payout invoices, ledger entries, and CA questions. Treat them as separate evidence chains, not as one generic "Dodo payout."

If the bank statement shows domestic INR from an Indian entity, do not blindly assume it will behave like a direct foreign inward remittance. That does not automatically decide your GST outcome, but it is exactly the point where your CA and bank should review the treatment before you assume LUT / zero-rated export handling.

If the payout trail shows foreign-currency settlement or a clearer cross-border remittance trail, collect the same details anyway. The goal is not to win an argument with your bank. The goal is to make the receipt boring to explain later.

05 · Documents to collect per payout

For every Dodo or MoR payout, save the documents while the transaction is fresh. Do not wait until GST filing, year-end accounting, or a bank query.

• Customer/order record. Customer country, product or subscription, order ID, invoice or receipt, gross amount, currency, and tax charged to the customer if shown.
• Platform payout record. Payout ID, payout invoice, payout date, currency, gross amount, fees, refunds, chargebacks, taxes, and net amount.
• Wallet or ledger entry. INR wallet entry, global-currency wallet entry, balance ledger, and any split between domestic and global payouts.
• Bank credit proof. Bank statement line, remitter name, account credited, UTR/reference, date, INR value, and any bank advice or inward-remittance note.
• Invoice mapping. How the payout maps to customer invoices, subscriptions, refunds, platform fees, and tax line items.
• CA/bank note. The purpose-code, GST/LUT, and FIRA/FIRC position your CA or bank has confirmed for that payout pattern. If the invoice is for SEO or marketing work, compare it with the SEO purpose-code checklist before you scale the rail.

06 · GST, LUT, and zero-rated export caution

Indian SaaS founders often want the cleanest possible answer: "If Dodo is global and my customers are outside India, can I use LUT and treat this as zero-rated export?" The cautious answer is: do not decide from the checkout label alone.

GST export-of-service treatment depends on facts your CA must review: supplier location, recipient location, place of supply, payment flow, contractual role, platform role, invoice trail, and bank proof. A MoR structure can change who is selling to the end customer and what your Indian business is receiving from the platform.

That does not mean a MoR route is bad. It means the zero-rated export file needs a clean explanation. If you already have LUT, make sure the Dodo payout pattern supports your position before revenue grows. If you do not have LUT yet, read the LUT and IGST refund guide before the next billing cycle.

07 · Test with one small payout

The safest operational move is boring: run one small live payout before switching your whole SaaS revenue flow. Use that payout as a proof test with Dodo, your bank, and your CA.

• Ask Dodo what documents should be generated for the payout.
• Confirm what appears on the Indian bank statement.
• Ask the bank whether the evidence is enough for FIRA/FIRC or inward-remittance proof.
• Ask your CA how to book gross revenue, platform fees, tax collected by the MoR, and net payout.
• Check whether the treatment is consistent with your LUT/GST and export-documentation position.

If the answer is clean, you can scale with more confidence. If the answer is messy, you discovered the problem while the amount was still small.

08 · Check before moving volume

Before moving meaningful revenue to Dodo or any MoR, answer these questions in writing: who is the legal seller, what does the customer invoice show, what does your Indian business invoice or receive, what does the bank statement show, which proof supports FIRA/FIRC or inward remittance, and what does your CA say about GST/LUT?

If those answers are fuzzy, fix the recordkeeping before volume grows. A MoR can make global checkout feel simple, but the Indian export file still has to survive bank and tax review.

Sources / further reading: Dodo Payments Merchant of Record documentation; Dodo payout activation documentation; Dodo payout process documentation; RBI Master Direction on Export of Goods and Services. Confirm your exact payout route, FIRA/FIRC position, purpose-code treatment, GST/LUT treatment, and entity setup with your CA, AD bank, and qualified advisors.