Blueprint
Bank Details Collection
Verified bank details, ready before the money is
Verified before you pay
Collect bank details from customers before you need to pay them, and know they're right. Customers connect their account through Open Banking or upload a statement, and Volume checks the name on the account matches your record before storing the details securely, ready for payment.
1
Request
Customers are asked for their bank details through targeted campaigns, at the right point in their journey, with reminders until they respond. They provide them in the portal.
2
Verify
Details from Open Banking are checked against your record automatically. Uploaded statements go through plausibility checks. Either way, a Confirmation of Payee check confirms the account name before anything is accepted.
3
Store
Verified details are encrypted, masked in logs and held against the customer, ready for payment, with role-based permissions on who can see or change them. Anything that fails a check goes to a Triage review, where your team accepts or rejects it.
4
Pay
When a payment is due, the details are played back to the customer to confirm or update, then passed on for payment.
A working version of every stage
Every bank details process asks the customer, verifies what they provide, stores it securely and uses it when it's time to pay. The Blueprint gives you a working version of each stage, linked by Workflows. You decide which checks and providers it uses.
Linked into one process
We provide the tools. You decide how they fit together, and Workflows link them into one process.
Add the steps you need
Need another step? Add a second check for high-value payments, a call-back for unmatched names, or a refresh if details are more than a set age. The process is yours to shape, and you can change it later without a development project.
What you can do
We provide the tools. You build the process
Every tool below already works with the others on one platform. Pick the ones your process needs, and Workflows link them into one process, with every check recorded against the customer
Connect with Open Banking
Customers connect and authorise their bank account from your portal in a few taps. Volume confirms the account name matches your record and stores the details, with nothing typed by hand.
Or upload a bank statement
Customers who'd rather not use Open Banking can upload a statement instead. Volume checks it's plausible: a recent date, a recognised layout, the right name, and a personal current account rather than a business one.
Name checked with Confirmation of Payee
Before details are accepted, a Confirmation of Payee check confirms the name on the account matches the customer on your record.
Exceptions reviewed by your team
If a check fails, such as a name mismatch, the details go into a Triage review. A dashboard surfaces every exception, and your team accepts or rejects the name returned before anything is stored.
Ask ahead of time
Run configurable campaigns that ask customers for their bank details before payments are due, combining email, SMS and portal messages on any schedule, with reminders until they respond.
Held securely, ready to use
Bank details are encrypted at field level and masked in logs and the audit trail. Role-based permissions control who can view, edit or delete them.
Confirmed at the right moment
Stored details are played back to the customer when they accept an offer or a payment is due, so they can confirm them or update them in their portal.
Your providers or ours
Use the Open Banking, statement and Confirmation of Payee providers already connected through Integrations, or plug in the third-party services you already use.
See it in action
Collecting bank details ahead of PCP settlements
Here's how a claims management firm collects and verifies claimants' bank details on Volume before their settlements arrive. Every step is automated by Workflows, using the tools and integrations shown
1
Request
Campaign launched
Claimants whose settlements are on the way are asked to add their bank details in their portal. Communication campaigns are fully configurable, so you can combine email, SMS and portal messages in any order and on any schedule.
2
Request
Reminders sent
Claimants who haven't responded are reminded automatically until their details are on file.
3
Request
Claimant chooses how
In the portal, the claimant chooses to connect their account through Open Banking or upload a bank statement.
4
Verify
Open Banking connection
The claimant connects and authorises their account. Volume confirms the account name matches the claimant on record.
5
Verify
Or statement checked
If the claimant uploads a statement instead, Volume checks the statement date, layout and name, and that it's a personal current account rather than a business one.
6
Verify
Confirmation of Payee
A Confirmation of Payee check confirms the name on the account matches the claimant.
7
Verify
Mismatches reviewed
If the name doesn't match, the details go into a Triage review. The exception appears on the team's dashboard, and a reviewer accepts or rejects the name returned.
8
Store
Details held securely
The verified details are encrypted and stored against the claimant, ready for payment.
9
Pay
Confirmed at offer acceptance
When the claimant accepts their offer, their bank details are shown back to them to confirm, or update if anything has changed.
10
Pay
Ready for payment
Once the settlement is reconciled, the confirmed details are used to pay the claimant.
FAQ
Common questions
How does Open Banking work here?
The customer connects and authorises their bank account from your portal. Volume receives the account details directly from their bank, checks the account name against your record and stores them, so nothing is typed in by hand.
What if a customer doesn't want to use Open Banking?
They can upload a bank statement instead. Volume runs plausibility checks on it and a Confirmation of Payee check on the account details.
What checks are run on a bank statement?
That it's recent, that its layout matches a genuine statement from that bank, that the name matches your record, and that it's a personal current account rather than a business account. You can add or adjust checks through configuration.
What is Confirmation of Payee?
A UK service that checks whether the name on a bank account matches the name you expect, before any money is sent to it.
What happens if the name doesn't match?
The details aren't accepted automatically. They go into a Triage review, and a dashboard surfaces every exception. Your team sees the name returned alongside your record and chooses to accept or reject it.
Which providers do you use?
You can use the Open Banking, statement and Confirmation of Payee providers already connected through Integrations, or plug in the third-party services you already have.
Can customers update their details?
Yes. Details are played back when a payment is due, such as when an offer is accepted, and customers can update them in their portal at any time.
How are bank details protected?
Data is hosted in the UK, held in your own encrypted database and encrypted at field level. Role-based access control restricts who can view, edit or delete bank details, and sensitive values are masked in logs and the audit trail. Volume holds Cyber Essentials and Cyber Essentials Plus certification and is committed to ISO 9001 & 27001.
How long does it take to set up?
Because you start from a working Blueprint rather than a blank page, most bank details processes go live in weeks, not months. We'll agree a timeline with you after discovery.
Proven in practice
Running for real customers
Case Study – Claims Management
Onboarding 100,000 claimants in six months
My Car Loan Claims asks claimants for their bank details ahead of settlement. Each account is verified through Open Banking or a statement and Confirmation of Payee before it's stored.
Read the Case StudyPrevious
