Open banking Drop-in integration

On this page, you can find additional configuration for adding open banking to your Drop-in integration.

Before you begin

Before starting your open banking integration:

1. Contact our Support Team to add open banking in your test Customer Area.

2. Make sure you've integrated Drop-in v5.27.0 or later.

API reference

You don't need to send additional fields for open banking. To see optional fields that you can send for all payment methods, choose the endpoint you integrated:

• /sessions: This is the default with Drop-in v5.0.0 or later.
• /payments: If you implemented an additional use case.

Drop-in configuration

Optional configuration

You can add the following optional configuration:

If you want to add optional configuration, include this in a configuration object. The following example shows how to configure Drop-in to remove the bank logos, and preselect Bank of Scotland:

const openBankingConfiguration = {
  showImage: false, // Optional. Set to **false** to remove the bank logos from the open banking form.
  issuer: "uk-bankofscotland-oauth2" // Optional. Set this to an **id** of an open banking issuer to preselect it.
};

Include the openBankingConfiguration object when creating a configuration object for Drop-in:

List of issuer IDs

For the UK, where you can show the issuer list in the payment form, the available banks are listed below:

Chargebacks

In rare scenarios, it's possible that you do not receive the funds even after receiving a successful AUTHORISATION webhook. The successful AUTHORISATION webhook means that the payment has passed the verifications that the issuer and our open banking partners run on the shopper account, and that the bank transfer was initiated successfully. However, the payment can still fail for the following reasons:

• The shopper cancelled the transaction. Banks in some countries (including Germany and Poland) allow shoppers to cancel bank transfers until midnight of the day of the transaction.
• Some banks process transactions with a delay and do not block the funds for an authorized open banking payment. For example, if the shopper completes a open banking payment on a Saturday, the bank might only process it on Monday. If the shopper has withdrawn sufficient funds in the meantime, the payment will fail.

In these cases, Adyen is not informed that the transaction failed. We also don't know whether the bank might still process it later.

On our side, the status of the payment is SentForSettle until we receive the funds. You can check the status of the payment in your Customer Area.

If we have not received the funds after 8 weekdays, the status of the payment becomes Settled, then Chargeback, and you receive a CHARGEBACK webhook.

In case we receive the money after this point, you receive a CHARGEBACK_REVERSED webhook.

Test and go live

We provide different test issuers for testing open banking payments, including testing for failed or cancelled payments. Select the corresponding test issuer name, for example Demo Open Banking Redirect (payment cancelled), to simulate a cancelled payment scenario.

We recommend that you test each scenario before you go live.

Check the status of test payments in your Customer Area > Transactions > Payments.

Before you can accept live open banking payments, contact our Support Team to add open banking in your test Customer Area.

See also