Simulating Verifications on Test Environment (Sandbox)

Tazamatch is available in sandbox by default. To test different verification scenarios, pass the account number / IBAN values shown below to POST /v3/verify/payee (with any name - name does not drive the outcome - and the BIC / sort code shown where applicable).

Country and currency have no effect on sandbox behaviour; only the account number / IBAN drives the response.

Match outcomes

For the corresponding account number / IBAN, the outcomes would be same as below.

Use it to test	Account / IBAN	verification_status	match_outcome	match_score	beneficiary_type	account_exists
Strong match - IBAN (IE)	`IE83AIBK93115200000001`	valid	strong_match	1.00	individual	true
Strong match - Account+BIC (IN)	`987654321001`	valid	strong_match	1.00	individual	true
Strong match - Account+BIC (NG)	`1234567890`	valid	strong_match	1.00	individual	true
Strong match - Account+Sort Code (GB)	`12345678`	valid	strong_match	1.00	individual	true
Strong match - Account+Routing (US)	`781245633`	valid	strong_match	1.00	individual	true
Strong match - Account only (MX)	`999000000000000505`	valid	strong_match	1.00	individual	true
Strong match - Account only (AR)	`0170032450000643500000`	valid	strong_match	1.00	individual	true
Strong match - Registration ID (CN, individual)	`321872160000`	valid	strong_match	1.00	individual	true
Strong match - Registration ID (CN, business)	`321872160001`	valid	strong_match	1.00	business	true
Strong match - Registration ID (BR, business)	`BR1199950505000010000000888C1`	valid	strong_match	1.00	business	true
Strong match - Registration ID (SA, business)	`SA1510100011100000461311`	valid	strong_match	1.00	business	true
Strong match - IBAN (DE)	`DE67370400440532010001`	valid	strong_match	1.00	individual	true
Strong match - IBAN (NL)	`NL80ABNA0513165301`	valid	strong_match	1.00	individual	true
Strong match - IBAN (ES)	`ES0721000418450200051001`	valid	strong_match	1.00	individual	true
Strong match - Korean corridor (translated name)	`11112222321`	valid	strong_match	0.95	individual	true
Partial match - IBAN (IE)	`IE56AIBK93115200000002`	valid	partial_match	0.50	individual	true
Partial match - Account+Sort Code (GB)	`23456789`	valid	partial_match	0.50	individual	true
Partial match - Account+Routing (US)	`781245634`	valid	partial_match	0.50	individual	true
Partial match - Registration ID (CN)	`321872160003`	valid	partial_match	0.50	individual	true
Partial match - Registration ID (CN, alt)	`321872160004`	valid	partial_match	0.50	individual	true
No Match - IBAN (IE)	`IE29AIBK93115200000003`	invalid	no_match	0.00	individual	true
No Match - Account+Routing (US)	`781245636`	invalid	no_match	0.00	individual	true
No Match - Account+Sort Code (GB)	`34567890`	invalid	no_match	0.00	individual	true

account_exists variants

Use it to test	Account / IBAN	verification_status	match_outcome	match_score	beneficiary_type	account_exists
Strong match, `account_exists = true`	`987654321001`	valid	strong_match	1.00	individual	true
Strong match, `account_exists = false`	`987654321006`	valid	strong_match	1.00	individual	false
Strong match, `account_exists` not returned (null)	`987654321007`	valid	strong_match	1.00	individual	null
Account closed	`IE45AIBK93115200000006`	invalid	n/a	n/a	n/a	false

beneficiary_type not returned

Use it to test	Account / IBAN	verification_status	match_outcome	match_score	beneficiary_type	account_exists
Strong match, `beneficiary_type = null` (DE)	`DE67370400440532010007`	valid	strong_match	1.00	null	true
Strong match, `beneficiary_type = null` (IN)	`987654321008`	valid	strong_match	1.00	null	true

matched_name_details - corrected & translated name

Use it to test	Account / IBAN	match_outcome	match_score	corrected_name	translated_name
Corrected name returned (partial match)	`123456789007`	partial_match	0.80	SACHIN TENDULKAR	n/a
Translated name returned (Korean corridor)	`11112222321`	strong_match	0.95	n/a	Song Hye-kyo
Corrected name returned (GB, strong match)	`12345678`	strong_match	1.00	HARRY SNAPE POTTER	n/a

corrected_name is the suggested correct name; surface it to the payer for confirmation. translated_name is relevant for cross-script corridors (Korean, Chinese, Arabic).

additional_information - transaction activity

Use it to test	Account / IBAN	match_outcome	match_score	transaction_activity	transaction_activity_started_at
Transaction activity = true	`987654321009`	strong_match	1.00	true	2026-01-01
Transaction activity = false	`1234567891`	strong_match	1.00	false	2026-01-01
Transaction activity not returned (null)	`DE67370400440532010008`	strong_match	1.00	null	null

transaction_activity = false does not mean the account is inactive; it means no recent transaction activity was detected in the observed time period. A “returned false” case is only distinguishable from “not returned” when transaction_activity_started_at also accompanies it - the response omits the transaction_activity_details block entirely unless one of the two fields is present.

Combined scenarios

Multiple verified_information fields returned together in a single response. All rows have verification_status = valid.

Use it to test	Account / IBAN	match_outcome	match_score	beneficiary_type	account_exists	corrected_name	transaction_activity
Strong match + transaction_activity	`IE83AIBK93115200000009`	strong_match	1.00	individual	true	n/a	true
Business strong match + transaction_activity	`NL80ABNA0513165309`	strong_match	1.00	business	true	n/a	true
Strong match + transaction_activity (alt)	`987654321010`	strong_match	1.00	individual	true	n/a	true
Business strong match + corrected_name + transaction_activity	`321872160002`	strong_match	1.00	business	true	JSR APPLE AND ORANGE COMPANY LTD	true
Partial match + corrected_name + transaction_activity=false	`123456789008`	partial_match	0.80	individual	true	SACHIN RAMESH TENDULKAR	false
No match + transaction_activity=false	`IE29AIBK93115200000004`	no_match	0.00	individual	true	n/a	false
account_exists & beneficiary_type not returned	`DE67370400440532010009`	strong_match	1.00	null	null	n/a	n/a

Error scenarios

Use it to test	Account / IBAN	verification_status	Description	account_exists
Creditor account not found (IE)	`IE72AIBK93115200000005`	invalid	CreditorAccountNotFound	false
Creditor account not found (ID)	`1234567890343`	invalid	CreditorAccountNotFound	false
Creditor account not found (MX)	`999000000000000123`	invalid	CreditorAccountNotFound	false
Creditor agent invalid - sort code invalid (GB)	`11223344`	invalid	CreditorAgentInvalid	n/a
Creditor agent invalid - BIC invalid (IN)	`987654321014`	invalid	CreditorAgentInvalid	n/a
Creditor agent invalid - BIC unrecognised (BD)	`111112222202`	invalid	CreditorAgentInvalid	n/a
Creditor agent invalid - generic	`987654321011`	invalid	CreditorAgentInvalid	n/a
Creditor account flagged (IN)	`987654321003`	invalid	CreditorAccountFlagged	false
Creditor name match incomplete (IN)	`987654321005`	valid	CreditorNameMatchIncomplete	true
Creditor account detail unable to validate (ID)	`987654321012`	not_supported	We were unable to validate the payee for this corridor.	n/a
Creditor account detail unable to validate (DE)	`DE29370400440532010006`	not_supported	We were unable to validate the payee for this corridor.	n/a
Invalid registration number (IT)	`IT129499821`	invalid	InvalidRegistrationNumber	n/a
Account logic test successful (IE)	`IE92BOFI90001710027952`	valid	AccountLogicTestSuccessful	true
Account logic test failure (NL)	`NL84ABNA042560090`	invalid	AccountLogicTestFailure	false
Account closed (IE)	`IE45AIBK93115200000006`	invalid	account_closed	false
Currency mismatch	`0170032450000643500001`	not_supported	currency_mismatch	n/a
Corrected currency	`AE350030012285049920002`	not_supported	corrected_currency	n/a
Unrecognised response code	`987654321099`	failed	UnrecognisedResponseCode	n/a
Unknown / unconfigured account	(any unrecognised value)	not_supported	sandbox_account_not_configured	n/a

CreditorAccountFlagged means the account exists but has been flagged (e.g. suspected fraud/compliance hold) - block the payment; do not expose the raw flag reason to the payer. Only an unrecognised response code returns verification_status = failed; invalid and not_supported are the outcomes for every documented error code above.

HTTP error responses

These two cases simulate a technical failure during verification: an HTTP error is returned, no verification record is created, and no fee is charged - unlike every other case on this page, which returns HTTP 200 with a persisted record.

Use it to test	Account / IBAN	HTTP response	Notes
Blank / malformed account number	(blank)	500 Internal Server Error	We were unable to securely process your verification request due to an internal error. Please try again, and contact support@tazapay.com if the problem persists.
Timeout / unavailable	`404404404`	503 Service Unavailable	Payee verification is temporarily unavailable. Please try again shortly.

API Overview

Tazapay API

JavaScript SDK

Appendix

Simulating Verifications on Test Environment (Sandbox)

Match outcomes

account_exists variants

beneficiary_type not returned

matched_name_details - corrected & translated name

additional_information - transaction activity

Combined scenarios

Error scenarios

HTTP error responses

​Match outcomes

​account_exists variants

​beneficiary_type not returned

​matched_name_details - corrected & translated name

​additional_information - transaction activity

​Combined scenarios

​Error scenarios

​HTTP error responses

Match outcomes

account_exists variants

beneficiary_type not returned

matched_name_details - corrected & translated name

additional_information - transaction activity

Combined scenarios

Error scenarios

HTTP error responses