Stripe usually feels simple right up to the first payout. A founder closes a sale, checks the balance, and notices the deposit is lower than expected. Nothing is broken. The gap is the fee stack, and that stack matters more than many realize.
That's the full answer to what are the fees for stripe. The headline rate is only the starting point. A startup's actual cost depends on ticket size, customer geography, payment rail, subscription tooling, disputes, and any extra products layered onto checkout. For an early-stage company, those details affect gross margin, CAC payback, and runway.
This is the operating view of Stripe pricing. Not just the published rate card, but the effective rate a startup should model before setting prices or forecasting cash.
Table of Contents
- Decoding Your Stripe Bill What Founders Need to Know
- The Core Rate Stripe's Standard Transaction Fees
- Beyond the Basics Common Additional Stripe Fees
- Fees for Specific Stripe Products and Services
- Putting It All Together Sample Fee Calculations
- How Startups Can Reduce Stripe Fees
- FAQ Common Questions About Stripe Fees
Decoding Your Stripe Bill What Founders Need to Know
Most founders don't have a Stripe problem. They have a modeling problem.
The confusion starts because Stripe is easy to adopt. There are no monthly or setup fees for core processing, and the first published number looks straightforward. But a finance lead shouldn't stop at the headline. The right question is: what fee stack applies to this company's actual transactions?
A startup selling only domestic card payments has one cost profile. A SaaS company with recurring billing has another. A business that sells across borders, deals with disputes, or pays out sellers has a very different one. That's why the same payment processor can feel inexpensive for one team and margin-heavy for another.
For a practical company profile and ecosystem context, founders often start with a basic company overview like this Stripe profile for startups.
What the effective rate means
The effective rate is total Stripe cost divided by total payment volume. That's the number that should show up in a startup's forecast model.
It matters because published processing fees don't fully capture what finance sees in its monthly close. Teams need to account for:
- Base processing fees tied to the payment method used
- Cross-border costs if customers pay with international cards or in another currency
- Operational costs such as disputes and reconciliation gaps
- Product add-ons if the business uses subscriptions, invoicing, tax tooling, payouts, or fraud products
Practical rule: A founder shouldn't ask, “What's Stripe's fee?” The better question is, “What does one blended month of payments cost for this business model?”
What good modeling looks like
A clean Stripe model usually starts with transaction buckets. Domestic cards sit in one bucket. International cards sit in another. Subscription volume gets separated from one-time charges. Disputes get tracked as their own line item rather than buried in payment fees.
That shift changes decisions. It helps a team price subscriptions correctly, choose better payment methods for larger invoices, and avoid surprise margin compression late in the month.
The Core Rate Stripe's Standard Transaction Fees
The base layer is still the easiest part to understand. Stripe's standard online card pricing in major markets is built around 2.9% + $0.30 per successful domestic card charge, according to Stripe's pricing page. The same pricing page also lists other payment methods such as Instant Bank Payments at 2.6% + $0.30 and Klarna at 5.99% + $0.30. On a $100 domestic card payment, the fee comes to about $3.20 before add-ons.
Why the fixed fee matters so much
Founders often focus on the percentage and ignore the fixed component. That's a mistake.
The 2.9% portion scales with transaction size. The $0.30 portion doesn't. That means smaller transactions absorb a heavier fee burden as a share of revenue, while larger transactions carry less drag from the fixed fee. Low-price SaaS plans, usage-based billing with frequent microcharges, and marketplaces with small orders feel this most sharply.
A simple way to think about it is this: one part of the fee behaves like rent, the other behaves like tax. The percentage rises with the payment amount. The fixed fee shows up every time, even on a small charge.
Payment context changes the rate
Stripe doesn't price every rail the same way. The headline online card rate applies to that specific card scenario. Payment method and channel matter.
For example, Stripe also publishes in-person Terminal payments at 2.7% + $0.05, which can produce a different effective cost profile than online checkout. That distinction matters for startups with hybrid sales models, field collections, or event-based payments.
The published rate is useful as a benchmark. It isn't the same thing as the company's actual blended cost.
For finance planning, this section is the baseline only. A startup should treat it as the first line in the model, not the final answer.
Beyond the Basics Common Additional Stripe Fees
A startup's true Stripe cost is usually higher than the card rate because additional fees can layer on top of the base transaction. Stripe-related fee analysis commonly cites a 1.5% fee for international cards, a 1.0% currency-conversion fee, a $15 non-refundable dispute fee, Stripe Billing at 0.7% of subscription volume, and Invoicing at 0.4% to 0.5% per paid invoice. The same analysis also notes that ACH direct debit is 0.8% capped at $5, while ACH credit payments are $1 per transaction. In mixed-use situations, effective rates can rise above 6% according to this Stripe fee breakdown.
If then triggers founders should watch
The cleanest way to model these fees is with trigger logic.
- If the customer uses an international card, add the international card fee.
- If settlement requires currency conversion, add the FX fee.
- If the business uses recurring billing tools, add the subscription-tooling fee on that volume.
- If a charge becomes a dispute, add the dispute fee even though the original transaction has already been processed.
- If the company moves some volume to ACH, model that rail separately because it prices differently.
Many startups don't have one payment flow. They have several. Domestic self-serve SaaS, outbound invoicing, enterprise renewals, and cross-border purchases can all sit in the same Stripe account while generating different economics.
The fees that usually surprise teams
International card fees often create the first surprise. A company may think it has domestic pricing because it's incorporated in one market, but the fee trigger usually depends on the customer card context, not the founder's assumptions.
Disputes are the second surprise. The $15 non-refundable dispute fee creates hard-dollar cost even before revenue recovery gets sorted out. That can distort margins fast in categories with weak customer recognition, unclear descriptors, or billing confusion.
Then there's recurring tooling. Subscription companies often think of billing software as operating expense rather than payment cost. In practice, if a fee is tied directly to collected subscription volume, finance should include it in the payment stack when calculating contribution margin.
A startup that charges recurring subscriptions internationally can end up paying a very different effective rate than a startup taking one-time domestic card payments, even if both say they “use Stripe.”
A better way to forecast
Instead of applying one blanket fee assumption to all revenue, split revenue into practical lanes:
| Revenue lane | What to include in the fee model |
|---|---|
| Domestic card sales | Base card fee |
| International card sales | Base card fee plus international layer |
| Converted currency sales | Add FX layer |
| Subscription revenue | Add billing tooling if enabled |
| Invoiced collections | Add invoicing and rail-specific costs |
| Disputed payments | Track dispute cost separately |
That structure won't eliminate payment expense. It will make it predictable.
Fees for Specific Stripe Products and Services
Stripe often starts as payment processing and then expands into infrastructure. That's useful operationally, but it changes the cost picture because add-on products are billed separately and stack on top of the base payment fee.
Independent cost modeling for software businesses found that once international card fees, Billing, Tax, fraud tooling, dispute fees, and currency conversion are included, a typical effective cost can rise from the headline 2.9% + 30¢ to roughly 7.8% to 12.3%, as described in this fee modeling analysis. The same analysis notes that Connect lists payout fees at 0.25% + 25¢ per payout, while FX fees on Stripe pricing start at +0.5% depending on the market.
Which product changes which cost
The practical way to evaluate add-ons is product by product.
| Stripe Product | Typical Fee Structure | Ideal For |
|---|---|---|
| Billing | Additional fee on subscription volume | SaaS and recurring revenue businesses |
| Invoicing | Fee per paid invoice | B2B companies sending invoices |
| Tax | Separate product charge | Teams that want automated tax handling |
| Radar | Separate fraud-related charge | Businesses with fraud exposure |
| Connect | Payout-related fees and platform costs | Marketplaces and multi-party payment flows |
That table isn't just a pricing summary. It shows where many startup models drift off course. Teams often price their own product using only card-processing assumptions, then discover later that the business also depends on subscription management, tax support, fraud controls, or payouts.
Billing and invoicing deserve separate treatment
For recurring revenue companies, Stripe Billing belongs in the unit economics model, not hidden in software overhead. If subscriptions are the revenue engine, the fee on subscription volume is part of what it costs to collect that revenue.
The same goes for invoicing. A B2B startup with many paid invoices may have a different effective rate from a product-led company collecting mostly through card checkout, even when monthly revenue looks similar on the surface.
A founder considering incorporation and setup options tied to payments operations may also review Stripe Atlas resources for startups alongside processing costs.
Connect changes marketplace math
Marketplace operators need to be especially careful. Connect introduces payout economics that don't exist in a simple direct-to-customer SaaS flow.
That means the platform's take rate can get squeezed from both sides. Stripe takes the base transaction fee on incoming payments, then Connect can add payout-related costs on money moving out. A marketplace with small seller payouts can feel the fixed portion more acutely, much like low-ticket transactions on the collection side.
The right model for Stripe isn't one line called “payment fees.” It's a modular stack tied to how money comes in, what tools sit on top, and where money goes next.
For operators, that modular view is the only reliable one.
Putting It All Together Sample Fee Calculations
The abstract version of fee modeling is useful. The transaction-level version is the one finance can use. Stripe fee analysis notes that the standard online card or wallet fee is 2.9% + $0.30 per successful charge, in-person Terminal is 2.7% + $0.05, ACH direct debit is 0.8% capped at $5, ACH credit is $1, and wire payments are $8. It also notes that international cards commonly add +1.5% and currency conversion commonly adds +1%. That framework appears in this Stripe fee explainer.
Scenario one domestic SaaS subscription
Take a $25 monthly subscription paid by domestic card.
Base payment fee:
- 2.9% of $25 = $0.725
- Fixed fee = $0.30
- Base total = $1.025
If the business also uses Billing on that subscription volume at 0.7%, then:
- 0.7% of $25 = $0.175
Total Stripe-related fee:
- $1.025 + $0.175 = $1.20
Net before any other operating costs:
- $25.00 - $1.20 = $23.80
Effective Stripe-related rate:
- $1.20 / $25 = 4.8%
This is why low-price recurring plans need careful modeling. The fixed fee and subscription-tooling fee together take a bigger bite than founders often expect.
A team building AI-heavy SaaS pricing can use the same approach it uses in infrastructure planning. This guide to GPT-5 API cost modeling for startups is a useful parallel because the discipline is similar: model the blended cost, not the headline unit price.
Scenario two international ecommerce sale with FX
Take a $200 sale paid with an international card that also requires currency conversion.
Calculation:
- Base card fee: 2.9% of $200 = $5.80
- Fixed fee: $0.30
- International card fee: 1.5% of $200 = $3.00
- Currency conversion fee: 1% of $200 = $2.00
Total fee:
- $5.80 + $0.30 + $3.00 + $2.00 = $11.10
Net payout before other costs:
- $200.00 - $11.10 = $188.90
Effective rate:
- $11.10 / $200 = 5.55%
The key point isn't just the number. It's that a founder using the domestic card rate for global sales would materially understate payment cost.
Scenario three larger B2B invoice over ACH
Take a $2,000 collection handled through ACH direct debit.
Calculation:
- 0.8% of $2,000 = $16
- ACH direct debit is capped at $5
Total payment fee:
- $5
Net payout before other costs:
- $1,995
This example shows why startups should map payment method to use case. Cards are convenient, but they aren't always the right economic choice for larger B2B collections.
How Startups Can Reduce Stripe Fees
Most startups can't eliminate payment fees, but they can reduce avoidable ones. That starts with operating choices, not wishful thinking.
The first lever is payment method design. If a company collects larger B2B invoices, ACH direct debit can be materially cheaper than card processing because it's priced at 0.8% capped at $5 rather than the standard card model. That doesn't fit every workflow, but it can make a meaningful difference on larger payments.
Operational levers that usually matter
- Route larger invoices differently: Card convenience is expensive when invoice sizes rise. Teams collecting bigger B2B payments should evaluate ACH as the default path.
- Separate domestic and international assumptions: A blended fee forecast only works if international volume is modeled explicitly rather than averaged away.
- Treat disputes as a process problem: Clear descriptors, billing communication, and clean refund handling can reduce downstream fee leakage.
- Audit add-ons quarterly: Teams often enable products during launch and forget to revisit whether each one still earns its keep.
- Review ticket size economics: If the business relies on small transactions, bundling usage or increasing billing intervals may improve the effective rate.
A short walkthrough can help founders think through fee controls in practice.
Credits and negotiated pricing
Another lever is startup credits and partner programs. Some founders can offset payment-related costs through ecosystem programs, and a directory like this roundup of startup credits and perks can help teams identify relevant offers and eligibility paths.
As volume grows, founders should also revisit whether standard pricing still makes sense. At that stage, the conversation shifts from published rates to account-specific economics and payment mix. A company with stable volume, cleaner fraud patterns, and predictable collections has a better basis for that conversation than one that only knows its top-line revenue.
Good payment cost management isn't about hunting for one magic fee reduction. It's about matching payment rail, product setup, and operational discipline to the company's revenue model.
That work belongs with finance and operations, not just engineering.
FAQ Common Questions About Stripe Fees
Does Stripe charge monthly or setup fees
For core processing, Stripe notes there are no monthly or setup fees. That's one reason the platform feels simple at the start. The complexity comes later from payment-method-specific pricing, disputes, refunds, and add-on products rather than from a standard platform subscription.
Where can founders see the detailed fee breakdown
Stripe documents a Fees report that users can view from the Dashboard, Reporting API, or Sigma. Fee data is available 96 hours after a fee affects the balance, and Stripe notes that the report covers most fees but excludes some items such as Terminal device purchases, Stripe Capital fees, Atlas fees, and certain post-paid invoiced fees, according to Stripe's fees reporting documentation.
For founders looking to extend that discipline into broader vendor savings and perk discovery, this startup perks directory is one place to organize cost-reduction work outside payments too.
How should a startup audit its real Stripe cost
The practical answer is monthly reconciliation by fee type. Finance should export itemized fee data, bucket it by payment rail and product, and compare actual fee totals with the assumptions in the operating model. That's how a team turns “what are the fees for stripe” from a vague question into a repeatable closing process.
Are Stripe fees tax deductible
Payment processing fees are generally treated as a business expense. The accounting treatment depends on the company's jurisdiction and advisor guidance, so founders should confirm classification with their accountant rather than relying on a generic blog answer.
Credit for Startups is a free directory for founders who want to find credits, perks, and non-dilutive funding across cloud, AI, developer infrastructure, and startup operations. Teams that are trying to stretch runway can browse Credit for Startups to compare offers, eligibility paths, and application routes in one place.
