Simulating Account Holder Verification in Sandbox

The sandbox environment for Account Holder Verification (AHV) allows you to test your integration before going live, including different match levels, name variations, and fallback conditions — without involving any real accounts or providers.

This simulator helps you verify how your system handles name checks for both personal and business accounts, using predefined test data and structured responses.

Supported Features

In the sandbox, you can simulate:

Exact name matches
Close matches (e.g. spelling differences or mismatched account types)
No matches (e.g. incorrect names, invalid accounts, opt-outs)
Fallback behavior for unknown (non-predefined) inputs

All responses follow the same API format as in production — enabling accurate and efficient testing.

How to Simulate Specific Match Scenarios

To trigger a specific match result, submit one of the predefined input combinations (e.g. sort code, account number, name).
The sandbox will respond with the corresponding matchLevel, reasonCode, and explanation.

Predefined Test Cases

Test Case	FirstName	LastName	CompanyName	Country	BranchCode	AccountNumber	MatchLevel	AccountHolder	ReasonCode	ReasonId	Description	DetailedDescription
Match - Personal Account	Samantha	Smythe		GB	999996	00000001	Match
Match - Business Account			Bridgford Gardening	GB	999996	00000011	Match
Close Match - Wrong Name	Sam	Smythe		GB	999996	00000001	Close Match	MISS SAMANTHA SMYTHE	MBAM	2	There may be a match on the Account Name	The CoP Responder has performed the matching and it is a close match
No Match - Wrong Type P2B			Samantha Smythe	GB	999996	00000001	No Match	MISS SAMANTHA SMYTHE	PANM	4	Personal account, name matches	The CoP Requester indicated a business account, but it is actually a personal account and the name matches
No Match - Wrong Type B2P	Bridgford	Gardening		GB	999996	00000011	No Match	BRIDGFORD GARDENING	BANM	3	Business account, name matches	The CoP Requester indicated a personal account, but it is actually a business account and the name matches
No Match - Wrong Name	David	Smythe		GB	999996	00000001	No Match		ANNM	1	Account Name does Not Match	The CoP Responder has performed the matching and confirms it is not a match
No Match - Invalid Account	Samantha	Smythe		GB	999996	98989898	No Match		AC01	7	Incorrect Account Number	Account does not exist in the CoP Responder's books
No Match Opted Out			Johnson Logistics	GB	999996	00000048	No Match		OPTO	10	Opted out of CoP Scheme	Payee has been opted out of the CoP service by the CoP Responder
No Match Account Not Supp.	Not	Supported		GB	999996	00000062	No Match		ACNS	9	Account type Not Supported for CoP	Account not supported for CoP by the CoP Responder
Catch-All – Any other input	any	any	any	GB	any	any	No Match		ANNM	1	Account Name does Not Match	Returned when input doesn't match predefined sandbox cases

Catch-All Fallback for Unknown Inputs

If you test with input values not listed above, the sandbox will respond with:

MatchLevel: No Match
ReasonCode: ANNM
Description: Account Name does Not Match
DetailedDescription: The CoP Responder has performed the matching and confirms it is not a match

Notes

The sandbox is stateless and returns predefined responses only
No real data is accessed or verified
IBAN-based test cases will be introduced in a future update once provider details are confirmed