WALLET BALANCE
— BTC
Loading wallet…
RelayGuard / Payment workspace
Connecting to Mezo…
PAYMENT OPERATIONS
Payments, governed by policy.
Review payment requests, apply clear spending rules, and verify settlement on Mezo.
◇ POLICY-GATED EXECUTION
NETWORKCHECKING
Mezo Testnet
Chain ID — · Block —
AUTHORIZATION LOG
Sign-in required
Hash-linked audit events
MEZO PROTOCOL CONTEXT
Trove-aware MUSD policy
COLLATERAL RATIO—
BTC COLLATERAL—
MUSD DEBT—
Checking the operator’s live MUSD trove before applying spending policy.
NEW AGENT INTENT
Request a payment
CONTROL & SETTLEMENT
Payment journey
1
Agent proposesPayment intent is validated
READY2
Policy decidesLimits and recipients checked
WAITING3
Human reviewApproval when threshold requires it
4
Explicit executionAuthorized signer submits to Mezo
5
Receipt verifiedSuccess only after RPC evidence
The agent never approves its own payment.
Submission and settlement are separate states. A transaction hash alone is not proof of payment.
PAYMENT ACTIVITY
Current transaction
◈
Ready for a payment intentPolicy decisions and verified evidence appear here.TAMPER-EVIDENT RECORD
Audit trail
No recorded decisions yet.
MUSD COMMERCE
One payment layer.
Customers and agents.
Accept MUSD in person, online, or from software agents—with one merchant wallet and verifiable settlement.
Built for both sides of the transaction
Share an exact MUSD invoice by link or QR, or monetize an API with x402. Customers sign with their wallet; agent payments settle through the Mezo facilitator.
MERCHANT WORKSPACE
Account access
Manage invoices and payment activity from your merchant account. Customers can pay through a shared checkout without signing in.
Connecting account…
YOUR RECEIVING WALLETSign in to connect your wallet.Prove ownership with one signature. RelayGuard never asks for your private key.
CUSTOMER CHECKOUT
Create an invoice
Loading merchant…Checking receiving wallet
MEZO MUSDPAYMENT ACTIVITY
Recent invoices
Loading merchant invoices…
Payments are made in MUSD on Mezo Testnet. Each invoice settles directly to your verified wallet. The buyer reviews and authorizes the transfer in their own wallet.
YOUR PRODUCT · x402
Monetize an API endpoint
Register a route from your own API. RelayGuard gives you a scoped API key and a small Express adapter that loads your exact MUSD price and verified receiving wallet. Your server keeps the resource and returns it only after facilitator-confirmed settlement.
Sign in and verify your wallet to set up product integrations.
AGENT CHECKOUT · x402
Unlock an agent integration brief
Give agents a machine-readable Mezo/MUSD integration guide with exact payment terms, Permit2 setup, and settlement-safety checks. Access is unlocked after the facilitator settles an exact MUSD payment.
PROTECTED ENDPOINT
Loading price…
If required, your wallet will request an exact MUSD approval first; that approval transaction uses BTC for gas. The facilitator handles gas for the MUSD settlement.
RELAYGUARD FIELD GUIDE
Good questions.
Clear answers.
A practical guide to MUSD checkout, agent payments, and the Mezo controls behind RelayGuard.
01PeopleQR checkout
02Agentsx402 access
$MUSDON MEZO
03MerchantDirect settlement
ONE RECEIVER · TWO PAYMENT PATHS
Mezo TestnetChain ID 31611
Non-custodial checkoutMerchant receives MUSD directly
Policy-aware agentsLimits, review, verified receipts
THE SHORT ANSWERS
Explore the details
01What is RelayGuard?
RelayGuard is a MUSD commerce and payment-control product built for Mezo. Merchants can create shareable invoices for people, while software agents can pay to unlock a protected API resource. A policy console adds spending rules and settlement evidence.
02How does customer checkout work?
A merchant creates an exact MUSD invoice with an expiry and shares its link or QR code. The customer connects a Mezo-compatible wallet, reviews the transfer, and signs it. RelayGuard checks the Mezo receipt and matching MUSD transfer before the invoice is marked paid.
Invoice→Wallet signs→Receipt verified
03Does RelayGuard hold or custody customer funds?
No. The buyer signs a direct MUSD transfer to the merchant’s configured receiving wallet. RelayGuard records invoice and verification state; checkout funds do not pass through a RelayGuard custody account.
04What does x402 do in this product?
x402 lets an agent request a protected HTTP resource and receive exact MUSD payment terms when payment is required. The buyer signs a payment authorization; the Mezo facilitator verifies and settles it. The API releases the resource only after successful settlement.
05Who pays gas for an agent payment?
The facilitator handles gas for the MUSD settlement. If the wallet first needs to approve an exact Permit2 allowance, that approval is a separate transaction and uses BTC for gas on Mezo. RelayGuard does not request an unlimited token approval.
06How does the trove-aware spending policy work?
Before an operator-authorized MUSD agent payment, RelayGuard reads Mezo trove health and applies an application policy: at or above 150% ICR, configured limits apply; from 110% to below 150%, human approval is required; below Mezo’s 110% minimum, new MUSD authorization is blocked. If protocol data cannot be read, MUSD policy actions fail closed. The 150% buffer is RelayGuard’s choice, not a Mezo parameter.
≥150%LIMITS110–150%HUMAN REVIEW<110%BLOCKED
07Does every buyer need a trove? Does RelayGuard change one?
No. Trove health is a signal for the configured operator’s agent-spending policy; it is not a checkout requirement for customers. RelayGuard’s integration is read-only: it does not open, top up, repay, or otherwise modify a trove automatically.
08What evidence is recorded for a policy decision?
Mezo reads for a decision are pinned to one block. The authorization retains the borrower, block, observation time, price, ICR, collateral, debt, and risk tier. Hash-linked audit events commit policy and evidence digests, so edits to stored evidence can be detected during verification.
09What happens if the trove changes after approval?
RelayGuard rechecks the policy before approval and execution. If the risk tier changed, a stale approval or execution is rejected; the operator can cancel the pending authorization and submit a fresh request. An authorized human can still reject a stale request.
10Is RelayGuard production-ready for mainnet?
RelayGuard is currently a Mezo Testnet demo (chain ID 31611), not a mainnet payment service. Testnet invoice and x402 settlements have been verified. Controlled live testing of policy thresholds, a fresh production QR checkout, and operational hardening remain outstanding. Do not send mainnet funds to this demo.
11Whose wallet balance and trove do I see in the payment workspace?
These are the balances and trove for RelayGuard’s operator-configured signer. They are not your connected wallet, your signed-in account, or a merchant’s payout wallet. The status dashboard is public and read-only; payment controls require sign-in.
12Can my business use its own wallet and checkout?
Yes. The merchant workspace is multi-tenant: each signed-in merchant can verify its own receiving wallet and create invoices that pay that wallet directly. Merchant profiles, invoice history, and x402 resources are scoped to the merchant account; the operator balance shown on this payment dashboard is separate.
13What can I do here without signing in?
Anyone can inspect the operator signer’s public Mezo Testnet balance and trove status. Creating payment requests, viewing protected spending limits and recipient settings, and approving or executing payments require an authenticated account. The separate merchant checkout flow remains available to buyers without a RelayGuard sign-in.
STILL CURIOUS?
Explore RelayGuard in the product.
See the live testnet controls, create an invoice, or inspect the agent checkout flow.