Payments should feel like the rest of the internet: low-friction, programmatic, and safe for humans and autonomous agents. facilitator.dev verifies payment payloads and settles on-chain so your API can stay focused on serving resources.
Why teams use a facilitator →No direct node management or custom verification code. Offload payment verification and settlement to a single, auditable service.
Standardized verification/settlement flows keep behavior uniform across endpoints and teams.
Start accepting payments without rebuilding blockchain plumbing. Keep your app HTTP-native.
The facilitator never takes control of funds. It validates signed client intent and executes accordingly.
Safe for autonomous agents with clear limits and auditable actions—great for machine-to-machine APIs.
You can verify and settle locally. Using a facilitator just accelerates adoption and reduces mistakes.
Checks that a client’s payment payload matches the server’s declared requirements and is correctly signed.
Submits validated payments to the blockchain on behalf of the server and monitors confirmations.
Provides verification and settlement responses so the server can decide whether to fulfill the request.
Executes based on client-signed payloads; does not hold funds. Self-host or swap implementations without breaking contracts.
Clients request resources over HTTP. If payment is required, your resource server can ask for it and delegate verification and settlement to the facilitator. Once confirmed, serve the resource and include transaction details in your response headers.
GPL-3.0 licensed, publicly auditable code. Embraces openness and ensures implementers remain in charge.
Run it yourself or use a hosted instance. Either way, the facilitator remains a trust-minimizing component that only acts per client intent.
Test the flow with a tiny transfer. This demo is set to 1 USDC on Ethereum.