Skip to content
Proxy Developer Docs

Get started with Proxy

Proxy adds a shareable payment handoff to a checkout you already own. A buyer starts the order, another person can pay, and your product still controls the cart, payment provider, fulfillment, and access.

Quickstart goal: choose the provider path before reading implementation details, then leave this page for a concrete guide.

1. Choose your payment provider

Section titled “1. Choose your payment provider”

Stripe

Choose Stripe when your product already takes payment through your Stripe account. Proxy supports one-time payments and subscriptions, including hosted Checkout, embedded Checkout, custom Checkout with Elements, and direct Stripe objects created by your backend.

Choose your Stripe flow →

Shopify

Choose Shopify when the order starts from a Shopify storefront and must finish in native Shopify Checkout. Check the guide for current installation availability.

Check Shopify fit and availability →

2. Confirm the shared model

Section titled “2. Confirm the shared model”
  1. The buyer starts a normal cart in your product or Shopify store.
  2. Your integration creates one Proxy handoff for that intended order.
  3. The buyer shares the handoff; the payer reviews it through Proxy.
  4. The payer completes payment in Stripe or Shopify.
  5. Proxy observes the provider result and sends signed merchant events. Your backend decides when to fulfill the order or grant access.

Proxy does not become your payment processor, merchant of record, catalog, tax engine, or fulfillment system.

3. Know what you will need

Section titled “3. Know what you will need”
  • a Proxy organization and merchant;
  • access to the Stripe account or approved Shopify installation used by the checkout;
  • for Stripe, a server endpoint that can create or recover one durable Proxy handoff for an intended order; the managed Shopify app supplies this server-side step for Shopify;
  • a payer return page or supported Shopify cart surface; and
  • a test order plus a clear success signal in your product.

4. Continue to a concrete guide

Section titled “4. Continue to a concrete guide”

Every provider branch ends with prerequisites, implementation steps, a validation checklist, and the next operational guides:

You are done with provider selection when you can name the provider, who creates the Stripe object if applicable, the payment type, and the page or redirect the payer will use.

Section titled “Earlier Stripe quickstart links”

Stripe setup moved to its own guide when this page became provider-first. These compatibility anchors keep previously published deep links actionable: