Review 1 of 6 · Payment processors for ITIN and international founders
The short version: Stripe is the right first processor for a legitimate SaaS, digital, or service business running on a US LLC — it works with no SSN and no ITIN, and it's why forming a US company unlocks payments for founders in countries Stripe doesn't serve directly.
It is also unforgiving. If you run high-chargeback e-commerce, Stripe can close your account, hold funds up to 180 days, and refund your customers — leaving you with neither the money nor the sale.
Know which of those two businesses you are before you build on it.
Why Stripe matters so much to this audience
Stripe doesn't operate in most of the countries our readers live in. Pakistan, Nigeria, Bangladesh, Egypt, Vietnam, and many others are not on Stripe's supported list.
The route around that is not a workaround — it's the intended structure: form a US LLC, get an EIN, open a US business account, and apply to Stripe as a US business. No SSN or ITIN required.
That single fact is the reason the entire non-resident LLC formation industry exists. For a large share of founders reading this, Stripe access is the business case for the company.
Eligibility: what you actually need
- A US LLC or corporation in good standing
- An EIN
- A US business bank account with real US routing and account numbers — Mercury, Wise, Relay, and similar all work
- A passport for identity verification
- A live website (more on this below — it's the most common rejection cause)
You do not need: an SSN, an ITIN, a US address for yourself, or a US partner.
The country-matching rule that trips people up
Your Stripe account country must match your business entity's country. A US LLC needs a US Stripe account and US bank details.
What fails: trying to connect a foreign bank account with only IBAN/SWIFT details to a US Stripe account. It won't work, and founders lose weeks discovering it. You need US routing and account numbers, which is why the Mercury/Wise/Relay question comes before the Stripe question.
The application and verification experience
Stripe's onboarding is fast, but verification includes a review of your website — and this is where most avoidable rejections happen.
The single most common rejection cause
Missing Terms of Service, Privacy Policy, and Refund Policy on your site.
This comes up constantly in founder communities, and it's entirely preventable. Stripe's reviewers look for them. A site with a beautiful product page and no policy pages reads as an incomplete business.
What else causes rejection
- Placeholder or "coming soon" website. Stripe wants to see what you actually sell.
- Business description that doesn't match the website. If your application says "software consulting" and the site sells supplements, that's a flag.
- Restricted or borderline category. Stripe publishes a prohibited-business list. Read it before applying, not after.
- Inconsistent details across your LLC filing, EIN letter, bank account, and application.
If you're rejected
Read Stripe's stated reason carefully — it's usually more specific than founders assume. Fix the actual root cause. Then wait 2–4 weeks before reapplying.
Reapplying immediately with unchanged circumstances triggers automatic rejection. This is the same pattern as Mercury: the system reads a rapid resubmission as an attempt to game the review rather than a corrected application.
Fees
- 2.9% + $0.30 per successful US card charge [VERIFY CURRENT]
- +1% for international cards [VERIFY CURRENT]
- +1% for currency conversion [VERIFY CURRENT]
- First payout: 7–14 days after your first successful charge, then on your normal schedule
So a European customer paying a US-based Stripe account in EUR costs roughly 4.9% + $0.30 once international card and conversion fees stack. Worth modelling honestly if most of your customers are outside the US — it changes the comparison against Merchant-of-Record platforms considerably.
The shutdown pattern — the section that matters most
This is where Stripe reviews written for US founders mislead this audience badly, because the consequences of a Stripe closure are far worse when you're abroad.
How it escalates
Stripe's risk system operates on continuous scoring. The escalation ladder is roughly:
- Rolling reserve imposed — commonly 10%–25% of volume held on a 90-day rolling basis for businesses judged higher-risk [VERIFY CURRENT: reserve percentages vary and Stripe does not publish a standard schedule]
- Payouts paused pending review
- Account closed, with funds held up to 180 days
- In some cases, customer refunds issued — Stripe can refund your customers approximately five days after closure
That fourth step is the one founders don't see coming. You don't merely lose access to the money temporarily; the transactions can be reversed entirely.
The named triggers
Chargeback ratio approaching 1%. This is the industry tripwire, and it's the single most important number to watch. Card networks impose monitoring programmes above it, and processors act well before that.
Sudden volume spikes. A successful flash sale or viral moment can look identical to fraud in a risk model. If you're planning a launch that will multiply your normal volume, contact Stripe in advance rather than after.
Fulfilment delays. Dropshippers are the classic casualty here — long shipping times generate "item not received" disputes, disputes generate chargebacks, and the model breaks.
Category drift. Starting as a SaaS and adding a supplements line without telling Stripe.
The message founders report seeing
The recurring wording across Shopify community forums and Reddit is some variant of: "We identified a high volume of unauthorized charges on your account, and payouts are now paused."
[VERIFY: this phrasing is widely reported by founders; treat as a reported pattern rather than official Stripe language.]
Liability survives closure
Stripe is explicit about this and it's worth stating plainly: closing your account does not release you from liability for negative balances, disputes, or chargebacks. If chargebacks land after closure, you still owe them.
What actually improves outcomes
Founders who recover from a reserve or hold report the same things:
- Responding immediately with fulfilment evidence — tracking numbers, delivery confirmations, signed contracts, usage logs for SaaS
- Demonstrating active dispute prevention — clear billing descriptors, visible refund policy, responsive support
- Bringing the chargeback ratio down and keeping it down
- Having a coherent, consistent business story that matches what they told Stripe at onboarding
Founders who lose the funds are usually those who can't produce evidence that goods or services were actually delivered.
Country reality
Stripe's country dimension works differently from a bank's. Once you're operating through a US LLC, Stripe is underwriting your business, not your passport.
What that means:
- Your country of residence matters less to Stripe than to Mercury or Relay
- But consistency still matters — an account registered in the US, logged into daily from one country, with customers in a third, and a high-risk model, compounds risk scoring
- Use your real setup. Don't mask your location with a VPN. Inconsistency is a flag; honest geography is not.
The founders who have trouble aren't the ones logging in from Lagos or Karachi. They're the ones running a chargeback-heavy model from anywhere.
What Stripe works well with
Universal, and this is a genuine advantage:
- Shopify (as a gateway where permitted), WooCommerce, custom checkouts
- Mercury, Wise, Relay as payout destinations
- QuickBooks, Xero for reconciliation
- Extensive API and developer tooling — the reason technical founders default to it
Alternatives
If your model is chargeback-prone or high-risk:
- Merchant-of-Record platforms (Paddle, Lemon Squeezy, Polar, Dodo) — they become the seller of record and assume chargeback liability. Higher cost (~5%+), but they absorb the risk that would kill your Stripe account. They also require no US LLC at all, which makes them the fastest legitimate start for founders in Stripe-blocked countries.
- High-risk processors (PaymentCloud, Durango, Easy Pay Direct) — built for CBD, supplements, coaching, adult. Major caveat: almost all require an SSN or ITIN from a 25%+ owner. Durango is the most offshore-friendly of the three.
For buyer trust alongside cards: PayPal, as a secondary rail only — its own hold behaviour is worse than Stripe's.
[CLIENT STORY PLACEHOLDER: SaaS founder with a live product, complete policy pages, and clean documentation — approved smoothly, no reserve. Show what the site looked like. Illustrates that the bar is passable for legitimate businesses.]
[CLIENT STORY PLACEHOLDER: An e-commerce founder hit with a rolling reserve after a chargeback spike, and what evidence resolved it. Illustrates the recovery path. Use with permission and don't overstate the outcome — some don't recover.]
The honest bottom line
Stripe is right for you if: you run SaaS, digital products, or services on a US LLC; your chargeback exposure is low; you can maintain a real website with proper policies; and you want the best developer tooling and integration ecosystem available.
Stripe is wrong as a single point of failure if: you run dropshipping, high-ticket coaching, supplements, or anything with elevated dispute rates. Not because Stripe is unfair, but because your model is structurally mismatched to a processor that prices risk this way.
The rule regardless of model: have a second processing option configured before you need it. A Stripe closure with no backup means zero revenue on the day it happens, and setting up an alternative takes weeks you won't have.
Should you use a service to apply?
No. Stripe's application is self-serve, free, and there's no privileged channel — anyone claiming a relationship that guarantees approval is selling something that doesn't exist.
What genuinely determines your outcome: a real website with complete policy pages, an accurate business description, consistent documents, and a legitimate model. All within your control, all free to fix.
Where help earns its keep is upstream — forming the entity correctly, getting the US bank account that Stripe requires, and making sure your site has what reviewers look for before you apply rather than after you're declined.
This review reflects information verified as of July 2026 and publicly reported user experiences across Shopify community forums, Reddit, and founder communities. Stripe's fees, reserve practices, and policies change — verify anything marked [VERIFY CURRENT] on Stripe's own site before relying on it. Nothing here is financial or legal advice. We are not affiliated with Stripe and receive no compensation from them.
Frequently asked questions
Can non-resident founders use Stripe without a US bank account?+
Yes. Stripe can pay out to a non-US bank account in many countries, and it does not require a US bank account to activate. However, payout speeds and currency conversion fees are better when you connect a US bank account. For founders processing significant volume, connecting a Mercury or Wise Business account for USD payouts is the standard setup.
Why does Stripe put new accounts on a payout hold?+
Stripe holds payouts for new accounts during an initial review period, typically 7–14 days, while it assesses the account's risk profile. The hold is extended if Stripe identifies unusual transaction patterns, high dispute rates, or a mismatch between the stated business model and actual transactions. Keeping your business description accurate and processing a few small transactions before large ones reduces the hold period.
Question not answered here? Email daniel@keystonebridgeglobal.com. We add answers to this page as they come in.
Want the shortlist for your situation?
Which provider is right depends on your country, your volumes, and whether you can travel. Check your country's path or book a consultation and we'll tell you which of these we'd open first — and which to skip.