Pesquisar

Are you looking for test card numbers?

Would you like to contact support?

Atenção, esta página não se encontra disponível em Português
Payment-method icon

BACS Direct Debit Component

Add BACS Direct Debit to your existing iOS Components integration.

Our BACS Direct Debit Component renders BACS Direct Debit in your payment form and collects shopper information.

When making an BACS Direct Debit payment, you need to:

Before you begin

This page explains how to add BACS Direct Debit to your existing iOS Components integration. The iOS Components integration works the same way for all payment methods. If you haven't done this integration yet, refer to our Components integration guide.

Before starting your BACS Direct Debit integration:

  1. Make sure that you have set up your back end implementation for making API requests.
  2. Add BACS Direct Debit in your test Customer Area.

Show BACS Direct Debit in your payment form

Include BACS Direct Debit in the list of available payment methods. You don't need to collect any information from the shopper in your payment form.

  1. Specify in your /paymentMethods request:

The response contains paymentMethod.type: directdebit_GB.

We provide logos for BACS and Direct Debit which you can use on your payment form. For more information, refer to Downloading logos.

Make a payment

When the shopper proceeds to pay, you need to:

  1. From your server, make a /payments request, specifying:
    • paymentMethod.type: Set this to directdebit_GB.
    • shopperEmail: The shopper's email address.
curl https://checkout-test.adyen.com/v66/payments \
-H "x-API-key: YOUR_X-API-KEY" \
-H "content-type: application/json" \
-d '{
  "merchantAccount":"YOUR_MERCHANT_ACCOUNT",
  "reference":"YOUR_ORDER_NUMBER",
  "amount":{
    "currency":"GBP",
    "value":1000
  },
  "{hint:paymentComponentData.paymentMethod from app}paymentMethod{/hint}":{
    "type":"directdebit_GB",
    "holderName":"S. Hopper",
    "bankAccountNumber":"00000002",
    "bankLocationId":"043001"
  },
  "shopperEmail":"s.hopper@gmail.com"
}'
# Set your X-API-KEY with the API key from the Customer Area.
adyen = Adyen::Client.new
adyen.api_key = "YOUR_X-API-KEY"
 
response = adyen.checkout.payments({
  :amount => {
    :currency => "GBP",
    :value => 1000
  },
  :reference => "YOUR_ORDER_NUMBER",
  :paymentMethod => {
    :type => "directdebit_GB",
    :holderName => "S. Hopper",
    :bankAccountNumber => "00000002",
    :bankLocationId => "043001"
  },
  :merchantAccount => "YOUR_MERCHANT_ACCOUNT",
  :shopperEmail => "s.hopper@gmail.com"
})
// Set YOUR_X-API-KEY with the API key from the Customer Area.
// Change to Environment.LIVE and add the Live URL prefix when you're ready to accept live payments.
    Client client = new Client("YOUR_X-API-KEY", Environment.TEST);
    Checkout checkout = new Checkout(client);

    PaymentsRequest paymentsRequest = new PaymentsRequest();

    String merchantAccount = "YOUR_MERCHANT_ACCOUNT";
    paymentsRequest.setMerchantAccount(merchantAccount);

    Amount amount = new Amount();
    amount.setCurrency("GBP");
    amount.setValue(15000L);
    paymentsRequest.setAmount(amount);

    DefaultPaymentMethodDetails paymentMethodDetails = new DefaultPaymentMethodDetails();
    paymentMethodDetails.setType("directdebit_GB");
    paymentMethodDetails.setHolderName("S. Hopper");
    paymentMethodDetails.setBankAccountNumber("00000002");
    paymentMethodDetails.setBankLocationId("043001");
    paymentsRequest.setPaymentMethod(paymentMethodDetails);

    paymentsRequest.setReference("YOUR_ORDER_NUMBER");
    paymentsRequest.setShopperEmail("s.hopper@gmail.com");

    PaymentsResponse paymentsResponse = checkout.payments(paymentsRequest);
// Set your X-API-KEY with the API key from the Customer Area.
$client = new \Adyen\Client();
$client->setXApiKey("YOUR_X-API-KEY");
$service = new \Adyen\Service\Checkout($client);

$params = array(
  "amount" => array(
    "currency" => "GBP",
    "value" => 1000
  ),
  "reference" => "YOUR_ORDER_NUMBER",
  "paymentMethod" => array(
    "type" => "directdebit_GB"
    "holderName" => 'S. Hopper',
    "bankAccountNumber" => '00000002',
    "bankLocationId" => '043001'
  ),
  "merchantAccount" => "YOUR_MERCHANT_ACCOUNT",
  "shopperEmail" => "s.hopper@gmail.com"
);
$result = $service->payments($params);
#Set your X-API-KEY with the API key from the Customer Area.
adyen = Adyen.Adyen()
adyen.client.xapikey = 'YOUR_X-API-KEY'

result = adyen.checkout.payments({
   'amount': {
      'value': 1000,
      'currency': 'GBP'
   },
   'reference': 'YOUR_ORDER_NUMBER',
   'paymentMethod': {
      'type': 'directdebit_GB',
      'holderName': 'S. Hopper',
      'bankAccountNumber':'00000002',
      'bankLocationId': '043001'
   },
   'merchantAccount': 'YOUR_MERCHANT_ACCOUNT',
   'shopperEmail':'s.hopper@gmail.com'
})
// Set your X-API-KEY with the API key from the Customer Area.
var client = new Client ("YOUR_X-API-KEY", Environment.Test);
var checkout = new Checkout(client);

var amount = new Model.Checkout.Amount("GBP", 1000);
var details = new Model.Checkout.DefaultPaymentMethodDetails{
  Type = "directdebit_GB",
  HolderName = "S. Hopper",
  BankAccountNumber = "00000002",
  BankLocationId = "043001"
};
var paymentRequest = new Adyen.Model.Checkout.PaymentRequest
{
  Reference = "YOUR_ORDER_NUMBER",
  Amount = amount,
  MerchantAccount = "YOUR_MERCHANT_ACCOUNT",
  PaymentMethod = details,
  shopperEmail = "s.hopper@gmail.com"
};

var paymentResponse = checkout.Payments(paymentsRequest);
// Set your X-API-KEY with the API key from the Customer Area.
const {Client, Config, CheckoutAPI} = require('@adyen/api-library');
const config = new Config();
// Set your X-API-KEY with the API key from the Customer Area.
config.apiKey = '[API_KEY]';
config.merchantAccount = '[YOUR_MERCHANT_ACCOUNT]';
const client = new Client({ config });
client.setEnvironment("TEST");
const checkout = new CheckoutAPI(client);
checkout.payments({
    amount: { currency: "GBP", value: 1000 },
    paymentMethod: {
        type: 'directdebit_GB',
        holderName: 'S. Hopper',
        bankAccountNumber: '00000002',
        bankLocationId'043001',
    },
    reference: "YOUR_ORDER_NUMBER",
    merchantAccount: config.merchantAccount,
    shopperEmail: "s.hopper@gmail.com"
}).then(res => res);

For a received payment, the /payments response contains the action.url that you need in the next step.

{
    "resultCode": "Received",
    "action": {
        "type": "voucher",
        "paymentMethodType": "directdebit_GB",
        "url": "PDF_MANDATE_URL"
    }
}

Present the payment result

Use the resultCode that you received in the /payments response to present the payment result to your shopper.
The resultCode values you can receive for BACS Direct Debit are:

resultCode Description Action to take
Received Adyen has received the payment and will submit the DDI and the payment for processing to BACS. You will receive a notification when the status of the payment has been updated.
There will be a settlement delay of four to six days. Inform the shopper that you've received their order, and are waiting for the payment to be completed.
Present the shopper with the URL in action.url from the response. The shopper may optionally download the mandate PDF document.
Authorised The payment was successful. Inform the shopper that the payment was successful.
Cancelled The shopper cancelled the payment. Ask the shopper whether they want to continue with the order, or ask them to select a different payment method.
Error There was an error when the payment was being processed. For more information, check the refusalReason field. Inform the shopper that there was an error processing their payment.
Refused The payment was refused. For more information, check the refusalReason field. Ask the shopper to try the payment again using a different payment method.

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.storePaymentMethodtrue.
  1. When you receive the notification that the payment was authorised, note the recurringDetailReference or the storedPaymentMethodId. 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 recurringDetailReference returned in the response when you created the token. This holds the token for the shopper received in the successful payment notification for the initial payment.
  • shopperReference: The same unique shopper ID you used to create the shopper token.
  • shopperInteraction: ContAuth.
{
   "merchantAccount":"YourMerchantAccount",
   "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/..."
}

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 notifications.

Chargebacks

The BACS scheme and the Direct Debit Guarantee give significant consumer rights to the shopper, such as:

  • An immediate money back guarantee if an error is made in the payment of a direct debit.
  • The right to cancel the DDI at any time.

Unpaid direct debits are booked as chargebacks. A chargeback can indicate that:

  • The DDI was changed or cancelled.
  • The shopper disputes the due date, amount, or frequency of the direct debit.
  • The shopper has not paid the direct debit.
  • There were insufficient funds in the shopper's bank account.
You cannot defend against BACS chargebacks. These will always result in the shopper receiving a refund.

For more information on the chargeback process, refer to Dispute management.

Chargeback notification

A notification for a chargeback has:

  • pspReference: Adyen's unique reference associated with the payment request.
  • eventCodeCHARGEBACK.
  • reason: Reason for the chargeback.
  • successtrue.

Here is an example of a notification for a chargeback due to insufficient funds in the shopper's bank account.

{
   "live":"false",
   "notificationItems":[
      {
         "NotificationRequestItem":{
            "additionalData":{
               "directdebit_GB.mandateId":"424544",
               "directdebit_GB.serviceUserNumber":"298288",
               "directdebit_GB.serviceUserName":"Adyen Payments",
               "directdebit_GB.sequenceType":"OneOff",
               "directdebit_GB.dateOfSignature":"2016-10-21"
            },
            "amount":{
               "currency":"GBP",
               "value":1000
            },
            "eventCode":"CHARGEBACK",
            "eventDate":"2016-10-21T11:34:15+02:00",
            "merchantAccountCode":"YourMerchantAccount",
            "merchantReference":"TMRef1234",
            "paymentMethod":"directdebit_GB",
            "pspReference":"9914770424540842",
            "reason":"Insufficient funds",             
            "success":"true"
         }
      }
   ]
}

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