This page explains how to add Pay by Bank (US) to your existing Android Components integration.
Requirements
Select the server-side flow that your integration uses:
API reference
Select the endpoint you are using to make payments:
Component setup
There is no need for additional configuration specifically for Pay by Bank (US).
Import the module
Import the library and include the module for Pay by Bank (US) as described in the Android Components integration guide, using a value depending on the Components version that you have integrated with:
- For v5.8.0 or later use paybybank-us.
- For v5.7.1 or earlier use instant.
This works in the same way for both the Sessions flow and the Advanced flow.
Create the Component
Launch and show Pay by Bank (US) using a Component class name depending on the Components version that you have integrated with:
- For v5.8.0 or later use PayByBankUSComponent.
- For v5.7.1 or earlier use InstantPaymentComponent.
Create the Component as follows:
Redirect handling
Your Components integration handles the redirect, so you do not need to do anything additional for Pay by Bank (US).
Payment outcome
Your Components integration gets the payment outcome, so you do not need to do anything additional for Pay by Bank (US).
Capture
We strongly recommend capturing Pay by Bank (US) payments immediately, to reduce the risk of insufficient funds at the time of capture.
Adyen completes the checks on the shopper's bank account, including a balance check and risk checks, at the time of authorization. However, the issuing bank does not hold the authorized funds and thus it is possible that the account balance is no longer sufficient by the time you capture the payment. For that reason, you should capture Pay by Bank (US) payments as soon as possible.
However, even with immediate capture there is still a risk of insufficient funds at the time of capture, because capturing is an asynchronous process on the ACH Direct Debit network.
Recurring payments
Pay by Bank (US) supports tokenization of the shopper's payment details for recurring transactions.
We strongly recommend that you ask explicit permission from the shopper if you intend to make future recurring payments. Being transparent about the payment schedule and the amount reduces the risk of chargebacks.
To make recurring payments, refer to Tokenization to:
- Create a token through the initial payment.
- Use the token in subsequent payments.
- Manage tokens.
Test and go live
We recommend that you test various scenarios, such as approved payments, authentication errors, and payments cancelled by the shopper. You can check the status of test payments in your Customer Area > Transactions > Payments.
To go live, you need to add Pay by Bank (US) in your live Customer Area. Our partner Plaid then registers your merchant account with participating banks, including some of the largest banks in the US. The registration takes up to one business week from the moment Plaid has started the process. During this time, your shoppers cannot connect their bank account to Plaid. For this reason, you cannot accept live Pay by Bank (US) payments until the registration process is completed.
We send you a paymentMethod.created webhook when you can start accepting live Pay by Bank (US) payments.