Search

Are you looking for test card numbers?

Would you like to contact support?

Payment-method icon

Open Banking for API only

Add Open Banking to an existing API-only integration.

Accept Open Banking payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.

Before you begin

These instructions explain how to add Open Banking to your existing API-only integration. The API-only integration works the same way for all payment methods. If you haven't done this integration yet, refer to our API-only integration guide.

Before starting your Open Banking integration:

  1. Make sure that you have set up your back end implementation.
  2. Add Open Banking in your test Customer Area.

Build your payment form for Open Banking

To show Open Banking in your payment form, you need to:

  1. Show a list of available banks to your shopper.
  2. After the shopper selects a bank, pass the corresponding Issuer value to your server. You'll need this to make a payment.

    The available banks are different for test and live payments.

    Test payments

    Bank name Issuer
    Model Bank v2 1

    Live payments

    Bank name Issuer
    Allied Irish Bank 1
    Allied Irish Bank (Corporate) 2
    Barclays 3
    Bank of Scotland 4
    Danske Bank 5
    Danske Bank (Corporate) 6
    First Direct 7
    First Trust Bank 8
    First Trust Bank (Corporate) 9
    Halifax 10
    HSBC Bank 11
    Lloyds Bank 12
    M&S Bank 13
    Nationwide Building Society 14
    National Westminster Bank 15
    Royal Bank of Scotland 16
    Santander 17
    Ulster Bank 18
    Bank of Ireland 19

We provide logos for Open Banking and the issuing banks, which you can use on your payment form. For more information, refer to Downloading logos.

You can also get the issuer list from the /paymentMethods response, as explained in the API-only integration guide.

In your /paymentMethods request, specify:

The list of issuing banks are included in the object with type: openbanking_UK.

Make a payment

In your /payments request, specify:

  • paymentMethod.type: openbanking_UK
  • paymentMethod.issuer: The shopper's bank. Specify this with the Issuer value that corresponds to this bank.
  • returnUrl: The URL where the shopper will be redirected back to after they complete the payment.

{
   "merchantAccount":"YOUR_MERCHANT_ACCOUNT",
   "reference":"open banking test",
   "amount":{
      "currency":"GBP",
      "value":1000
   },
   "paymentMethod":{
      "type":"openbanking_UK",
      "issuer":"1"
   },
   "returnUrl":"https://your-company.com/..."
}

The /payments response contains:

  • resultCode: RedirectShopper
  • details: Array that contains the key parameter name and the corresponding data type that you should expect when the shopper is redirected to your returnURL. You need to submit this value in your /payments/details request when handling the redirect.
  • action: Object containing information about the redirect.
  • action.paymentData: Value that you need to submit in your /payments/details request when handling the redirect.
  • action.url: Link to where you should redirect your shopper.
  • action.method: GET or POST. The HTTP request method that you should use. After the shopper completes the payment, they will be redirected back to your returnURL using the same method.
    The redirect method depends on your payment method configuration and the length of the data included in the request, so make sure that your integration can handle both HTTP GET and HTTP POST methods.

{
   "resultCode": "RedirectShopper",
   "action": {
      "data": {},
      "method": "GET",
      "paymentData": "Ab02b4c0!M=...",
      "paymentMethodType": "openbanking_UK",
      "type": "redirect",
      "url": "https://test.adyen.com/hpp/skipDetails.shtml?brandCode=openbanking_UK..."
   },
   "details": [
   {
      "key": "payload",
      "type": "text"
   }
   ],
   ...
}

Handle the redirect

To complete an Open Banking payment, you need to redirect the shopper to the issuer's website. After the shopper is redirected back to your website or app, make a /payments/details request to check the payment result.

For more information and detailed instructions, refer to Handling redirects.

Present the payment result

Use the resultCode that you received in the /payments/details response to present the payment result to your shopper.

The resultCode values you can receive for Open Banking are:

resultCode Description Action to take
Authorised The payment was successful. Inform the shopper that the payment has been successful.
You will receive the funds in 2-3 days.
Cancelled The shopper cancelled the payment while on their bank's website. Ask the shopper whether they want to continue with the order, or request that they select a different payment method.
Pending The shopper has completed the payment but the final result is not yet known. It may take minutes or hours for the Open Banking payments network to confirm this. Inform the shopper that you've received their order, and are waiting for the payment to be completed.
You will receive the final result of the payment in an AUTHORISATION notification.
Refused The payment was refused by the shopper's bank. Ask the shopper to try the payment again using a different payment method.
If a shopper completed the payment but failed to return to your website or app, you will receive the outcome of the payment in an AUTHORISATION notification.

Test and go live

Before accepting live Open Banking payments, test your integration using the following details: 

Bank name Issuer ID Username Password
Model Bank v2 1 mits mits

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

See also