Workflow-ready
Call the check when a supplier submits or changes settlement details.
BANK DETAIL CONTROL API
Check an IBAN before payment data moves forward.
Bring IBAN checks into vendor onboarding and bank-detail change workflows, then route the result through the approvals your organisation requires.
Built for server-side integration · Structured outcomes · Human-controlled decisions
OVERVIEW
A verification signal that fits the process.
Use the API result inside the workflow, evidence rules and approval responsibilities your organisation has defined.
Structured outcome
Return a consistent verification result for rules, reviewer queues and audit context.
Controlled change
Keep the check separate from the human approvals required to alter payment instructions.
INPUTS
Start with the evidence you already collect.
1
Submitted IBAN
Send the IBAN captured through your authorised supplier or finance workflow.
2
Business context
Associate the check with the relevant supplier, request and reviewer context in your system.
3
Change event
Use a new or amended bank-detail event to trigger the check and the required approval path.
INTEGRATION NOTES
Designed for a controlled backend workflow.
- Designed for backend integration into onboarding and bank-detail change journeys.
- Results can be mapped to validation, review and exception states in the consuming application.
- Integration scope and available response attributes are confirmed during API onboarding.
An IBAN verification response is not a payment instruction, proof that the requester is authorised, or a substitute for independent bank-detail change controls.
WORKFLOW
From API call to documented decision.
Capture securely
Collect bank details through an authorised channel and keep credentials and sensitive data out of client-side logs.
Run the check
Submit the IBAN and record the structured outcome against the relevant vendor event.
Approve independently
Apply maker-checker, callback or other organisation-approved controls before changing payment instructions.
RESPONSIBLE AUTOMATION
Automate the check.
Keep people accountable.
Vendoreye helps place verification evidence and exceptions in the right workflow. Your authorised team remains responsible for policy, escalation and approval.
Discuss your verification flow ↗Recommended decision states
- Check completed and evidence available
- Review required for a mismatch or possible match
- Evidence unavailable or insufficient
- Technical error requiring retry or support
Do not convert an unavailable check or technical error into a pass.
FREQUENTLY ASKED QUESTIONS
Questions teams ask before integration.
Can this be used for bank-detail changes?
Yes. It can provide a verification signal inside the change workflow, while your existing authorisation and fraud controls remain in force.
Does a successful check approve payment?
No. Payment approval and payment execution remain separate controlled actions.
Should the API key be used in the browser?
No. Keep verification credentials in an approved backend or secure integration layer.
RELATED VERIFICATION APIs
Connect the checks your policy requires.
Use each result as evidence within a risk-based onboarding, renewal or change-control process.
VERIFICATION, CONNECTED
Bring the API into your
vendor workflow.
Tell us which checks, systems and approval stages you need to connect.
Request API access ↗