Product Info

Product Info
x402 explained: the payment standard for AI agents

Software is becoming a paying customer

‍

AI agents now do real work. They research markets, write and test code, check freight rates and pull data from dozens of APIs to finish a single task. Sooner or later, an agent reaches a service that charges for access.

That is where things slow down. Most online payment flows assume a person is present to create an account, enter card details, store an API key or approve a monthly bill. Those flows work well for people. An agent acting on its own, mid-task, needs a way to pay in the same moment it asks for the data.

x402 is an open protocol built for exactly that. This piece explains what x402 is, how a payment moves from agent to API, where it is already useful, what a business needs to accept payments from software, and how Tazapay is making that easier.

‍

What x402 is

‍

x402 is an open standard that lets a client pay for a web resource inside the same HTTP request it uses to ask for it. The client can be an AI agent, a script or an app. The resource can be an API response, a dataset, a file or a unit of compute.

The name comes from HTTP status code 402. Every web request returns a status code: 200 means the request worked, 404 means the page was not found. Code 402, Payment Required, was reserved in the early days of the web for a payment system that never arrived, so it went largely unused for decades.

x402 gives that code a defined format. When a server returns 402, the response carries machine-readable payment terms: the amount, the accepted token, the network, the receiving address and a time limit. A server can list several options, and the client picks one it can pay. The client sends its payment in a request header, and the server confirms it in a response header, so no new endpoint, redirect or checkout page is needed, as described in Coinbase's x402 launch announcement.

Payments today run mainly on stablecoins such as USDC. The standard is designed to work across blockchain networks and to extend to other payment methods over time.

Coinbase introduced x402 in May 2025 as an open protocol. In July 2026, the Linux Foundation launched the x402 Foundation to govern it, with Coinbase contributing the protocol and 40 member organisations signing on, including Visa, Mastercard, Stripe, Google, AWS and Cloudflare. That matters for businesses evaluating it: x402 is now a vendor-neutral standard, not one company's product.

‍

How an x402 payment works

‍

Three parties take part in every x402 payment: the agent that wants the resource, the API server that sells it, and a facilitator that checks and settles the payment. Here is the sequence for an agent that needs a freight rate from a paid logistics API.

‍

The agent gets its data before settlement finishes
Step
Between
What happens
1
Agent to API server
The agent requests the resource with a normal HTTP call.
2
API server to agent
The server replies 402 Payment Required with the payment terms.
3
Agent
The agent's wallet signs a payment for the exact amount. No funds move yet.
4
Agent to API server
The agent repeats the request with the signed payment in a header.
5
API server to facilitator
The server asks the facilitator to verify the payment.
6
Facilitator to API server
The facilitator confirms it is valid, in milliseconds.
7
API server to agent
The server returns the data plus a payment receipt.
8
Facilitator to blockchain
The payment settles on chain in the background, after the response.

Source: Coinbase Developer Platform, x402 Foundation

‍

A little more detail on the key steps:

  • The signed payment (step 3). The agent signs an authorisation that names the amount, the recipient, a validity window and a one-time number called a nonce. It uses a standard signing format (EIP-712 on EVM-compatible networks). Nothing is transferred at this point; it is a verifiable promise to pay.
  • The retry (step 4). The signed payload travels in a request header (X-PAYMENT in the launch version of the spec), so the agent calls the same endpoint again rather than a separate payment page.
  • The receipt (step 7). The server's response carries a header confirming the payment, so the agent has proof of what it paid for.

‍

For the agent, paying becomes one extra round trip, not a separate checkout process. For the API provider, every request can be priced and paid individually, which suits pay per call models better than prepaid credits or monthly plans.

‍

Why it can keep up with agents

‍

An agent might call dozens of paid endpoints to finish one task. If every call had to wait for a payment to fully settle on a blockchain, the agent would spend more time waiting than working. x402 avoids this by separating two jobs that are usually bundled together: checking the payment and settling it.

‍

Verification, inside the request
Signature is genuine
Amount covers the price
Token and network match
Nonce never used before
Still inside its validity window
Takes milliseconds
Settlement, in the background
Transaction submitted on chain
Network fee paid
Block confirmations awaited
Failed submissions recovered
Payment recorded as final
Seconds to minutes, depending on the network
The API responds as soon as the left column passes. The right column happens after the response.

Source: Coinbase Developer Platform, x402 Foundation

‍

Verification happens inside the request. The facilitator checks the signed payment against the server's terms. Every check works on the signed message itself, so none of them waits on the network. The nonce check is what stops replay: once a payment has been used, the same proof cannot pay for a second request.

Settlement follows, in the background. Once the payment passes, the server releases the data straight away, while the facilitator submits the transaction, pays the network fee and waits for confirmation. If a submission fails, recovering it is the facilitator's job, not the API's. Whoever runs the facilitator takes on the small risk between approval and final confirmation.

This split is what makes small, frequent payments practical. The cost of each payment comes down to the network fee, which is low on the networks x402 typically runs on. A request can be priced at a few cents, or less, and still make commercial sense.

‍

Where x402 fits

‍

The common thread is simple: one piece of software needs to pay another, at the moment it uses the service. The businesses best placed to sell to agents already price by usage, and their fastest-growing callers are automated.

  • Data API providers. Financial, legal, scientific, weather and logistics data sold per query. A research agent hits a premium endpoint, pays for that one lookup and moves on.
  • AI infrastructure providers. Compute, inference, embeddings, vector search and storage. In a multi-agent pipeline, each step can pay the next service it calls, without a shared billing account behind every agent.
  • Developer tool vendors. Code analysis, testing and deployment services. A coding agent in a CI pipeline can buy a single scan or test run per use.
  • Digital content platforms. Licensed images, video, audio and datasets. An AI content agent pays the rights holder per asset as it fetches each one.
  • B2B marketplaces and procurement platforms. Freight quotes, customs data, compliance checks and service orders. An agent placing an order gets a payment rail that does not stop for a human to approve every transaction.

x402 does not replace cards, bank transfers or invoicing. Those stay the right tools for people and for most business-to-business payments. It adds a rail for a new kind of buyer, one that needs to pay in the middle of a request rather than at a checkout page.

‍

What a business needs to accept agent payments

‍

Adding x402 to an endpoint takes little code, since open-source middleware handles the 402 response itself. The harder part is everything behind the payment. A business that wants to sell to agents at scale needs answers to five questions.

  • Where do the funds land? Stablecoin payments need a wallet or custody arrangement that is secure, monitored and owned by the business.
  • Who verifies and settles? Someone has to run the facilitator role described above, including paying network fees and recovering the rare transaction that fails.
  • How does the money reach the books? Thousands of small payments need to be matched to requests, reconciled and, for most businesses, converted into the currency they report in.
  • Is it compliant? Receiving stablecoins brings licensing, KYB and anti-money laundering obligations that vary by market.
  • Does it fit existing payment operations? Agent revenue should sit alongside card, bank transfer and invoice revenue, not in a separate system.

‍

The protocol is still young, and its governance only became vendor-neutral in July 2026. That makes now a good time for API and data businesses to plan for agent payments, before their own customers start asking for it.

‍

How Tazapay enables x402 payments

‍

In simple terms: Tazapay acts as an x402 facilitator for its merchants. API and data businesses can charge AI agents per request and keep the money in stablecoins or pay it out in local currency, without building any blockchain setup themselves. The merchant keeps running its own API, and Tazapay never sees that traffic, only the payment details it needs to check and settle each payment.

‍

Getting started takes three steps:

  • Add the standard middleware. The merchant adds the open-source x402 middleware to its API and points it at the Tazapay facilitator (service.tazapay.com/v3/x402) with its existing Tazapay API key. There is no separate blockchain account, third-party SDK or reconciliation code to set up.
  • Set a price per route. The merchant decides what each endpoint costs, either a fixed price per call or usage-based pricing up to a maximum the agent authorises. Agents pay in USDC on Base or Polygon PoS.
  • Get paid as normal Collects. Funds land in the merchant's Tazapay USDC wallet and appear as normal Collects, then flow into balance, FX and payouts like any other incoming payment.

‍

Who
What they do
AI agent
Calls the merchant's API and pays per request in USDC
Merchant's API, with the standard x402 middleware
Sets the price for each route and serves the request once the payment checks out
Tazapay facilitator
Checks each payment, settles it on Base or Polygon PoS after the request succeeds, and covers the network fee
Merchant's Tazapay USDC wallet
Receives each payment as a normal Collect, ready for balance, FX and payouts
Shaded rows are run by Tazapay

‍

To the agent, the merchant's API is a standard x402 endpoint. To the merchant's finance team, agent revenue is one more set of Collects.

‍

Settle in stablecoins or fiat

‍

Agents pay in stablecoins, but the merchant does not have to hold them. With Tazapay, agent revenue lands in the merchant's USDC wallet, where it can stay in USDC or be converted and paid out in local currency through Tazapay's existing FX and payouts. A data provider that has never touched a blockchain can price its API per call and still get paid in the currency it reports in.

Tazapay runs the payment checks and on-chain settlement described earlier and covers the network fees, so the merchant never needs to hold gas tokens. Only KYB-approved merchants can receive x402 payments through Tazapay, and payers are screened before settlement.

‍

What merchants get

  • No blockchain infrastructure to build or run
  • Settlement in stablecoins or in fiat, in local currency, as the merchant prefers
  • Network fees and on-chain settlement handled by Tazapay
  • Every payment recorded as a normal Collect, with no reconciliation code to write
  • Compliance and KYB through a licensed provider

‍

Because x402 runs on Tazapay's existing stablecoin payment infrastructure, agent revenue does not sit in a separate system. For businesses weighing how stablecoins fit their wider payment stack, our guide to stablecoin payments for global businesses covers the bigger picture.

‍

Stablecoin-related services are provided exclusively by Tazapay Canada Corp, a FINTRAC-registered Money Services Business. Tazapay Pte. Ltd. (Singapore) does not provide Digital Payment Token services under the Payment Services Act 2019.

‍

Sources

  1. Coinbase Developer Platform, Introducing x402: a new standard for internet-native payments, 6 May 2025
  2. The Linux Foundation, Operational launch of the x402 Foundation, 14 July 2026
  3. x402 Foundation, x402 overview and FAQs, accessed November 2026

‍

Product Info
Tazamatch Payee Verification: How It Works and Coverage

When a payout bounces, someone pays for it in hours and fees. A typo in an account number, an account the payee closed months ago or a name that belongs to someone else all end the same way: returned funds, a waiting recipient and extra reconciliation work for your team. Tazamatch is the Tazapay tool built for that problem [1]. It tells you whether a payee's account is real and whether the name you hold lines up with the bank's records, and it does so while the money is still in your balance.

Below is a plain-language walkthrough of how Tazamatch works: what it checks, where it slots into a payout, the three ways to run it, how to read what comes back, how to use it from the dashboard or the API, and where it is available.

‍

What Tazamatch does

‍

The point of Tazamatch is timing. Problems get caught when a payee is added to your records, rather than after a transfer has already gone out. Tazapay positions this as a way to cut down on failed payouts, spot suspicious payees sooner and give recipients more confidence, all without slowing your payout process down [2].

‍

Two payout problems Tazamatch targets
And what the check does about each
The problem
What Tazamatch does
Money goes to an account that is wrong or no longer active
Confirms the account before you create the payout
A payee's name does not match the bank's records, and nobody notices
Gives back a match type and a score comparing your name with the name the bank holds

Source: [1]

‍

A check never moves money. Running Tazamatch sends nothing, holds nothing back from your balance and adds no beneficiary to your account. You simply get an answer to act on [1].

Payouts carry on while checks run. Verification sits alongside your payout operations rather than in front of them, so nothing already in motion is held up [2].

Every corridor answers the same way. Banks in different countries report very different data. Tazapay converts all of it into one standard format, so the rules you build for handling results work wherever your payees are [2].

Use it where it suits you. A check can run as you onboard a new payee, just ahead of a payout, or any other time you want one. Your developers can call it through the Tazamatch API, and your operations team can run it from the merchant dashboard [3][4].

‍

Where Tazamatch fits in the payout flow

‍

Think of Tazamatch as a checkpoint between onboarding a payee and paying them. The product overview lays the journey out in four stages [1].

‍

The payout journey with Tazamatch
A checkpoint between onboarding and paying out
1
Onboard the payee
Collect the recipient's bank and name details.
2
Run a Tazamatch check
Send those details for checking from the API or the dashboard.
3
Look at the outcome
See the status of the check and how closely the name matched.
4
Decide on the payout
Go ahead and pay, hold the payee for a closer look, or turn them down.
Running a check sends no money, holds no funds and adds no beneficiary.

Sources: [1] [5]

‍

Under the hood, each check has the same three beats [5]. You send the payee's account details, Tazamatch opens a verification record with an ID beginning pyv_, and your team decides what to do: pay, review or reject. If you are adding a new country, or you are unsure what a corridor needs, you can first ask Tazamatch whether that corridor is supported and which fields it expects. That step is optional.

‍

Three ways to trigger a verification

‍

How you start a check depends on where it sits in your process, and Tazamatch offers three modes to match [5]. Whichever you pick, you get back a verification record that starts out as pending [3].

‍

Picking a Tazamatch mode
Match the mode to where the check fits in your process
Mode
What you send
Good fit for
Mode A: Standalone
The account details on their own. Nothing is saved as a beneficiary and no existing record is touched.
One-off checks, checking many payees at once, or teams that keep payee lists in their own systems
Mode B: While creating a beneficiary
A new beneficiary with the verify flag switched on. The check happens inside that same call, so there is nothing extra to send.
Checking payees as you onboard them. Note that the beneficiary is saved whatever the check finds.
Mode C: Saved beneficiary
The ID of a beneficiary you already have in Tazapay, in place of the raw bank details.
A fresh check ahead of a large payout, routine re-checks, or payees saved before you switched Tazamatch on

Sources: [5] [3]

‍

How to read a Tazamatch result

‍

Whatever the corridor, a check ends up described by one of a handful of states, plus a match type when the account is found [6]. It opens as pending and then settles into a final state.

‍

What each state means
Pending is the only state that changes
State
Stage
In plain terms
pending
In progress
The check is still running
valid
Final
The bank found the account, and you get a name match score
invalid
Final
No account could be found with the details you sent
not_supported
Final
Tazamatch does not yet cover this corridor

Source: [6]

‍

The API pages add one more outcome, failed. This is when the check itself could not finish, for example because the provider timed out or returned an error. You are not charged for a failed check [7].

A valid result also carries a match type, which tells you how close the name you sent is to the name the bank holds.

‍

Reading the name match
You only see a match type on valid results
Match type
What it tells you
strong_match
The names line up, allowing only for small differences such as capital letters or spaces
partial_match
The names overlap but are not the same, such as a dropped middle name, a short form or a nickname
no_match
The account is real, but the name on it is different from the one you sent

Source: [6]

‍

Valid plus no_match is a signal to look closer, not proof of a bad payee. The account is open, but the bank has a different name on file. Tazapay recommends a careful review before you pay. Whatever the result, including a partial_match or no_match, the decision to go ahead with the payout is still yours.

‍

What a verification returns

‍

A finished check hands back a verification record. The full list of what it holds is in the API overview, and some corridors return more than others [2][6].

‍

Inside a verification record
Summarised from the Tazamatch API overview
Part of the record
What you learn from it
Status and description
How the check ended, plus extra context when there is some
Beneficiary
Which saved beneficiary was checked, when you used one
Beneficiary details
The payee information that went through the check: individual or business, email, tax ID, address, phone and account details
Name match details
The match type, a numeric score (0.97 in the documented example) and a summary label like strong_match
Account exists
A yes or no on whether the account is real
Transaction activity and additional information
Activity on the account and any extra notes from the provider, in corridors that offer them

Sources: [2] [6]

‍

To see what a verification in a given corridor can return, look at its verification metadata [8]. It flags support for account existence, name check, match score, match type, corrected name, translated name and transaction activity.

‍

Using Tazamatch in the dashboard

‍

If Tazamatch is switched on for your account, you can run checks straight from the Tazapay merchant dashboard [4]. There are three things you can do there.

‍

Run a check. Open Tazamatch > Verify Payee, fill in the bank and payee details your corridor asks for, and submit. You see the state and match type on screen. It does the same job as the Create Verification API call.

Look back at past checks. Tazamatch > Verifications lists every check on your account with its state, match type, corridor and time. Open any entry for the full record, including its pyv_ ID and every field that came back.

See what a corridor needs. Under Tazamatch > Capabilities, pick where the money is going, the currency and how it will be paid, and the dashboard shows the fields that corridor requires and what it can check. You only need this when you are unsure.

‍

Using Tazamatch through the API

‍

On the API side, the Tazamatch API guide breaks integration into two main steps, with an optional corridor lookup before them [3].

‍

Before you start (optional): look up the corridor. Send the destination country, plus the currency if you want to narrow it down, to Fetch Verification Metadata [8]. You learn whether the corridor is covered, which bank fields and bank codes it needs, which payee fields it needs (tax ID included), what it can check and its coverage figure. If a corridor is not covered, leave verification out for it.

‍

Step 1: send the check. Call Create Verification in whichever mode suits your process [9]. You get a pyv_ ID back, with the state set to pending.

Step 2: collect the result. Use that ID with Fetch Verification, checking again until the state settles on valid, invalid or not_supported [10]. For a view across all your checks, List Verifications can narrow results by state, match type, destination country, currency, beneficiary, payout rail, date range or a keyword [11].

‍

Let webhooks tell you instead. Rather than checking repeatedly, you can listen for verification webhooks [7]. One event, payee_verification.completed, arrives when a check ends as valid or invalid. The other, payee_verification.failed, arrives when a check could not finish, such as after a provider timeout or error, and carries no charge. Every webhook endpoint you set up receives both unless you turn them off. A not_supported result sends neither, because no check was actually attempted.

Plan for errors. The Tazamatch error codes fall into three groups [12]. The first covers bad or missing inputs, such as the payee type, name, email, phone, destination, country, currency, account number, bank identifier, or fields a particular corridor insists on. The second is a single code for corridors Tazamatch does not cover. The third covers provider-side trouble: rate limits, outages or an internal fault. For that last group, wait a moment and retry, and reach out to [email protected] if it keeps happening.

‍

Tazamatch coverage by corridor

‍

Tazamatch is available in 50+ corridors, with more being added, and what it can do differs from country to country [13]. The table shows, market by market, whether the name is checked, whether the bank's name for the account holder comes back to you, and the coverage figure Tazapay publishes.

‍

Where Tazamatch works today
Name check, name returned and coverage, grouped by region
Country
Name check
Name returned
Coverage
Asia Pacific
Australia (AU)
Yes
No
>90%
China, retail (CN)
Yes
No
>95%
India, IMPS (IN)
Yes
Yes
>95%
India, UPI (IN)
Yes
No
>95%
Indonesia (ID)
Yes
Yes
>95%
Malaysia (MY)
Yes
Yes
>90%
South Korea (KR)
Yes
Yes
>90%
Thailand (TH)
Yes
Yes
>80%
Vietnam (VN)
Yes
Yes
>90%
Europe
Austria (AT), Belgium (BE), Croatia (HR), Cyprus (CY), Estonia (EE), Finland (FI), France (FR), Germany (DE), Greece (GR), Ireland (IE), Italy (IT), Latvia (LV), Lithuania (LT), Luxembourg (LU), Malta (MT), Netherlands (NL), Portugal (PT), Slovakia (SK), Slovenia (SI), Spain (ES), United Kingdom (GB)
Yes
No
>90%
Bulgaria (BG)
Yes
No
<50%
Poland (PL)
Yes
Yes
>60%
Latin America
Argentina (AR)
Yes
Yes
>85%
Brazil (BR)
Yes
Yes
>90%
Chile (CL)
Yes
Yes
>80%
Colombia (CO)
Yes
Yes
>80%
Ecuador (EC)
Yes
Yes
>80%
Mexico (MX)
Yes
Yes
>90%
Peru (PE)
Yes
Yes
>50%
Uruguay (UY)
Yes
Masked
>80%
Middle East and Africa
Ghana (GH)
Yes
Yes
>80%
Nigeria (NG)
Yes
Yes
>80%
Saudi Arabia (SA)
Yes
Masked
>80%
South Africa (ZA)
Yes
No
>70%
United Arab Emirates (AE)
Yes
Yes
>90%
Uganda (UG)
Yes
Yes
>70%
North America
United States (US)
Yes
No
~100%
South Asia
Bangladesh (BD)
Yes
No
<50%
Nepal (NP)
Yes
Yes*
>80%
Pakistan (PK)
Yes
Yes
>90%

‍

Next on the roadmap. In Asia Pacific: China for business accounts, Hong Kong, the Philippines, Singapore and Taiwan. Turkey is next in Europe, and Canada in North America.

‍

Required fields by country

‍

Countries ask for different bank and payee details. You can pull them per corridor from Fetch Verification Metadata, or use the table below, which carries the same information [8].

‍

Bank and payee details each country needs
Bank fields, bank codes, payee fields, tax ID and account types
Country
Bank fields
Bank codes
Payee fields
Tax ID needed
Account types
Asia Pacific
Australia
account_number, country, currency
bsb_code
name, type
No
Retail, Commercial
China (Retail)
account_number, country, currency
swift_code, cnaps
name_local, type
No
Retail only
India (IMPS)
account_number, country, currency
ifsc_code
name, type
No
Retail, Commercial
Indonesia, Malaysia, South Korea, Thailand, Vietnam
account_number, country, currency
swift_code
name, type
No
Retail, Commercial
Europe
Austria, Belgium, Bulgaria, Croatia, Cyprus, Estonia, Finland, France, Germany, Greece, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Portugal, Slovakia, Slovenia, Spain
iban, country, currency
None
name, type
No
Retail, Commercial
Poland
iban, country, currency
None
name, type
No
Commercial only
United Kingdom
account_number or iban, country, currency
sort_code
name, type
No
Retail, Commercial
Latin America
Argentina, Mexico, Peru
account_number, country, currency
None
name, type
No
Retail, Commercial
Brazil
account_number, country, currency
bank_code, branch_code
name, type, tax_id
Yes
Retail, Commercial
Chile, Colombia, Ecuador
account_number, country, currency
swift_code
name, type, tax_id
Yes
Retail, Commercial
Uruguay
account_number, country, currency
swift_code
name, type
No
Retail, Commercial
Middle East and Africa
Ghana, Nigeria, South Africa, Uganda
account_number, country, currency
swift_code
name, type
No
Retail, Commercial
Saudi Arabia
iban, country, currency
None
name, type, tax_id
Yes
Retail, Commercial
United Arab Emirates
iban, country, currency
None
name, type
No
Retail, Commercial
North America
United States
account_number, country, currency
aba_code
name, type
No
Retail, Commercial
South Asia
Bangladesh, Nepal
account_number, country, currency
swift_code
name, type
No
Retail, Commercial
Pakistan
iban, country, currency
swift_code
name, type
No
Retail, Commercial

Source: [13]

‍

Country-specific notes

‍

A few markets come with conditions. In China, only personal accounts can be checked for now, with business accounts planned. India is covered through two corridors: IMPS, which reaches every live IMPS member bank, and UPI. Poland works for business accounts only. Nepal sends back the account holder's name only on a strong match, and Uruguay sends it back partly hidden.

Five markets need a tax number. Saudi Arabia takes the National ID for a person or the Unified Number for a company, and also partly hides the returned name. Brazil takes a CPF for a person or a CNPJ for a company. Chile needs a RUT, Colombia a NIT and Ecuador a RUC. In Bangladesh and Bulgaria, reach is still limited, and Tazapay is working to widen it.

‍

Sources

‍

‍