Skip to content
snapcasterDevelopers

Path B

Path B is Partner-managed fulfillment. Snapcaster hosts Checkout and payment, then mints one Order per Seller and dispatches it to your Platform. Your Platform receives the Customer block because it needs the buyer’s name, email, and shipping address to fulfil the Order.

Path B order flowSnapcaster dispatches a signed Order to the Platform, which reports Fulfillment through the API.Platformfulfils the OrderSnapcasterhosts Checkout and paymentorder.createdsigned Order + buyer PIIFulfillment APIaccepted, shipped, delivered

Receive order.created

Section titled “Receive order.created”

Each signed Delivery uses the envelope { event_id, type, created_at, data, api_version }. The data object contains the same Order body returned by GET /orders and GET /orders/{orderId} at the same API version. It carries the Customer, line snapshots, external_ref, integer-cent money blocks, Shipping, and applicable tax.

Verify the signature over the raw body before parsing JSON, then deduplicate on event_id. The dedicated Webhook signing guide provides the Node.js verification example.

Delivery semantics

Section titled “Delivery semantics”

Delivery is at least once, so the same event_id can arrive more than once. A timeout or non-2xx response is retried with exponential backoff and eventually parked for manual replay. Arrival order is not guaranteed. Reconcile by the Order id in data.

Drive the Order lifecycle

Section titled “Drive the Order lifecycle”
Order lifecycleAn Order progresses from created to accepted, shipped, and optionally delivered, with Cancellation before shipping and Refund after shipping.createdacceptedshippeddeliveredcancelledrefunded

Use PATCH /orders/{orderId}/fulfillment for accepted, shipped, and optional delivered progressions. The accepted state may be skipped. Use the separate Cancellation command before Shipping and the repeatable Refund command after Shipping. Only terminations emit Order webhooks because your Platform caused the forward progression itself.

Poll as a fallback

Section titled “Poll as a fallback”

Poll GET /orders?since=<ISO-8601> after an outage instead of waiting for a dead-letter replay. The poll and webhook body share one parser at the same API version.

Need help?

Email Marketplace support with this page and the sandbox environment prefilled.

Never include an API key or Signing secret in the message.