1. Follow the merchant integration pattern
Every official extension implements the same three-step contract, and you can implement it directly against any stack. Your server needs three things — a discovery endpoint, a checkout call, and a settle call. Prism handles all the token math, chain selection, and x402 formatting.Advertise the handler
Expose a
/.well-known/ucp profile that includes the Prism payment handler
(xyz.fd.prism_payment), fetched from your Prism account.Prepare checkout
When an agent starts a checkout, call Prism to get the x402 payment
requirements for that order and return them in your checkout response.
Merchant integration guide
The full three-endpoint walkthrough — request/response shapes, token base
units, and settlement — the exact pattern our official extensions follow.
2. Drop in a server-side SDK
If your backend is in TypeScript, Python, or Java, the Prism SDKs handle authentication, request signing, and payment verification for you — often just a few lines of middleware on the route you want to protect.SDK overview
Framework guides for Express, NestJS, Next.js, Fastify, and the base
language SDKs.
API reference
The Prism Gateway REST API, if you’d rather integrate without an SDK.
3. Bring your own payment handler
Prefer to keep your existing commerce protocol layer and only add settlement? Each official extension exposes a pluggable payment-handler interface — you can ship your own settlement provider as a standalone package that self-registers, without forking the core plugin. The same interface is what our Prism and dummy/test handlers are built on, so there’s a working reference to model yours on in each repository.Understand the protocols first
If you’re new to how agents discover and buy, start with the concepts — the standards are what make any of these paths interoperable.Commerce protocols
UCP, ACP, and x402 — how AI agents discover a store, build a checkout, and pay.
Building an integration for a platform we don’t cover yet? We’d love to hear
about it — get in touch.