Changes to debtor and creditor identification fields

We're updating how we represent debtor and creditor information in payment responses to better support overseas payments. Below is a summary of the changes.

Please let us know if your integration relies on the account-number or bank-id fields being present.

Account identification fields

• account-number will become optional

• iban and bban will be introduced as optional fields so we can provide these when they’re available

• other-account-identification will be introduced as an optional field, serving as a catch-all for account number schemes we're currently unable to process

• account-number-code will be deprecated

Bank identification fields

• bank-id will become optional

• sort-code will be introduced as an optional field for UK domestic accounts

• bicwill be introduced as an optional field

• other-institution-identification will be introduced as an optiona field for schemes we're currently unable to process

• bank-id-code will be deprecated

We'll continue populating account-number and bank-id for all domestic payments, but you'll need to handle missing values on the debtor record to receive payments from overseas.

Why are we making this change?

We want to be able to receive and automatically process overseas payments on your behalf. By definition, the debtor (sender) on such payments is from a non-UK bank account, so doesn't have a UK account-number.

Those of you with a keen eye will have noticed that our current API doesn’t support this in the right way. We currently pair account-number with the account-number-code field set to bban, but UK account-numbers are not bbans.

When is this happening?

We’ll make the account-number and bank-id fields optional (while continuing to populate them) in the next few weeks. We're hoping to support overseas payments in the next couple of months. We’ll keep you posted.

Questions?

We're here to help. Just reach out at support@griffin.com or get in touch with your Customer Success manager.

Thanks for reading!

 Read our docs

 Join our Slack community

 Follow us on LinkedIn