This page explains how to add Pay by Bank (US) to your existing Android Components integration.<\/p>\n
Select the server-side flow<\/a> that your integration uses:<\/p>\n\n Select the endpoint you are using to make payments:<\/p>\n\n There is no need for additional configuration specifically for Pay by Bank (US).<\/p>\n 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:<\/p>\n This works in the same way for both the Sessions flow<\/a> and the Advanced flow<\/a>.<\/p>\n Launch and show Pay by Bank (US) using a Component class name depending on the Components version that you have integrated with:<\/p>\n Create the Component as follows:<\/p>\n\n Your Components integration handles the redirect, so you do not need to do anything additional for Pay by Bank (US).<\/p>\n Your Components integration gets the payment outcome, so you do not need to do anything additional for Pay by Bank (US).<\/p>\n We strongly recommend capturing Pay by Bank (US) payments immediately, to reduce the risk of insufficient funds at the time of capture. <\/p>\n 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.<\/p>\n 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.<\/p>\n Pay by Bank (US) supports tokenization of the shopper's payment details for recurring transactions.<\/p>\n 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.<\/p>\n<\/div>\n To make recurring payments, refer to Tokenization<\/a> to:<\/p>\n You can test the payment flow as well as the chargeback flow.<\/p>\n To go live, you need to await registration with our partner Plaid.<\/p>\n In the test environment, the redirect flow mimics the live flow, but not all refusal reasons can be simulated.<\/p>\n 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<\/strong> as your username when you are redirected to confirm the payment.<\/p>\n These are the scenarios you can test:<\/p>\nAPI reference<\/h2>\n
Component setup<\/h2>\n
Import the module<\/h3>\n
\n
Create the Component<\/h3>\n
\n
Redirect handling<\/h2>\n
Payment outcome<\/h2>\n
Capture<\/h2>\n
Recurring payments<\/h2>\n
\n
Test and go live<\/h2>\n
Test the payment flow<\/h3>\n