Fee behaviour on connected accounts
Understand how to configure the billing behaviour for new connected accounts.
The controller.
property on v1/accounts
determines the set of billing behaviours you can expect for direct charges and product usages that occur on this connected account. This doc details the behaviour of the different values it can have.
Note
Any activity occurring at the platform account level is billed to your platform regardless of the controller.
value on your connected accounts. For example, Stripe charges the platform directly for destination charges (with or without on_
) and card account updates for cards stored on your platform account.
Selecting billing behaviour
You can only set the controller.fees.payer property when you create an account.
The following sections describe the behaviour of each value.
account
Stripe collects fees directly from your connected account. We don’t charge any Connect fees to it or to your platform.
Any application fees that your platform bills to the connected account are in addition to Stripe fees.
You can set the payer type to account
when you create connected accounts. Accounts created with type=standard
also have this value.
application
The platform pays payment fees for direct charges and fees for Stripe products such as Radar, Card Account Updater, and Instant Payouts. For complete details, see the table below.
The platform also pays Connect fees for these accounts .
We recommend that you monetise payments and Stripe products where the platform is billed by collecting fees from your connected accounts.
You can set the payer type to application
when you create connected accounts.
Platforms that pay Stripe payment fees for direct charges can access dedicated reports.
See Platform Reporting for direct charge payment fees paid by platform.
application_custom or application_express
application_
and application_
are assigned to accounts created with type=custom
and type=express
, respectively. Their billing behaviours for direct charges and connected account usage of Stripe products matches the historical behaviour of Custom and Express accounts. For complete details, see the table below.
We recommend that you monetise payments and Stripe products where the platform is billed by collecting fees from your connected accounts.
You can’t set the payer type to application_
or application_
when you create connected accounts. They only apply to accounts created with type=custom
or type=express
.
List of fee behaviours for payer values
Product Category | account | application | application_custom | application_express |
---|---|---|---|---|
Stripe payment processing fees | Connected Account | Platform | Connected Account | Connected Account |
Interchange Plus Payment Fees | Connected Account | Platform | Platform | Platform |
Dispute fees | Connected Account | Platform | Connected Account | Connected Account |
Instant Payouts | Connected Account | Platform | Platform | Platform |
LPM Payment Failure Fees | Connected Account | Platform | Connected Account | Connected Account |
Premium Payouts | Connected Account | Platform | Platform | Platform |
Invoicing and Subscriptions | Connected Account | Platform | Platform | Platform |
Radar | Connected Account | Platform | Varies | Varies |
Terminal Add-ons | Connected Account | Platform | Connected Account | Connected Account |
Stripe Tax | Connected Account | Platform | Platform | Platform |
3D Secure | Connected Account | Platform | Varies | Varies |
Adaptive Acceptance | Connected Account | Platform | Platform | Platform |
Card Account Updater | Connected Account | Platform | Platform | Platform |
Checkout Add-ons | Connected Account | Platform | Platform | Platform |
Instant bank account verifications | Connected Account | Platform | Platform | Platform |