Payment rails can now be configured per product

We're in the process of rolling out Direct Debits, and as part of this, payment rails can now be configured per product. For each bank account product, you now have a configuration that tells you which payment rails are enabled for that product and its related bank accounts.

What’s changed?

• Payment rails configured per product - until now, all Griffin accounts were enabled for every payment type we offer: Book Transfers, Faster Payments, Bacs Direct Credits and CHAPS. Now, each bank account product can be configured for specific rails

• Unsupported payments are rejected automatically - a payment received into an account that isn't set up for that payment type is rejected and returned to the scheme with a reason code, making it clear to the sender that the account isn't available to that payment scheme

Why we’ve added this

Direct Debits are a bit different. As a pull payment, it's possible for your customers to set up a Direct Debit on an account they shouldn't, such as a savings account. This new configuration prevents those unintended cases.

It also gives you and us more control over how your accounts can be used, and means we can roll out new payment types, like Direct Debits, when you're ready.

Will this affect existing integrations?

No, existing integrations are unchanged. All accounts remain enabled for the same payment rails as before, except Direct Debits.

If you want to enable Direct Debits for any of your products, or disable a payment rail, speak to your Customer Success manager or a member of our Connect team.

Thanks for reading!

Stay connected:

 Read our docs

 Follow us on LinkedIn