2.9% + $0.30 and $2/Month: Stripe Connect Fees for U.S. Platforms

Stripe Connect combines standard card processing fees with Connect-specific charges, including a per-active-account fee, payout fees, and optional Instant Payout costs, and together these determine what your platform actually keeps. The baseline U.S. card rate is 2.9% plus $0.30 per transaction, with add-ons for international cards and currency conversion. Who absorbs each charge depends entirely on how you configure your charge type and fee-payer settings.


TL;DR:

  • Stripe’s processing costs for domestic transactions are 2.9% plus $0.30 per charge, increasing by 1.5% for international cards and 1% for currency conversion, which can significantly raise total fees.
  • Connect-specific charges include a $2 monthly fee per active account, payout fees, and optional instant payout costs around 1.5%, affecting cash flow and overall profitability depending on payout frequency and account volume.
  • Fee responsibility varies by charge type, with platform settings determining who pays processing fees and dispute costs, which can lead to unexpected expenses if misconfigured.
  • High dispute or refund costs often outweigh minor rate savings, making configuration choices and dispute management strategies more impactful on profit margins than seeking lower processing rates.
  • Using features like download gating and paid revisions can prevent unpaid work and disputes, helping studios manage Connect costs and improve overall margins.

Audome
Keep Paid Audio Work On Track
Audome helps studios manage revisions, control final downloads, and collect client payments in one secure collaboration workspace.

Explore Audome

Table of Contents

How Stripe Connect fees are structured

Every Connect fee falls into one of two buckets: standard payment processing charges that apply to any Stripe account, and Connect-specific charges that only apply because you’re operating a platform with connected accounts.

How Stripe Connect fees are structured — overview diagram

On the processing side, Stripe charges 2.9% plus $0.30 for a successful U.S. card transaction. That base rate can climb when a card is issued outside the United States or when currency conversion happens: an additional 1.5% applies to international cards, and roughly 1% more applies for currency conversion when the transaction requires it. These add-ons stack, so a foreign card paid in a converted currency can carry noticeably higher costs than a domestic U.S. transaction.

On the Connect side, platforms typically encounter:

  • A per-active-account fee of $2 per month for each connected account that processes volume.
  • A payout fee that includes a small percentage plus a fixed amount on standard payouts to connected accounts.
  • An Instant Payout fee of approximately 1.5%, subject to a minimum charge, for accounts that want same-day access to funds.
  • Dispute fees that shift depending on charge type and negative-balance responsibility settings.

Stripe’s Connect pricing page confirms these figures and notes that exact costs vary depending on the Connect account type and plan a platform chooses. Importantly, Stripe’s pricing documentation states there are no setup fees or monthly fees under standard pricing: you pay per transaction and per Connect event, not a flat subscription just to keep the integration running. Businesses with higher volume or specialized needs can request custom pricing, which typically brings a lower blended rate in exchange for a sales conversation and a volume commitment. Most platforms start on standard pricing and only move to custom terms once monthly processing volume is substantial enough to justify the negotiation.

Key fee components with example math

Worked examples make the fee structure concrete. Here’s what a $100 charge and a $1,000 charge cost under standard U.S. card pricing.

  1. $100 domestic card charge: 2.9% of $100 is $2.90, plus the $0.30 fixed fee, for a total processing cost of $3.20. Net proceeds before any platform fee: $96.80.
  2. $1,000 domestic card charge: 2.9% of $1,000 is $29.00, plus $0.30, for a total of $29.30. Net proceeds before any platform fee: $970.70.
  3. $1,000 international card with currency conversion: add 1.5% ($15.00) for the international card and roughly 1% ($10.00) for conversion, on top of the $29.30 base, bringing total processing costs to about $54.30.

Stripe’s standard U.S. rate is 2.9% plus $0.30 per successful card charge, and that single line item is the number most platforms should model first, since it applies to nearly every transaction before any Connect-specific fee is added.

Once processing fees are subtracted, the platform’s application fee comes out of what remains. If a platform charges a $50 application fee on that $1,000 transaction, the connected account receives $970.70 minus $50, or $920.70, assuming the platform absorbs no additional cost.

Payment transaction fee calculation flow

Who pays what: fee-payer behavior by charge type

Stripe Connect supports three charge types, and each one changes who is financially responsible for processing fees, disputes, and refunds.

  • Direct charges: the connected account is the merchant of record, the charge appears on their Stripe balance, and processing fees come out of their funds by default.
  • Destination charges: the platform creates the charge, funds land on the platform’s balance first, and the platform decides how much (if any) to transfer to the connected account via the destination parameter.
  • Separate charges and transfers: the platform charges the customer directly and later creates a separate transfer to the connected account, giving the platform full control over timing and amount.

Fee responsibility is not fixed. Stripe lets platforms set who pays processing fees using controller.fees.payer and related account configuration, and who absorbs negative balances using defaults.responsibilities.fees_collector, according to Stripe’s platform pricing tools documentation. A platform can choose to absorb all processing costs itself, pass them entirely to the connected account, or split responsibility by charge type.

Dispute liability follows the same logic. For destination charges and for separate charges and transfers, Stripe generally debits the platform’s balance for the dispute and its fee. For direct charges, Stripe first attempts to debit the connected account, though the platform’s actual exposure depends on how negative-balance responsibility is configured, per Stripe’s Connect disputes documentation. Getting this configuration wrong is one of the more common reasons platforms are surprised by a dispute bill months into operating.

Connect-specific charges and their timing

Beyond the per-transaction rate, several Connect charges accrue on a recurring or per-event basis, and understanding their timing matters for cash flow forecasting and monthly reconciliation.

  • The per-active-account fee is $2 per month, charged for each connected account that processes at least one transaction that month, not for dormant accounts.
  • Standard payouts cost 0.25% plus $0.25 per payout, so batching smaller payouts into fewer, larger transfers reduces the number of times this fee applies.
  • Instant Payouts run about 1.5% with a minimum charge, a premium worth reserving for connected accounts that genuinely need same-day funds rather than offering it by default to everyone.
  • Refunds generally do not return the original processing fee, and the application fee is only returned to the connected account if the platform sets refund_application_fee to true, according to Stripe’s refund and dispute guidance.

Stripe documents a per-active-account charge of $2 per month for Connect platforms, a cost that adds up quickly for marketplaces with thousands of low-volume connected accounts and is worth modeling before scaling recipient count aggressively. Grouping infrequent, low-value payees into fewer settlement windows, rather than paying them out (and getting charged) every week, is one of the simplest ways to control this line item.

Pricing options and platform strategies

Platforms generally choose between two philosophies: absorb Stripe’s fees as a cost of doing business, or pass them through to connected accounts as a condition of using the platform.

  1. Platform-pays: the platform covers processing and Connect fees itself, which simplifies the pitch to connected accounts but compresses platform margin unless offset elsewhere.
  2. Stripe-managed passthrough: connected accounts see and absorb Stripe’s fees directly, which preserves platform margin but requires clear disclosure to avoid disputes over unexpected deductions.
  3. Blended/custom pricing: platforms with meaningful volume can request custom, IC±style pricing from Stripe, often a lower blended rate in exchange for negotiated terms, per Stripe’s monetization guidance.

Stripe’s Platform Pricing Tool lets platforms configure application_fee_amount to collect platform revenue directly out of each transaction, effectively monetizing payment volume rather than treating Stripe as a pure pass-through cost. This is also where controller.fees.payer settings determine whether Stripe’s own processing fee is deducted from the platform’s cut or the connected account’s cut before the application fee is calculated.

Pro Tip: Run both pricing models against your last three months of transaction volume before committing. The math often favors platform-pays for high-retention products and passthrough for high-churn, price-sensitive marketplaces.

Platforms considering how platform-pays and Stripe-managed pricing compare for creator and media businesses can see a fuller breakdown in how these models play out for media SaaS platforms.

How fees affect unit economics and how to reduce net cost

Processing fees are generally deductible as ordinary business expenses for U.S. companies, according to Stripe’s tax resources, so they reduce taxable income even as they reduce gross revenue. That doesn’t eliminate the margin hit, but it softens it, and it’s worth flagging to whoever handles your bookkeeping so processing costs are categorized consistently.

A few levers actually move the needle on net cost:

  • Negotiate volume pricing once monthly processing consistently exceeds the threshold where Stripe will discuss custom rates.
  • Steer payment-method mix toward domestic cards where possible, since international and currency-conversion add-ons are avoidable in many cases.
  • Batch payouts on a weekly or monthly schedule instead of daily, cutting the number of 0.25% plus $0.25 payout fees you incur.
  • Reserve Instant Payouts for connected accounts that request them, and consider marking up that fee slightly rather than absorbing it for everyone.

Pro Tip: Reducing disputes matters more than shaving basis points off your processing rate. A single chargeback often costs more in fees and account risk than months of incremental rate savings.

Payout timing and who bears dispute costs under different charge types are covered in more detail in this breakdown of payment links versus invoices.

Audome perspective: managing Connect costs with paywalls and revisions

Studios using Stripe Connect often lose money not to processing rates but to unpaid deliveries and revision disputes. Gating final downloads behind payment, an approach detailed in strategies for restricting file downloads, prevents the scenario where a client receives finished work and then disputes the charge. Pairing that with paid revision limits reduces the endless-revision cycle that erodes studio margin long before Stripe’s fees ever enter the picture. Tight reconciliation between project delivery and Stripe Connect payout status also keeps studios from carrying negative balances while waiting on client payment.

What the fee breakdown actually tells platform operators

The conventional advice on Stripe Connect fees treats the percentage rate as the main variable to optimize, and that’s backward.

The bigger blind spot is disputes and refunds. Platforms spend real effort minimizing processing rates while leaving refund_application_fee unset and charge-type defaults unexamined, which means a single wave of disputes or refunds can cost more than a year of rate shaving. If you’re building or running a Connect platform, prioritize configuration decisions (charge type, fee-payer settings, refund logic) before you chase a better blended rate. Background on how platform economics shape creator and music businesses more broadly is available from DRVVYN Sound’s overview of digital platform economics.

— Kreg

A simpler way for studios to handle Connect billing

Studios running their own Stripe Connect integration often end up building the same things from scratch: download gates, revision counters, and refund reconciliation logic. The workspace can include features that lock final downloads until payment is received and automatically bill for revisions past a chosen limit, so the paywall and revision logic sit next to the project rather than requiring custom code.

Audome

For studios that would rather configure these rules once than maintain Stripe logic indefinitely, Audome’s Studio and Pro plans start at $12.50 per month for Studio and $48 per month for Pro, both billed monthly or at a lower annual rate. Review the plans and start a trial to see how paid revisions and download gating fit your workflow.

FAQ

What are Stripe fees in the USA?

Stripe’s standard U.S. card processing rate is 2.9% plus $0.30 per successful transaction, with no setup or monthly fee under standard pricing. International cards add roughly 1.5%, and currency conversion adds about 1% more when it applies.

How much is the Stripe fee for $1,000?

International or currency-converted transactions cost more due to the additional 1.5% and 1% add-ons.

Does Stripe take 20%?

A platform’s total deduction can look much higher than Stripe’s own fee if it also applies a large application fee on top, but that additional amount is the platform’s own charge, not Stripe’s.

Why are Stripe fees so high?

card processing costs. The total can climb when international cards, currency conversion, Instant Payouts, or per-active-account and payout charges stack on top for Connect platforms. Reviewing charge type and fee-payer configuration often reveals costs that were passed through inefficiently rather than the base rate itself being the problem.

Who pays the Stripe fee on a refund?

Refunds generally do not return the original processing fee to the platform or connected account, and the application fee is only returned if refund_application_fee is set to true, according to Stripe’s refund documentation. Platforms should build this setting into their refund logic to avoid connected accounts losing the application fee unexpectedly.

Scroll to Top