Tazamatch is coming soon. The APIs listed here are for reference only and are not yet available in production or sandbox.
Get Verification Metadata
GET /v3/verification/payee/metadata
Use this endpoint before initiating a verification to check whether payee verification is supported for a given corridor, and to retrieve the exact fields required to run a verification.
Authorizations
Basic authentication header of the form Basic <encoded-value>, where <encoded-value> is the base64-encoded string username:password.
Query Parameters
Destination country (ISO 3166-1 alpha-2, e.g. IN, US, GB).
Currency of the destination account (ISO 4217, e.g. INR, USD).
Type of payout rail. Allowed: local, swift, local_payment_network.
local_payment_network.type
Type of local payment network. Required if type = local_payment_network (e.g. upi_inr, pix_brl, promptpay_thb).
Response
List of supported corridors matching the query, each with required fields and verification capabilities. Destination country (ISO 3166-1 alpha-2).
Currency of the destination account (ISO 4217).
Type of payout destination supported for verification. Allowed: bank, local_payment_network.
local_payment_network_type
Type of local payment network. Populated when destination_type = local_payment_network (e.g. upi_inr, pix_brl). Empty string otherwise.
Estimated coverage percentage for this corridor.
List of accepted bank name values for this corridor, where applicable. Empty array if not restricted.
Bank fields required for verification (e.g. account_number, iban, country, currency, account_type). Applicable when destination_type = bank.
Bank routing codes required for verification (e.g. ifsc_code, swift_code, aba_code, sort_code, branch_code, bsb_code, bank_code, cnaps). Applicable when destination_type = bank.
required_beneficiary_fields
Beneficiary fields required to complete the verification (e.g. name, type, phone, email, address, tax_id).
supported_verification_capabilities
Verification capabilities supported for this corridor. Show supported_verification_capabilities
Whether tazamatch can confirm if the account exists.
Whether tazamatch supports name matching against the account holder.
Whether a normalised confidence score (0.0 to 1.0) is returned for the name match.
Whether the match is classified as strong_match, partial_match, or no_match.
Whether a corrected or suggested name is returned when a close but imperfect match is found.
Whether a translation of the matched name in local script is returned.
Whether recent transaction activity on the account can be confirmed.