Skip to content
Proxy Developer Docs

Proxy Developer Docs

Add delegated checkout to your product so a buyer can start checkout and a payer can complete payment.
Start integratingAPI Reference

What Proxy does

Section titled “What Proxy does”

Proxy Checkout is for purchases where the buyer and payer can be different people. Your product creates a handoff from the buyer’s checkout, Proxy hosts the handoff, then sends the payer back to your checkout with a Proxy session ID.

Proxy is not your payment processor, card UI, catalog, tax system, fulfillment system, or merchant of record. You keep your Stripe account, checkout UI, pricing rules, cart logic, and entitlements. Proxy owns the delegated session, hosted handoff, payment-provider webhook normalization, and signed events your backend can use for entitlements.

Integration Path

Section titled “Integration Path”
  1. Configure Proxy with your payment provider, API keys, and hosted handoff settings.
  2. Add your own delegated payment button to the buyer checkout.
  3. Create a Proxy handoff from your backend with the buyer reference and cart snapshot.
  4. Present the returned handoffUrl to the payer.
  5. Let Proxy forward the payer to your checkout page with proxy_session_id.
  6. Open Stripe checkout from your backend and return the client secret to your checkout UI.
  7. If payment unlocks access, handle entitlements from signed Proxy events.

Start with the quickstart if you are adding Proxy to an app for the first time.