Overview

Sending money to the wrong account is costly for your business and your payees. Tazamatch lets you confirm that a bank account exists and that the account holder’s name matches your intended recipient, before a payout is ever initiated. By verifying payees upfront, you can reduce failed payouts, catch potential fraud early, and build trust with your recipients without adding friction to your payout flow. Verification is non-blocking, meaning your existing payout operations continue uninterrupted. Tazapay normalises verification results across corridors into a consistent response, so your integration stays simple regardless of where you’re paying.

The Verification Object

JSON

{
  "id": "pyv_xxxx",
  "object": "verification",
  "verification_status": "valid",
  "status_description": "",
  "beneficiary": "bnf_xxxx",
  "beneficiary_details": {
    "type": "individual",
    "email": "",
    "tax_id": "",
    "address": {
      "city": "Mumbai",
      "country": "IN",
      "line1": "123 Main Street",
      "line2": "",
      "postal_code": "400001",
      "state": "Maharashtra"
    },
    "phone": {
      "calling_code": "+91",
      "number": "9876543210"
    },
    "destination_details": {
      "type": "bank",
      "bank": {
        "account_number": "9876543210",
        "account_type": "savings",
        "bank_codes": {
          "ifsc_code": "HDFC0001234"
        },
        "bank_name": "HDFC Bank",
        "country": "IN",
        "currency": "INR"
      }
    }
  },
  "verified_information": {
    "name_match_details": {
      "type": "continuous",
      "value": 0.97,
      "summary": "strong_match",
      "translated_name": "",
      "corrected_name": ""
    },
    "account_exists": true,
    "beneficiary_type": "individual",
    "transaction_activity_details": null,
    "additional_information": null
  },
  "balance_transaction": {
    "holding_currency": "USD",
    "balance_impact": -10,
    "balance_transaction_id": "txn_xxxx"
  },
  "metadata": null,
  "created_at": "2026-04-07T10:00:00Z",
  "updated_at": "2026-04-07T10:00:05Z"
}

Field	Sub-fields	Type	Description
id		string	Unique ID of the verification object. Prefix `pyv_`
object		string	String representing the object’s type. It is `verification` here
verification_status		string	Outcome of the verification. One of `pending`, `valid`, `invalid`, `not_supported`, `failed`
status_description		string	Additional context on the verification status, when available
beneficiary		string	ID of the saved beneficiary that was verified (`bnf_xxxx`), if Mode A was used
beneficiary_details		json	Payee details that were verified, either resolved from the saved beneficiary or passed inline
	type	string	Type of beneficiary entity: `individual` or `business`
	email	string	Email address of the beneficiary
	tax_id	string	Tax identification number of the beneficiary
	address	json	Address of the beneficiary
	phone	json	Phone number of the beneficiary
	destination_details	json	Destination account details that were verified, including bank and account identifiers
verified_information		json	Results returned by the verification provider. `null` until the verification completes
	name_match_details	json	Details of the name-match check between the beneficiary’s name and the account holder’s name
	account_exists	boolean	Whether the destination account exists
	beneficiary_type	string	Beneficiary type as reported by the verification provider
	transaction_activity_details	json	Transaction activity details for the account, when supported by the corridor
	additional_information	string	Extra context returned by the verification provider, when available
balance_transaction		json	The balance transaction created for the verification fee
	holding_currency	string	Currency the verification fee was charged in
	balance_impact	integer	Amount deducted from your balance for this verification, in cents
	balance_transaction_id	string	ID of the balance transaction (`txn_xxxx`)
metadata		json	Key-value data attached to the verification, echoed back from the request
created_at		timestamp	Timestamp at which the verification was created
updated_at		timestamp	Timestamp at which the verification was last updated

Next Steps

Fetch Verification Metadata

Check coverage and required fields for a corridor

Create Verification

Submit a verification request

Verification Webhooks

Get notified when a verification completes

API Overview

Tazapay API

JavaScript SDK

Appendix

The Verification Object

Next Steps

Fetch Verification Metadata

Create Verification

Verification Webhooks

​The Verification Object

​Next Steps

Fetch Verification Metadata

Create Verification

Verification Webhooks

The Verification Object

Next Steps