Verification
Identity, account, and business verification services for confirming who you're dealing with before you move money.
Verification lets you confirm the account holder behind an IBAN before you move money. In the UAE this is Beneficiary Verification, a confirm-payee check that reduces misdirected payments and authorised-push-payment fraud.
In this guide
- What Beneficiary Verification confirms
- When to run it in a payment flow
- The match / no-match / error outcome
- How it fits alongside payment initiation
Availability
Beneficiary Verification is live in the UAE. See Coverage for what's enabled in each market.
What it confirms
Beneficiary Verification resolves the registered account holder for an IBAN and, when you supply the name you expect, tells you whether it matches. Use it as a confirm-payee step immediately before initiating a payment, or to validate account ownership during onboarding.
Where it fits
Run the check first, decide, then pay:
The call is server-to-server and Bearer-authenticated, and returns a structured MATCH / NO_MATCH / ERROR result you can branch on programmatically.
Key takeaways
- Beneficiary Verification confirms the bank's registered owner for an IBAN before you pay.
- Best run as a confirm-payee step right before initiating a payment.
- Server-to-server and Bearer-authenticated; call it from your backend, not a browser or mobile client.