Payment method support for Connect platforms and marketplaces
Learn about requirements and limitations when enabling payment methods for Connect platforms.
When using Connect for platforms and marketplaces, different payment methods are available depending on factors such as country location, business type, account type, and charge type. Select a payment method to learn about its level of Connect support.
For more information about enabling payment methods with Connect, refer to the following:
- Account capabilities
- Manage payment methods for connected accounts
- Payment method support
Payment methods
Payment method:
If you use Connect, you must take the following into consideration before you enable and use ACH Direct Debits.
Request ACH Debit capabilities for your connected accounts
Set the us_bank_account_ach_payments capability to active on your platform account, and for any connected accounts you want to enable for ACH debits. You can also request more account capabilities.
Note
Stripe automatically refunds the application fee to your platform account when the destination charge for an ACH debit fails. Learn about fees for failed payments.
Merchant of record
The charge type of Connect payments might change the merchant of record. The charge type can also change:
- The merchant of record shown on the mandate
- The business shown on confirmation emails
- The business shown on microdeposit reminder emails
The merchant of record determines the Stripe account authorised to create payments with a particular PaymentMethod. To learn more about sharing this authorisation across multiple connected accounts, see PaymentMethod and Mandate cloning.
PaymentMethod and mandate cloning
You can collect customer bank accounts on the platform account and clone ACH Direct Debit payment methods. Cloning these methods allows you to save customer bank accounts for later use on connected accounts. When you clone ACH Direct Debit payment methods, Stripe duplicates the mandate authorisation to the connected account, but we don’t send any new mandate confirmation emails.
Caution
If a mandate is authorised for a PaymentIntent or SetupIntent on_behalf_of a connected account, you can’t use that mandate with a different connected account.
When collecting a bank account that you intend to clone to connected accounts, you must communicate to the customer that their authorisation extends to connected accounts on your platform. For example, you can communicate this message to a customer through the mandate terms. Failure to communicate this message to your customers could result in customer confusion and increase the risk of disputed payments.