Payment method support for platforms and marketplaces

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.

Merchant of record and statement descriptors

The charge type of Connect payments might change the default statement descriptor and the merchant name that appears on the customer’s bank statement. The charge type can also change:

• The merchant of record shown on the mandate
• The merchant shown on confirmation emails
• The merchant 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.

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.

Connect and settlement

Settlement speed is generally controlled at the platform level. The table below shows a comprehensive view of settlement timing by account and charge type.