This page explains how to add Pay by Bank (US) to your existing Android Drop-in integration.
Requirements
Select the server-side flow that your integration uses:
API reference
Select the endpoint you are using to make payments:
Drop-in configuration
There are no configuration steps specific to Pay by Bank (US) required for Drop-in.
Redirect handling
Your Drop-in integration handles the redirect, so you do not need to do anything additional for Pay by Bank (US).
Payment outcome
Your Drop-in 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.
Through our partner Plaid, 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
You can test the payment flow as well as the chargeback flow.
To go live, you need to await registration with our partner Plaid.
Test the payment flow
In the test environment, the redirect flow mimics the live flow, but not all refusal reasons can be simulated.
To test the payment flow, you can either include a specific amount in your payment request to test a specific scenario, or you can specify custom_balances as your username when you are redirected to confirm the payment.
These are the scenarios you can test:
| Scenario | Username | Amount |
|---|---|---|
| Approved | Not required, but you can use custom_chase, custom_boa, custom_citi, or custom_wellsfargo to test different bank accounts. | USD 3.53 |
| Refused with refusal reason Failed: Risk of unauthorized returns | Not required, but you can use custom_chase, custom_boa, custom_citi, or custom_wellsfargo to test different bank accounts. | USD 27.53 |
| Test custom transaction amounts with different account balances, such as high value transactions or refusals due to an insufficient balance. | custom_balances | Any USD amount |
Entering a username is not required to test the payment flow. Tests without a username all use the same bank account from CITIZENS BANK. The custom_balances username allows you to select from several bank accounts with different balances. For example, if you want to test high value transactions, you can use the custom_balances username and select a bank account with a high balance.
-
Make a test Pay by Bank (US) payment using an amount from the table with scenarios or your own amount.
-
When you are redirected to First Platypus Bank, depending on your test scenario, either enter a username or leave this field blank.
-
Leave the password blank and select Continue.
-
Check the status of test payments in your test Customer Area > Transactions > Payments.
Test the chargeback flow
The chargeback mechanism for Pay by Bank (US) chargebacks relies on the ACH Direct Debit network. You can simulate a Pay by Bank (US) chargeback by providing a username that indicates the chargeback scenario you want to test. In the test environment, the flow goes directly to the Chargeback stage.
-
Send a test Pay by Bank (US) payment request.
-
When redirected to First Platypus Bank, specify the following username:
-
custom_chargeback_rXX where XX is the dispute reason code without the leading R.
You can use any of the ACH Direct Debit reason codes.Example: the username custom_chargeback_r01 triggers a chargeback with reason code R01 for Insufficient Funds.
-
-
Leave the password blank and select Continue.
-
Note that the request succeeds with
resultCode: Authorised.
The chargeback flow starts after the test payment is captured and settled. -
Wait for the CHARGEBACK webhook and check your test Customer Area > Revenue & risk > Disputes.
The webhook and your Customer Area show a chargeback with the return reason code that you specified in the test payment request.
Go live
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.