Understanding the Metadata API

The coverage tables on the previous pages show everything Tazapay supports. What your account can actually provision may be a subset - availability depends on your onboarding profile, industry vertical, and merchant country. The Metadata API answers this precisely. Call it before creating a Collection Account and it returns the list of capabilities - account type, currency, and payment method combinations - available specifically for your account. Anything restricted for your industry vertical or merchant country is already filtered out, so you can build your product against the real list instead of discovering restrictions at creation time.

Account type	Endpoint	Reference
Virtual Accounts	`GET /v3/metadata/collection_account/virtual_account`	Virtual Account Metadata
Stablecoin Wallets	`GET /v3/metadata/collection_account/wallet`	Wallet Metadata

Query Parameters

All parameters are optional - call with none to get every capability available to your account, or narrow the list down.

string

Filter capabilities by the country in which the account would be domiciled (ISO 3166 alpha-2, e.g. SG). Applies to virtual accounts.

array of string

Filter capabilities to those supporting the given currencies (ISO format, e.g. SGD).

string

The entity ID of a customer, to check availability for a specific onboarded entity.

boolean

Set to true to return capabilities for collecting on behalf of your customers, including any restrictions that apply (see on_behalf_of in the response below).

Response - Capabilities

The response contains a single capabilities array. Each entry describes one account configuration you can provision.

Virtual Accounts
Stablecoin Wallets

string

The payment method type this capability describes - e.g. local_bank_transfer_sgd, wire_transfer.

array of string

Currencies supported by this virtual account type.

object

Minimum and maximum limits per transaction.

Show transfer_limit

object

The minimum amount per incoming transaction - amount and ccy.

object

The maximum amount per incoming transaction - amount and ccy.

string

Currency in which the limits are specified.

object

Local rail details, present for local payment method types.

Show local.fund_transfer_networks

string

Name of the fund transfer network - e.g. FAST, SEPA, ACH.

object

Per-network transaction limits, in the same shape as the capability-level transfer_limit.

string

Additional details about the network, such as turnaround time and availability.

object

Whether - and under which conditions - this capability can be used to collect on behalf of your customers. This is where industry and country restrictions surface.

Show on_behalf_of

boolean

Whether collecting on behalf of customers is supported for this capability.

array of string

Industry verticals for which this capability is not available.

array of string

Conditions your customer must meet first - entity_approval_required or entity_submission_required.

array of string

Payers in these countries cannot send funds to this account type.

array of string

Customers in these countries cannot hold this account type.

string

How long the account takes to provision - instant, same_day, t_plus_1, t_plus_2, t_plus_3, or extended.

boolean

Whether an account of this type can be re-enabled after being disabled.

string

The stablecoin this capability describes - stablecoin_usdc or stablecoin_usdt.

array of string

Blockchains supported for this stablecoin - e.g. Ethereum, Tron, Solana, Base, Polygon Pos.

object

Minimum and maximum limits per transaction - minimum, maximum, and currency, in the same shape as the virtual account transfer_limit.

object

Whether - and under which conditions - this capability can be used to collect on behalf of your customers.

Show on_behalf_of

boolean

Whether collecting on behalf of customers is supported for this capability.

array of string

Industry verticals for which this capability is not available.

array of string

Conditions your customer must meet first - entity_approval_required or entity_submission_required.

array of string

Payers in these countries cannot send funds to this wallet type.

array of string

Customers in these countries cannot hold this wallet type.

string

How long the wallet takes to provision - instant, t_plus_1, t_plus_2, t_plus_3, or extended.

Putting It to Work

Call the Metadata API first

Before showing account options in your product or calling Create Collection Account, fetch the capabilities for your account.

Build against the returned list

Only offer the countries, currencies, and payment method types that come back - the list already reflects your account’s restrictions.

Check on_behalf_of before collecting for customers

If you provision accounts for your customers, check on_behalf_of.support and its restriction fields per capability, and handle additional_requirements before creating the account.

Capabilities can differ between sandbox and production, and between accounts - always query the environment and account you are integrating against.

Overview

Coverage

Managed Payments

Requesting Collection Accounts

Viewing Collection Accounts

Disabling Collection Accounts

Incoming Payments

Use Case Guides

Query Parameters

Response - Capabilities

Putting It to Work

​Query Parameters

​Response - Capabilities

​Putting It to Work

Query Parameters

Response - Capabilities

Putting It to Work