Fireblocks launches Agentic Payments Gateway for stablecoins

Fireblocks announced the Agentic Payments Gateway on May 20, 2026. The product is a hosted x402 facilitator for payment service providers that settles agent-initiated stablecoin payments into existing Fireblocks Vault accounts while enforcing Policy Engine rules and running pre-transfer KYT and Travel Rule checks.

The managed Gateway is offered as a white-label facilitator for PSPs and payments platforms that want merchants to accept agent-originated stablecoin payments without each merchant running its own facilitator. Fireblocks describes the Gateway as chain- and stablecoin-agnostic infrastructure that provides a full audit trail and structured settlement data for merchant settlements.

PSPs must have an active Fireblocks workspace with vault accounts and API access to use the hosted Gateway. Fireblocks lists the managed Gateway as an early-access product that requires commercial engagement and workspace configuration before deployment. Merchant onboarding for a PSP rollout includes mapping the white-label facilitator to merchant acceptance endpoints and planning reporting and reconciliation against Fireblocks’ audit trail.

Merchant servers keep the HTTP 402 payment surface when the facilitator is hosted. Public developer documentation for the open-source facilitator describes a flow in which a merchant returns a 402 response with payment requirements, then calls facilitator endpoints to verify and settle after the client provides a payment signature. Operators are advised to confirm the hosted base URL and authentication details with Fireblocks during onboarding.

Fireblocks publishes an Apache-2.0 self-hosted x402 facilitator on GitHub and in its developer docs for teams that want a test environment today. The self-hosted package includes a CLI quick start, requires Node.js 20+, a Fireblocks API key and PEM secret, and runs on testnet by default unless configured for mainnet. Documented transfer mechanisms include eip-3009 for USDC-style transfers, permit2 and upto-permit2 for broader ERC-20 metered billing, and erc7710 for smart-account delegation. Settlement uses a CONTRACT_CALL into Fireblocks Vaults and private keys remain in Fireblocks custody.

Agent Wallets, built on the Dynamic stack, target fintechs that need users to delegate spend to AI agents. Those wallets use MPC key management and the Policy Engine to enforce per-wallet and per-delegation rules such as spending limits, merchant allowlists, time windows and allowed asset lists. Delegations are revocable and scoped so agents can only sign transactions within defined constraints. Agents can initiate payments to merchants that accept x402 or MPP where protocol support exists.

Fireblocks joined the x402 Foundation and published a security extension that adds request integrity checks and spend governance intended to reduce risks from man-in-the-middle rerouting of facilitator traffic. The managed Gateway offering includes institutional custody controls such as MPC custody, co-signer governance and a structured audit trail.

Fireblocks names Tazapay as an early PSP building agentic acceptance flows on the Gateway. The company positions the managed Gateway as a production-grade, sales-led option for PSPs; the open-source self-hosted facilitator remains available for builders and testing until commercial access to the hosted path is arranged.