Table of Contents
PSPs that need merchants to take agent-initiated stablecoin payments, and fintechs that need users to delegate spend to AI agents, now share one Fireblocks suite for that lifecycle.
The Fireblocks Agentic Payments Gateway is the PSP-facing hosted x402 facilitator that settles into Fireblocks Vaults with Policy Engine, KYT, and Travel Rule checks. Agent Wallets (powered by Dynamic) are the fintech-facing side that scopes what an agent may spend.
This guide covers what operators can enable as of September 20, 2026 from Fireblocks' Agentic Payments product page, the May 20, 2026 launch blog, and the public x402 Facilitator developer docs. It does not invent pricing, chain lists, or unpublished API hosts.
Key Takeaways
- Agentic Payments Gateway is a hosted x402 facilitator PSPs can white-label for merchant agentic acceptance into Fireblocks Vaults.
- Suite compliance ships Policy Engine, pre-transfer KYT, Travel Rule, MPC custody, and co-signer governance on the Gateway path.
- Agent Wallets (Dynamic) let fintechs issue wallets with scoped, revocable agent spend limits, allowlists, time windows, and asset constraints.
- Fireblocks joined the x402 Foundation and published a security extension for request integrity and spend governance against MITM rerouting.
- Named downside: the managed Gateway is early-access / talk-to-sales; public how-to depth today is strongest on the open-source self-hosted facilitator.
Who this is for
Use the Gateway path if you are a PSP or payments platform that must let merchants accept agent-originated stablecoin payments without each merchant standing up its own facilitator.
Use Agent Wallets if you are a fintech issuing wallets and users will delegate spend to agents over x402 or MPP. Fireblocks' blog positions both products as one suite covering send and receive.
Tazapay, a regulated cross-border payments company serving businesses across 70+ markets, is cited as an early PSP building agentic flows on the Agentic Payments Gateway.
Gateway vs Agent Wallets vs self-hosted facilitator
| Piece | Buyer | What it does | Public enable path |
|---|---|---|---|
| Agentic Payments Gateway | PSPs | Hosted x402 facilitator; settle to Fireblocks Vaults; Policy Engine, KYT, Travel Rule | Product page + sales / early access for managed hosted facilitator |
| Agent Wallets (Dynamic) | Fintechs | User wallets with MPC; scoped agent delegation (limits, allowlists, windows, assets) | Fireblocks Agent Wallets + Dynamic agent payments docs |
| Open-source x402 Facilitator | Merchants / builders | Self-run verify + settle via Fireblocks CONTRACT_CALL | github.com/fireblocks/x402-facilitator + developers.fireblocks.com docs |
Stablecoin Insider already covers buyer-side wallets such as Crossmint Agent Wallets and seller-side checkouts such as Coinbase Business Checkouts. Fireblocks is the institutional custody stack putting a compliance-first facilitator and vault settlement in the middle.
What the Agentic Payments Gateway enables
Per Fireblocks' product page, the Gateway lets PSPs accept agentic payments by receiving agent-initiated stablecoin payments in Fireblocks Vaults via a hosted x402 facilitator.
Security and compliance controls called out on the same page include policy controls, pre-transfer KYT, and Travel Rule checks, plus reporting and reconciliation with a complete audit trail and structured settlement data.
The May 20, 2026 blog describes the Gateway as a purpose-built hosted facilitator any PSP can white-label and deploy across its merchant base, on chain- and stablecoin-agnostic neutral infrastructure, with Policy Engine, KYT, Travel Rule, MPC custody, and co-signer governance.
Fireblocks also says it joined the x402 Foundation and delivered a security extension that adds request integrity and spend governance to the protocol, aimed at preventing man-in-the-middle rerouting attacks that other facilitators do not address.
How to enable the Gateway (PSP operator path)
There is no public self-serve console walkthrough for the managed Gateway. Operators should treat enablement as a Fireblocks commercial + workspace setup, then merchant middleware.
Step 1. Confirm workspace and vault readiness
You need an active Fireblocks workspace with vault accounts that will receive merchant settlement, API access for settlement transactions, and the Policy Engine / compliance tooling your risk team already uses for transfers.
The product page's settlement story is Vault receipt via the hosted facilitator. Do not assume a new vault product; wire Gateway acceptance into the vaults and policies you already operate.
Step 2. Engage Fireblocks for Gateway / hosted facilitator access
Fireblocks' developer docs distinguish the open-source facilitator you run yourself from a fully managed hosted x402 Facilitator (production-grade security, monitoring, managed endpoint) and explicitly say to talk to Fireblocks about early access.
For PSP white-label rollout across a merchant base, start from the Agentic Payments Suite page or info@fireblocks.com as listed on Fireblocks marketing, and ask specifically for Agentic Payments Gateway / hosted facilitator early access.
Step 3. Map PSP white-label to merchant acceptance
The blog's PSP pitch is that merchants get a configurable, production-grade way to accept agentic payments once the Gateway is deployed for the PSP. Plan merchant onboarding, settlement reporting, and reconciliation against the audit trail Fireblocks advertises.
Use Tazapay's public quote as a reference shape: merchant-ready agentic acceptance at scale on neutral infrastructure across many markets, not a single-chain hobby facilitator.
Step 4. Align compliance: Policy Engine, KYT, Travel Rule
Before go-live, encode spend and transfer guardrails in the Policy Engine, and confirm pre-transfer KYT plus Travel Rule checks run on agentic settles the same way they do on your other Fireblocks flows.
Stablecoin Insider's take: treat agentic acceptance as another institutional transfer rail. If KYT or Travel Rule would block a human-initiated vault transfer, it should block the agentic path too.
Step 5. Wire merchant servers to verify then settle
Even when the facilitator is hosted, merchant servers still own the HTTP 402 surface. Public Fireblocks docs describe the pattern: return 402 with payment requirements, then call facilitator POST /api/payments/verify and POST /api/payments/settle after the client retries with a payment signature.
Those endpoint shapes are documented for the open-source facilitator. Confirm the exact hosted base URL and auth with Fireblocks during Gateway onboarding rather than hard-coding a guessed host.
Parallel path: self-hosted open-source facilitator
If you need a public, reproducible lab today, Fireblocks publishes an Apache-2.0 facilitator at github.com/fireblocks/x402-facilitator.
The full quick start lives on developers.fireblocks.com.
Documented prerequisites include Node.js 20+, a Fireblocks API key, vault account ID, and PEM API secret.
The facilitator is testnet-only by default unless X402_ALLOW_MAINNET=true.
Public CLI flow (summarized from docs): npm run setup, configure Fireblocks credentials, npm run dev, mint an admin JWT, x402 fireblocks test --create-missing, import an asset with a transfer mechanism, add a product, then x402 keys create for the merchant API key.
Documented transfer mechanisms: eip-3009 (USDC-style), permit2 / upto-permit2 (ERC-20 / metered), and erc7710 (smart-account delegation). Settlement uses Fireblocks CONTRACT_CALL; raw keys never leave Fireblocks.
For facilitator selection tradeoffs more broadly, see how to choose an x402 facilitator for USDC.
Agent Wallets path (fintech / Dynamic)
Fireblocks Agent Wallets, powered by Dynamic, let fintechs issue wallets users can safely delegate to AI agents.
Users keep custody through embedded wallets and MPC key management. Agents get scoped, revocable spending authority bound by the Fireblocks Policy Engine before anything signs.
Per-wallet and per-delegation rules enforce spend limits, merchant allowlists, time windows, and asset constraints. Agents can pay merchants accepting x402 or MPP, with support expanding as protocols emerge.
Compare that buyer-wallet model with Circle Agent Wallet and Crossmint Agent Wallets on Stablecoin Insider when you are choosing an agent spend stack rather than a PSP acceptance stack.
Lifecycle Fireblocks publishes
Fireblocks' product diagram runs: user sets delegation rules, Agentic Wallet enforces access and policy, the AI agent initiates payment within delegated authority, the merchant API exposes a payable endpoint, the facilitator validates and runs compliance, then funds settle to the merchant wallet with an audit trail.
That is the same HTTP 402 agent commerce pattern Stablecoin Insider covers in accepting x402 USDC from AI agents and Cloudflare Agents x402 MCP tooling, with Fireblocks adding institutional vault settlement and compliance hooks.
Stablecoin Insider's take
Stablecoin Insider's take: Fireblocks is packaging agentic payments the way institutions already move stablecoins, vaults, policies, and Travel Rule, not as a hobby facilitator.
If you are a PSP, prioritize Gateway early access and compliance mapping. If you are a builder validating x402 tomorrow, start on the public self-hosted facilitator and keep the managed Gateway as the production off-ramp once commercial access lands.
Need the buyer-side USDC wallet path next?
FAQ
What is the Fireblocks Agentic Payments Gateway?
It is Fireblocks' PSP-facing hosted x402 facilitator for accepting agent-initiated stablecoin payments into Fireblocks Vaults, with policy controls, pre-transfer KYT, Travel Rule checks, and settlement reporting.
How is the Gateway different from Agent Wallets?
Gateway is acceptance for PSPs and merchants. Agent Wallets (powered by Dynamic) are the fintech wallet layer that lets users delegate scoped spend to agents with MPC and Policy Engine controls.
Is the hosted Gateway the same as the open-source x402 facilitator?
No. Public docs describe an Apache-2.0 self-hosted facilitator you run yourself, and separately a managed hosted facilitator available through early access. The product-page Gateway is the managed white-label PSP path.
Which compliance controls does Fireblocks advertise for agentic payments?
Policy Engine workflow guardrails validated pre-transaction, embedded KYT and Travel Rule for agentic payments, MPC key management, and co-signer governance, plus audit trail and structured settlement data on the Gateway.
Who is an early PSP reference?
Fireblocks cites Tazapay, a regulated cross-border payment infrastructure company serving businesses across 70+ markets, as among the first building agentic payment flows on the Agentic Payments Gateway.
What transfer mechanisms does the public facilitator document?
eip-3009 for USDC-style transferWithAuthorization, permit2 and upto-permit2 for broader ERC-20 and metered billing, and erc7710 for smart-account delegation. Confirm hosted Gateway mechanism support with Fireblocks during onboarding.
This content is provided for informational and educational purposes only and does not constitute financial, investment, legal, or tax advice; no material herein should be interpreted as a recommendation, endorsement, or solicitation to buy or sell any financial instrument, and readers should conduct their own independent research or consult a qualified professional.
){kind=link}