Which x402 facilitator should you settle through?
Pick by the rail your buyers already pay on — and by the proof you hold afterward. ScriptMasterLabs' OMNIGATE settles USDC on Base and Arc and mints the payer a soulbound receipt token on Base for every settlement, at no extra charge; ScriptMasterLabs' 402Proof verifies the finalized ledger payment — amount and memo — against the invoice before access is issued, on XRPL and Xahau. Those are two distinct reasons to adopt a facilitator: OMNIGATE gives the buyer an on-chain receipt they can check without asking anyone; 402Proof gives the seller verification that the right payment cleared before anything is released. An agent buying from multiple APIs gets, from an OMNIGATE settlement, a settlement transaction and a receipt mint it can reconcile later; a seller on 402Proof gets, in any dispute, the ledger transaction and the invoice terms to compare. Both facilitators are operated by ScriptMasterLabs, and both settle directly to the seller's own wallet — neither takes custody of merchant funds. This guide is the selection page: the decision table first, the live terms stated flat, the boundaries stated as plainly as the capabilities, and the published proof linked so you can check every claim yourself.
The decision, at a glance
| Your rail and asset | Settle through | How it settles | The proof you hold |
|---|---|---|---|
| Base — USDC | OMNIGATE | x402 v2 exact (v1 also accepted on Base), verified and settled straight to the seller's wallet at mcp-x402.onrender.com | PAYMENT-RESPONSE receipt header, the on-chain settlement transaction, and a soulbound ERC-1155 receipt token minted to the payer on Base |
| Arc — USDC | OMNIGATE | x402 v2 exact on Arc (eip155:5042), same facilitator URL, same terms as Base | The same three records — the receipt token is minted on Base even when the payment settled on Arc |
| XRPL — XRP | 402Proof | Standard x402 v2 exact on XRPL through four02proof.onrender.com | The finalized ledger transaction, checked by the facilitator's verify/settle path |
| XRPL — RLUSD or USDC | 402Proof (invoice flow) | The seller issues an invoice; the payer pays on XRPL; 402Proof verifies the finalized payment against the invoice — amount and memo included — before issuing the access token | The ledger transaction plus the invoice terms it was checked against |
| Xahau — native XAH | 402Proof (hosted invoice flow) | The same invoice flow on Xahau: invoice, on-chain payment, verification, access token. This is a hosted invoice product, not a standard Xahau x402 exact route — see the boundaries below | The ledger transaction plus the invoice terms it was checked against |
| Solana — USDC | Not pitched as ready | 402Proof's discovery advertises a standard sidecar route, but the hosted service's live health report says Solana is disabled. Verify your exact route before relying on it | — |
Terms at a glance — as of November 17, 2026
- OMNIGATE's fee is an optional flat 0.005 USDC per settlement. A standard x402 payment with no fee leg settles with the fee waived inside a daily budget of 50 settlements across all payout addresses and 10 per payout address, counted on the UTC day. Past the budget, a fee-less payment is refused (facilitator_fee_required) until the next UTC day; a payment attaching the fee leg always works, and the fee is collected after the merchant leg — the merchant receives the full merchant amount. ScriptMasterLabs' own services are exempt. Read live from OMNIGATE's /supported document on November 17, 2026; if this page and the live document ever disagree, the live document is the authority.
- OMNIGATE networks and schemes: x402 v2 exact on Base (eip155:8453) and Arc (eip155:5042), plus x402 v1 on Base. Facilitator signer 0x575856D41970615e0a7DF3f76e4F7e5eC0d4E6b0. Onboarding is open and self-serve: no account, no API key.
- The receipt mint costs nothing extra. After settlement, OMNIGATE automatically attempts to mint the soulbound receipt token (Base, contract 0x70f215F2A94410642bf5DBcfc7B2384F47392FA6, token id 0) to the payer — including for Arc settlements. If a mint fails, the payment still stands.
- 402Proof's invoice rail charges third-party endpoints 0.01 in the invoice's asset per verified settlement — 0.01 XAH on Xahau, collected as a second payment carrying the invoice's fee memo; ScriptMasterLabs' own endpoints are fee-exempt. Read live from 402Proof's /health on November 17, 2026.
- 402Proof's standard XRPL exact tariff is $0.0100 USD per successful settlement at list, with automatic loyalty discounts — 20% at 100 prior settlements ($0.0080), 30% at 1,000 ($0.0070), 50% at 10,000 ($0.0050). Verification, failures and retries are free. Per 402Proof's discovery and attestations, merchant fees are accrued; the collection system is not live yet, so accrued balances are not collected revenue.
- 402Proof onboarding is partner-keyed and starts at scriptmasterlabs.com/settle-through-sml. Full catalog, every price on one page: https://scriptmasterlabs.com/sml-products
How OMNIGATE settles — and what the buyer walks away holding?
- Your x402 seller names OMNIGATE as its facilitator (https://mcp-x402.onrender.com). A stock x402 exact payment verifies and settles exactly as it is — no SML-specific client changes.
- OMNIGATE runs an on-chain preflight (nonce unused, payer balance covers the amount), then settles: the merchant leg pays the full amount directly to the seller's wallet. A refusal broadcasts nothing.
- The settlement response carries a PAYMENT-RESPONSE receipt header, and the settlement itself is an on-chain transaction anyone can open in a block explorer.
- About two seconds after the settlement block, the soulbound Receipt Token is minted to the payer on Base — for Base and Arc settlements alike. Soulbound means non-transferable: it is a proof artifact, not an asset. The buyer — human or agent — now holds records it can reconcile without asking ScriptMasterLabs anything.
- OMNIGATE's public fee counters at /x402/fee-stats show waived, collected and exempt settlements, so the fee claim is checkable from the facilitator's own endpoints, not from marketing copy.
How 402Proof settles — verification before access?
- The seller issues a fresh invoice (POST /v1/invoice) selecting the asset and network: RLUSD or USDC on XRPL, or native XAH on Xahau. The invoice binds the endpoint, price, asset, network, destination and expiry (5 minutes), and its memo is the hex of the invoice UUID.
- The payer submits the on-chain payment to the invoice's destination.
- 402Proof verifies (POST /v1/verify): the finalized ledger payment is checked against the invoice — amount exact, memo matching, destination and asset pinned, RLUSD issuer pinned. Underpayment, overpayment on the XRPL probe, wrong destination and wrong memo are rejected.
- Only after verification passes does 402Proof issue the HMAC-signed access token, carrying the invoice and endpoint claims — a token minted for one endpoint is rejected at another, and a settled invoice cannot be spent twice (a duplicate verify returns an explicit 409).
- For a download, an API or an agent-delivered service, the shape is the point: verified payment first, access second — open a new payment route without rebuilding the product.
The boundaries, stated as plainly as the capabilities
- XAH is a hosted invoice flow, not a standard x402 exact route. Native XAH on Xahau is 402Proof's product-specific /v1/invoice → /v1/verify API. It is not advertised — here or in 402Proof's own attestations — as a separately advertised standard x402 v2 Xahau exact kind. RLUSD does not exist on Xahau; RLUSD settles on XRPL only.
- Solana is not pitched as ready. 402Proof's discovery advertises a standard sidecar route for Solana; the hosted service's live /health, read November 17, 2026, reports solana_enabled: false. Discovery is not proof of a live route — verify the prospect's exact route before pitching it as ready, which is why this guide lists Solana as not ready instead of listing it as coverage.
- A receipt proves settlement, not delivery. A payment receipt — OMNIGATE's token included — proves the payment settled. Successful delivery of the purchased resource is a separate proof. Getting both, from a real outside buyer, is the win; this page does not blur the two.
- The published proofs are SELF-PROOF. The proving settlements below are ScriptMasterLabs' own wallets paying through ScriptMasterLabs' own facilitators, labeled SELF-PROOF. They prove the rails work end to end; they are not third-party volume, and no third-party volume is claimed anywhere on this page. 402Proof's discovery states the same posture in machine form: externalThirdPartySettlementsVerified: false. Its published attestations are operator self-probes, not an independent audit.
The proof, pre-assembled
The dated Arc example — both transactions, so anyone can check them: an Arc settlement and its automatic receipt mint on Base. Published in full at scriptmasterlabs.com/switch-to-omnigate and as a citable paper (Walton, T. (2026), First x402 Facilitator Settlement on Arc Mainnet With a Soulbound Receipt Token Minted for the Settlement, DOI 10.5281/zenodo.24235831).
| # | Date (UTC) | Network | Amount | Settlement tx | Receipt mint tx (Base) | Label |
|---|---|---|---|---|---|---|
| 2 | 2026-11-14 16:02:30 | Arc mainnet (eip155:5042) | 0.01 USDC, fee waived | 0x9a21d90286501ced3c48c56f3bdb4c4836116e619ab6414b40a0a0db52438cc5 (Arc block 31,225,528) | 0xb64cd7f111fe3562d08ade000d0bb20a18ff0f3622902103a7e3ffb6a0ae41f1 (Base block 57,408,885) | SELF-PROOF |
| 1 | 2026-11-13 16:42:49 | Arc mainnet (eip155:5042) | 0.01 USDC, fee waived | 0x08edbaa19c897ca25cce8aa29954d72c8df5308919fec6a08d41ed6828565793 (Arc block 31,059,743) | 0x422a30dbe703962cf3b8eba85c16c6444ba28d54c1952f7105a0fde41e8ac5cc (Base block 56,988,753) | SELF-PROOF |
- OMNIGATE's live terms: mcp-x402.onrender.com/supported — the machine-readable fee, waiver budget and signer document this page restates.
- 402Proof's attestations: scriptmasterlabs.com/402proof-facilitator-attestations — the compliance evidence page, with the live attestation feed at four02proof.onrender.com/v1/attestations and live health at four02proof.onrender.com/health.
- 402Proof's configured rails: four02proof.onrender.com/supported — invoice selectors, the payment flow (invoice → payer submits on-chain payment → verify → access token), and the same Solana and Xahau boundaries stated above.
The ask
Keep your current checkout. Give us one paid endpoint and we'll show you the route that fits. On Base or Arc, OMNIGATE settles USDC straight to your wallet and gives the buyer an independently checkable on-chain receipt. For XRPL or native XAH, 402Proof can verify the ledger payment before your service unlocks access. Start with one route, keep your existing setup, and judge it on a real outside payment and successful delivery.
Developers: the free next step
The free x402 Kit scaffolds a working pay-per-call x402 endpoint in one command — npm create @scriptmasterlabs/x402 — free, MIT-licensed, no account, no API key, with OMNIGATE as the default facilitator and facilitator failover built in. Scaffold the seller, settle a first payment inside the waiver budget at no facilitator fee, and read your own receipt token on Base. Selling on the XRPL or Xahau rails instead starts at scriptmasterlabs.com/settle-through-sml.
Get it from ScriptMasterLabs
- HIVE402 — ScriptMasterLabs' machine market, where endpoints settled through these facilitators are discovered and bought: 36,197 endpoints from 2,087 operators, 13,344 probe-verified payable, counted November 17, 2026, at https://hive402.scriptmasterlabs.com.
- OMNIGATE — the facilitator for USDC on Base and Arc: terms and receipts at https://scriptmasterlabs.com/omnigate-facilitator, live machine-readable terms at mcp-x402.onrender.com/supported.
- 402Proof — the facilitator for XRPL and Xahau: evidence at https://scriptmasterlabs.com/402proof-facilitator-attestations, live service at four02proof.onrender.com.
- Browse the full catalog — pay-per-call APIs, MCP servers, and both facilitators' seller routes — at https://scriptmasterlabs.com/sml-products
FAQ
Which x402 facilitator should you settle through? By rail: USDC on Base or Arc settles through OMNIGATE, ScriptMasterLabs' facilitator — payments land directly in the seller's wallet and every settlement mints the payer a soulbound receipt token on Base at no extra charge. XRP on XRPL (standard x402 v2 exact), RLUSD or USDC on XRPL (invoice flow), and native XAH on Xahau (hosted invoice flow) settle through 402Proof, ScriptMasterLabs' second facilitator, which verifies the finalized ledger payment — amount and memo — against the invoice before issuing the access token. Both are operated by Script Master Labs LLC, a Service-Disabled Veteran-Owned Small Business.
What does OMNIGATE charge? An optional flat 0.005 USDC per settlement, verified live from OMNIGATE's /supported document on November 17, 2026. Standard payments settle with the fee waived inside a daily budget of 50 settlements across all payout addresses and 10 per payout address, counted on the UTC day. Past the budget, a payment without a fee leg is refused until the next UTC day; a payment that attaches the 0.005 USDC leg always works, and the fee is collected after the merchant leg. The merchant is always paid in full, directly to their wallet — OMNIGATE takes no custody. No account and no API key are required.
What proof does a buyer get from an OMNIGATE settlement? Three records: a PAYMENT-RESPONSE receipt header on the settlement response, the on-chain settlement transaction itself, and a soulbound (non-transferable) ERC-1155 receipt token minted to the payer on Base — contract 0x70f215F2A94410642bf5DBcfc7B2384F47392FA6, token id 0 — at no extra charge, including for payments that settled on Arc. The mint is attempted automatically after settlement; if a mint fails, the payment still stands. A receipt proves settlement. Successful delivery of the purchased resource is a separate proof.
How does 402Proof verify a payment before releasing access? By invoice. The seller issues an invoice through 402Proof (POST /v1/invoice); the payer submits the on-chain payment on XRPL or Xahau; 402Proof checks the finalized ledger payment against the invoice — amount, destination, asset, expiry, and the memo, which is the hex of the invoice UUID — and only then issues an HMAC-signed access token bound to that invoice and endpoint (POST /v1/verify). Underpayment and wrong-issuer or wrong-memo payments are rejected. On XRPL, 402Proof also supports the standard x402 v2 exact scheme for XRP.
Is native XAH on Xahau a standard x402 exact route? No, and ScriptMasterLabs does not advertise it as one. Native XAH on Xahau runs through 402Proof's hosted invoice flow — the product-specific /v1/invoice to /v1/verify API — not a separately advertised standard x402 v2 Xahau exact kind. RLUSD does not exist on Xahau; RLUSD settles on XRPL. The boundary is stated on 402Proof's own public attestations page.
Does ScriptMasterLabs settle x402 payments on Solana? Not as a ready route, and this guide does not pitch it as one. 402Proof's discovery advertises a standard sidecar route for Solana, but the hosted service's live health report — read November 17, 2026 — reports Solana disabled (solana_enabled: false). Verify the exact route for your endpoint before relying on any Solana claim, ours included.
How do I start settling through OMNIGATE or 402Proof? Keep your current checkout and give ScriptMasterLabs one paid endpoint. For OMNIGATE, point your x402 seller's facilitator URL at https://mcp-x402.onrender.com — onboarding is open and self-serve, no account, no API key; the free x402 Kit (scriptmasterlabs.com/x402-kit) scaffolds a seller with OMNIGATE as the default facilitator. For 402Proof, onboarding is partner-keyed and starts at scriptmasterlabs.com/settle-through-sml. Judge either route on a real outside payment and successful delivery — a payment receipt proves settlement, and delivery is a separate proof.
Canonical: https://scriptmasterlabs.com/facilitator-selection-guide · Related: https://hive402.scriptmasterlabs.com · https://scriptmasterlabs.com/omnigate-facilitator · https://scriptmasterlabs.com/402proof-facilitator-attestations · https://scriptmasterlabs.com/x402-kit · https://scriptmasterlabs.com/sml-products