Payment-method icon

BACS Direct Debit Drop-in integration

Add BACS Direct Debit to an existing Drop-in integration.

This page explains how to add BACS Direct Debit to your existing Web Drop-in integration.

Requirements

Select which endpoint you are using:

Import resources for v6

If you are using Web Drop-in v6, import the resources you need for BACS Direct Debit:

import { AdyenCheckout, BacsDirectDebit} from '@adyen/adyen-web'

API reference

Select which endpoint you are using:

Drop-in configuration

There are no configuration steps specific to BACS Direct Debit required for Drop-in.

Recurring payments

If you have a recurring or subscription business model, we recommend tokenizing the shopper's payment details. When you create a shopper token from a BACS Direct Debit payment, we store the shopper's payment details with the token. You can use this token to make recurring BACS Direct Debit payments.

You need to use the /payments endpoint to make recurring payments with the token.

We strongly recommend that you request explicit permission from the shopper if you intend to make recurring BACS Direct Debit payments. Being transparent about the payment schedule and the amount they will be charged will reduce the risk of chargebacks.

Under the Direct Debit Guarantee, if there is a change in the collection date or the amount, you must give the shopper advance notice of the payment.

Create shopper token

Tokenize the shopper's payment details when you make the initial BACS Direct Debit payment.

  1. When you make a POST request to /payments to make a payment, additionally include:
  • shopperReference: Your unique ID for this shopper.
  • paymentMethod.storePaymentMethod: true.
  1. When you receive the RECURRING_CONTRACT webhook, store the pspReference. This is the token you will need to make recurring payments for this shopper.

Make recurring payments

We strongly recommend giving shoppers advance notice before each payment.

For each recurring payment for this shopper, make a BACS Direct Debit payment with a POST request to the /payments endpoint, and additionally include:

  • paymentMethod.recurringDetailReference or paymentMethod.storedPaymentMethodIdfor API v49 and above. This is the pspReference returned in the RECURRING_CONTRACT webhook when you created the token.
  • shopperReference: The same unique shopper ID you used to create the shopper token.
  • shopperInteraction: ContAuth.
{
   "merchantAccount":"YOUR_MERCHANT_ACCOUNT",
   "reference":"BACS test payment",
   "shopperReference":"YOUR_UNIQUE_SHOPPER_ID_IOfW3k9G2PvXFu2j",
   "shopperInteraction":"ContAuth",
   "amount":{
      "currency":"GBP",
      "value":49900
   },
   "paymentMethod":{
      "type":"directdebit_GB",
      "storedPaymentMethodId":"7219687191761347"
   },
   "countryCode":"GB",
   "shopperLocale":"en_gb",
   "returnUrl":"https://your-company.com/checkout?shopperOrder=12xy.."
}

If the payment was successfully received the response will contain the resultCode Received and a pspReference, which is our unique identifier for this transaction. You can track whether the payment was successful using webhooks.

Test and go live

Before accepting live BACS Direct Debit payments, test your integration using the following details:

Account Name Account Number Sort Code
David Archer 40308669 560036

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

Before you can accept live BACS Direct Debit payments, you need to submit a request for BACS Direct Debit in your live Customer Area.

See also