Accepting bank debits and transfer payments is a two-step process:
- Enable the payment method in the Dashboard.
- Use the individual payment method guides to implement it.
The Payment Methods API
The new Payment Methods API replaces the existing Tokens and Sources APIs as the recommended way for integrations to collect and store payment information. It works with the Payment Intents API to create payments for a wide range of payment methods.
PaymentMethod object is stateless, relying on the PaymentIntentThe Payment Intents API is a new way to build dynamic payment flows. It tracks the lifecycle of a customer checkout flow and triggers additional authentication steps when required by regulatory mandates, custom Radar fraud rules, or redirect-based payment methods. object to represent the transaction state of a given payment.
|Payment Method|| Payment Methods with
Payment Intents API
| Tokens or Sources with
|ACH Debit||Planned||Supported on Tokens (not Sources)|
|ACH Credit Transfer||Planned||Beta|
|SEPA Direct Debit||Supported||Supported|
|Bacs Direct Debit in the UK||Supported||Not supported|
|BECS Direct Debit in Australia||Supported||Not supported|
If your integration currently uses the Sources or Tokens API, follow the migration guide to transition to the Payment Intents and Payment Methods APIs.
The Sources API
Need to use a payment method that’s not yet supported by the Payment Methods API? Use the Sources API instead.
The main difference between the Payment Methods API and the Sources API is that sources describe transaction state through the status property, which means that each
Source object must be transitioned to a chargeable state before it can be used for a payment.