Collecting US payments from India: Stripe, ACH, net-30 and invoicing as GTM friction
A playbook for Indian B2B founders selling to US buyers: Stripe, ACH, invoices, wire, and net-30 without slowing deals or cash.
The short version. Cash from a US buyer should feel like part of the sale and never like a surprise after the signature. Pick the rail before the proposal. For an Indian B2B company, the least painful path is usually a USD invoice with card or wire first, Stripe where your entity and category fit, ACH only when your setup can support it, and net-30 after trust. Sell the product; remove the pay doubt.
Before you start:
- US buyers lose heat when pay rails feel foreign after they say yes
- Stripe helps when cards, invoices, retries, and your eligibility line up
- ACH feels local to US finance teams; promise it only after your bank or processor can deliver
- Net-30 is credit; grant it after PO proof, AP contact, signed order, and pay history
Step 1: Map the buyer's pay path, then the drag is visible
Founder, treat cash collection as part of discovery, right beside pain, budget, urgency, and legal risk. Name the rail. A buyer who can expense a corporate card today moves differently from a controller who needs a PO, a vendor file, a US tax form, and a bank account match before cash leaves. That gap can decide whether your signed deal turns into cash this month.
Write the pay path in the same notes where you keep the buying map; I would put it beside Founder-led sales for technical founders who have never sold rather than inside a finance folder. Buyers reveal this early when you ask how vendors get paid. Ask once. Procurement, AP, the budget owner, and the legal signer each hold a different piece of the cash route.
Step 2: Choose Stripe when checkout speeds trust, then small deals close cleanly
Stripe can make a US buyer feel at home when card payment, hosted invoices, receipts, and simple retries matter more than procurement theater. Keep it boring. Stripe publishes docs for supported markets, cards, invoices, ACH debit, and Billing; your actual access still depends on the entity, product category, bank setup, risk review, and export rules that apply to you. A card link can save a pilot that would die inside vendor setup.
Use Stripe for the deals where speed beats ritual and the buyer owns a card. Indian founders get into trouble when they pitch Stripe as the whole answer before checking eligibility, chargeback risk, foreign exchange, and the buyer's AP habit. Tools do not sell. The contract still needs a clean price, a tax-safe invoice, a due date, and a rail the buyer recognizes.
- Card-owned pilots
- Founder-approved trials
- Low refund risk
- Clear export category
- Wire would stall
Step 3: Offer ACH only when your rails support it, then larger invoices feel normal
ACH is a US bank-to-bank rail, and US finance teams often treat it as normal vendor plumbing. Confirm the setup first. An Indian company may reach ACH through a US entity, a bank partner, a platform account, or a processor, yet the right path depends on underwriting, mandate rules, account naming, and the way funds land back in India. Never promise ACH in a proposal before the processor can honor it.
Buyers ask for ACH when they want bank pull, predictable ledger entries, cleaner audit trails, and fewer card headaches. Add another lens: buyer trust. ACH debit can feel risky to a customer if your brand is new, the invoice is vague, the mandate flow looks odd, or the vendor name differs from the contract. Larger invoices need calm finance teams more than clever checkout pages.
Step 4: Put net-30 behind proof, then credit stops leaking cash
Net-30 sounds enterprise-friendly, and it can help when a serious buyer has a real AP cycle. Treat it as credit. A tiny Indian startup can become the lender for a much larger US customer when the founder grants terms without PO proof, buyer authority, AP contact, and a late-fee stance. Revenue on a slide will not pay salaries while the invoice waits.
Set the rule before the deal gets emotional. First-time buyers pay by card or wire unless procurement blocks every other route and the sponsor proves internal ownership. Repeat buyers earn terms after clean pay behavior; a warm call earns nothing. I would put cash due date beside pipeline stage in The only GTM metrics that matter before Series B, since bookings without cash discipline make founders lie to themselves.
- Signed order from buyer
- Named AP contact
- Vendor setup complete
- Prior invoice paid cleanly
- Late fees stated plainly
Step 5: Make the invoice procurement-ready, then finance has nothing to decode
US AP teams do not enjoy detective work. Make the PDF dull. Put the legal name, registered address, GSTIN if relevant, PAN if needed, bank details, currency, due date, PO field, service period, and contact email where a clerk expects them. Your CA owns tax fields; GTM owns whether the buyer can approve the bill without a Slack hunt.
Foreign vendors often get asked for Form W-8BEN-E, the IRS form that helps a US payer classify a non-US entity. Keep it ready. A clean packet should match the contract name, invoice name, bank beneficiary, tax form, and email domain, especially when expansion adds cost centers, PO owners, security checks, and finance habits like the ones covered in Retention and expansion: the GTM engine founders ignore until Series B. Tiny mismatches create giant delays.
What goes wrong?
Founders hide cash talk until the verbal yes. Then the deal slows. A US champion may love the product and still lose the week to vendor setup, legal name mismatch, missing tax form, purchase order policy, or a bank team that dislikes unfamiliar foreign wires. Silence creates the drag your CRM will label as legal review.
A buried pay path can make outbound look broken; buyers reply, take demos, praise the workflow, and stall when AP sees foreign bank coordinates. That stall lives downstream from the email, unlike the reply-rate problems covered in the cold outbound benchmarks piece. Blame the right leak. Pipeline health includes the path from yes to cash.
Step 6: Pick the default rail by deal type, then cash lands without drama
For most Indian founders selling early US B2B deals, the least painful route is a small set of defaults. Start there. Card via Stripe works when the buyer can expense a pilot; invoice plus wire works when procurement needs a vendor record; ACH works after your bank or processor can support it; net-30 works only after proof of pay behavior. One rule beats custom drama on every deal.
Write the default inside your sales notes before pricing leaves your inbox. Small pilots get card links when Stripe fits your entity and risk profile. Larger vendor-led deals get USD invoices with wire details, PO fields, AP contacts, and a named due date. Repeat accounts can move to ACH or terms after clean pay history.
- Self-serve pilot: card link
- Services project: invoice plus wire
- Repeat US account: ACH where supported
- Enterprise vendor file: PO plus net-30
- Expansion order: match the AP rail
Common questions
What's the least painful way to get paid by US customers when I'm an Indian company?
Usually, use a USD invoice with card or wire as the default, then add ACH only when your bank or processor can actually support it. Stripe helps for card-led pilots and hosted invoices if your entity, category, export setup, and risk profile fit. Net-30 belongs behind buyer proof, AP contact, PO clarity, and prior pay behavior.
Can an Indian company use Stripe to collect from US customers?
Yes, when Stripe supports the Indian entity, business category, bank setup, and risk profile involved in the sale. Founders should treat Stripe as a tool for cards, hosted invoices, retries, and some bank rails where eligible. Access can vary by product, use case, country route, and underwriting; the sales process should keep wire or another approved rail as a backup.
Should I create a US entity just to offer ACH?
Rarely for the first US deals. A US entity adds tax, bank, legal, accounting, and ops work that can distract a founder before the sales motion proves itself. ACH can help larger invoices feel local, but the entity choice should follow deal size, buyer demand, payback, and counsel guidance.
Is net-30 safe for a first US customer?
Sometimes, if the buyer has a real AP process and the sponsor proves authority. Safer defaults are card, wire, deposit, or upfront invoice terms until the account shows clean pay behavior. Net-30 should require a signed order, AP contact, vendor setup proof, and a clear due date in the contract.