Live on Solana mainnet, small limits. Status page.Reviewed internally. Early. Real money. Use with caution.Report a problemState as of October 2026

Product

Platform

The parts, and how far along each one is. Status as of October 2026.

Live on Solana mainnet, USDC, small limits. Devnet (test network) preview: test tokens only.

9
payment statuses, one at a time per payment
1,000+
automated tests, last counted October 2026
2
rails, one ledger: wallet on mainnet and devnet, card on a mock provider
0
customer funds held by Payzilla
01

Try the rules

Set the rules

Test network (devnet), test tokens.

Try the rulesSample
Price the seller asks
0.002 test USDC
The agent's limit per call
0.05 test USDC
The seller's release threshold
5 test USDC

Who is being paid

Ticked: The allow-listed seller

Not ticked: A different wallet

The agent's decision
PaysThe price (0.002) is within the agent's limit (0.05). The recipient is on the agent's allow-list.
When the seller releases
At Captured0.002 is at or below the seller's threshold of 5, so the seller can serve as soon as the transfer is confirmed.
Sample rules.
Who sets these rules today

The agent's limits live in the demo agent today, and the release threshold is set per seller by us, with a default of 5 test USDC. Neither is self-service yet.

02

The system, part by part.

What we have built

Wallet to wallet today.

Number of parts per job and state
JobLiveBuilt and testedIn developmentMock onlyPlanned
Get paid33000
Stay in control03201
See and reconcile02200
Run it safely23100
Connect more01020

25 parts. The outside boxes are not counted.

funds move from the buyer’s wallet to the seller’s wallet, outside Payzilla

Get paid: 6 parts
Get paid: parts and status
PartStatusDetails
Seller paywallBuilt and tested (reference code)
What it does
Runs on the seller’s server. Asks the API for the 402 challenge and shows it to the buyer. It calls verify and settle before it serves.
How it is checked
Tested end to end, including a replayed payment and a hostile run.
The limit
Reference code, not a packaged SDK.
Payzilla APILive
What it does
Takes requests from the seller’s paywall: creates the payment challenge, then verifies and settles. It answers settle only when the payment is released.
How it is checked
Tested end to end, including a replayed payment and a hostile run.
The limit
Mainnet: api-mainnet.payzilla.ai, with small limits. The devnet preview runs on private staging and has no public base URL.
Payment verifierBuilt and tested
What it does
Checks the exact transaction layout, amount, recipient and memo before anything is signed.
How it is checked
Property tests: the signer signs only when the payment is exactly right.
The limit
Solana, exact scheme, only.
x402 on SolanaLive
What it does
Runs one payment: checks the limits, runs the verifier, asks the signer for the fee-payer signature, sends the transaction, follows it to Captured and Final, and posts the ledger.
How it is checked
Tested, with fault injection and a reverted-payment path.
The limit
Live on Solana mainnet with small limits. On devnet, a preview by invitation.
Chain access and finalityLive
What it does
Reads and sends through several independent providers that must agree, and tracks each payment to Captured, then Final, including reversals.
How it is checked
Tested, with fault injection and a reverted-payment path.
The limit
Live on Solana mainnet with small limits. On devnet, a preview by invitation.
Signed webhooksBuilt and tested
What it does
Tells the seller’s system about each payment event, with a timestamped signature and retries.
How it is checked
Signature, retry and destination-safety tests.
The limit
Endpoint registration and secret rotation are not available yet.
Stay in control: 6 parts
Stay in control: parts and status
PartStatusDetails
Agent mandateBuilt and tested (agent side)
What it does
A maximum price per call, a daily budget and a list of allowed recipients. The agent enforces it before it signs. Payzilla does not.
How it is checked
Tested, including a tampered listing refused before anything is signed.
The limit
Lives in the demo agent. A reusable mandate service is planned. Payzilla cannot stop a payment an agent chooses to sign.
Address screeningIn development
What it does
Checks the payer against a public sanctions list, synced daily, when a payment is admitted.
How it is checked
A daily sync runs on staging. On staging, a new payment is also refused unless its source token account belongs to the payer who signs. A sanctions list older than the newest one already applied is refused, and a list that has gone old raises an alert.
The limit
The list holds very few Solana addresses, so it is a baseline, not coverage. On the devnet preview a stale list only raises an alarm. The production configuration is built to block new payments when the list is stale, and to screen both sides of a payment; the preview does not turn that on. No commercial provider has been chosen.
Per-seller limitsBuilt and tested
What it does
Limits for each seller on payment size, daily volume, unfinalized exposure and daily network fees. They run on private staging and on the live account. Checked before anything is signed. They bound how much network fee is spent for each seller. They do not change who pays.
How it is checked
Run on private staging with test values and on the live account.
The limit
No values are published. No outside seller is on them yet.
Wallet ownership proofIn development
What it does
A seller proves it controls its receiving wallet by signing a message.
How it is checked
In development.
The limit
Not self-service yet.
Network-fee policyPlanned
What it does
Decides who pays the network fee.
How it is checked
The resolver is tested.
The limit
One Payzilla-run account pays the network fee for every seller, on devnet and on the live account. A per-seller choice is not built.
Release policyBuilt and tested
What it does
Decides when a seller may serve: settle reports success at Captured up to a threshold, at Final above it.
How it is checked
Tested on both sides of the threshold.
The limit
Set per seller by us. Not self-service yet.
See and reconcile: 4 parts
See and reconcile: parts and status
PartStatusDetails
One ledgerBuilt and tested
What it does
Append-only, balanced entries for every rail.
How it is checked
Database guards and tests. A reversal must mirror the original.
Payment statesBuilt and tested
What it does
Nine statuses, one per payment at a time, including Reverted.
How it is checked
State-machine and property tests.
The limit
Names may still change before a hosted release.
Reconciliation breaksIn development
What it does
Reads the ledger and the chain and flags a mismatch with the network or the provider. It detects and does not repair.
How it is checked
Built for card settlement files and reverted payments.
The limit
Most checks run on private staging. A few are still to finish.
DashboardIn development
What it does
A read-only view of payments, timelines and ledger entries, read through the API.
How it is checked
Tested, and it shows real devnet payments.
The limit
A prototype. Routing, wallet and onboarding screens are previews.
Run it safely: 6 parts
Run it safely: parts and status
PartStatusDetails
Duplicate protectionBuilt and tested
What it does
One claim per payment signature, so the system is built to settle a repeated request once.
How it is checked
Tested, including repeated and concurrent requests.
The limit
Live on Solana mainnet with small limits. On devnet, a preview by invitation.
Signer and key handlingLive
What it does
Adds the network-fee payer’s signature, and only to validated payments. The key is held in AWS KMS, in staging and on the live account.
How it is checked
Tested live on devnet with a KMS key.
The limit
One shared fee-payer key; a key per seller is planned. The separate signing service is described in the next row.
Separate signing serviceLive account
What it does
A separate service that alone holds the permission to sign, so the part that talks to customers would not.
How it is checked
It runs as its own service on the live account. Staging and the devnet preview still sign inside the main service.
The limit
The production configuration uses a separate signing service whose key policy admits only that service. The devnet preview signs inside the main service with a staging key.
Key service (AWS KMS)In use on staging and live
What it does
Holds the network-fee key in a managed key service, on private staging and on the live account.
How it is checked
Tested live on devnet with a KMS key.
The limit
One shared fee-payer key. A final review of the signing setup has not been done yet.
Merchant isolationBuilt and tested
What it does
Row-level security keeps each merchant’s data apart.
How it is checked
A 103-check role test on managed staging, and tests with several merchants on a real PostgreSQL.
The limit
Staging has one merchant, so cross-merchant checks there use an unknown merchant.
Freeze switch and alarmsIn development
What it does
Alarms, a runbook for reconciliation breaks and a freeze switch for the signer.
How it is checked
Built; drilled in our own testing.
The limit
On-call is still to do. A restore test has passed once; a regular schedule is still to do.
Connect more: 3 parts
Connect more: parts and status
PartStatusDetails
Routing engineBuilt and tested
What it does
First-match rules decide which rail handles a payment.
How it is checked
Unit and property tests.
The limit
Two fixed rules today. An editor is in development.
Card checkout APIMock only
What it does
Starts a card payment and hands the visitor to the provider’s hosted card fields.
How it is checked
Tested end to end, including refunds and disputes.
The limit
Mock provider only. No real card provider is connected.
Card connectorMock only
What it does
Authorizes, captures, refunds and handles disputes against a mock provider.
How it is checked
Reviewed twice, with fixes tested.
The limit
No real card provider has been chosen.
Outside Payzilla: 3 parts
Outside Payzilla: not counted as parts
PartWhereDetails
Buyer or agentOutside Payzilla
What it does
A person or an AI agent that wants a resource. It is not part of Payzilla.
Buyer’s walletOutside Payzilla
What it does
The buyer’s own wallet signs its part of the payment. Today the tokens move from it to the seller’s wallet.
SolanaOutside Payzilla
What it does
Mainnet, where live payments settle in USDC, and devnet, the test network, with test tokens only.
What the status labels mean
  • Live: it runs on Solana mainnet with small limits.
  • Built and tested: it has tests and runs on devnet, private staging or the live account.
  • Partly built: some of it exists on staging, the rest is still to do.
  • In development: being built now.
  • Mock only: tested against a mock.
  • Planned: intended, not built, no dates.

The devnet preview uses test tokens only. Checks and limits described here are for devnet and private staging unless a row names the live account.

What is planned is also on the roadmap, with no dates.

03

Limits

Status as of October 2026.

  • Internal reviews

    With fixes and tests.

  • Small limits

    Live on Solana mainnet with small limits. No real card provider.

    No customer funds held
  • Software

    No licences or certifications claimed.

    Wallet to wallet today
The full wording

Internal reviews. With fixes and tests.

Small limits. Live on Solana mainnet with small limits. Devnet and test tokens in the preview. No real card provider.

Software. Today the tokens move from the buyer’s wallet to the seller’s wallet. Payzilla claims no licences or certifications.

Try one payment, or start selling

Real money. A Solana payment cannot be undone. The demo costs 0.01 USDC, about one US cent, from your own Solana wallet. Before you pay, check that the address bar says demo.payzilla.ai. Payzilla does not refund live demo payments. Tested with Phantom, Solflare, Trust Wallet and MetaMask.