Key Concepts

Tazamatch is coming soon. The APIs listed here are for reference only and are not yet available in production or sandbox.

When you submit a verification request, Tazamatch creates a verification object and returns a response as a consistent set of states and match types.

Verification states

State	Type	Meaning
pending	Intermediate	Verification request is in progress
valid	Terminal	Account found; a name match score is returned
invalid	Terminal	Account not found for the details provided
not_supported	Terminal	Corridor is not covered by Tazamatch

pending is a transient state.

State machine diagram

Match types

Returned only when verification_status = valid.

Match type	Meaning
strong_match	Name matches exactly or near-exactly (minor casing or spacing differences only)
partial_match	Name partially matches, e.g. missing middle name, shortened version, or nickname
no_match	Account exists but the name provided does not match the account holder on record

valid with no_match does not mean the payee is wrong. It means the account is active but the name differs from what is registered. Review carefully before proceeding.

What Tazamatch returns

A completed verification returns a pyv_xxxx object containing:

Field	Description
verification_status	Terminal state of the verification
name_match.summary	Match type (strong_match, partial_match, no_match)
name_match_details	Additional match detail where available
verified_details	Account holder name returned in corridors, where available

Not all fields are returned for every corridor. See Coverage for details by corridor.

Coverage

Supported corridors and capabilities

API

Step-by-step integration guide

Flow

Coverage

⌘I

Overview

Coverage

How to Use

Verification states

State machine diagram

Match types

What Tazamatch returns

Coverage

API

​Verification states

​State machine diagram

​Match types

​What Tazamatch returns

Coverage

API

Verification states

State machine diagram

Match types

What Tazamatch returns