Price, deliver and capture

Build a service integration around explicit prices, supported payment methods and idempotent fulfillment.

Publish an offer

Use the merchant portal to register your service and verify its domain before publishing offers. Offer prices use exact decimal USD strings and integer microcredits, with their credit face value shown alongside dollars.

Challenge and verify

Return a 402 payment challenge when payment authority is missing. List only the payment methods actually implemented and accepted by the offer. Verify the signed voucher against the issuer JWKS, audience, agent, offer, maximum amount and expiry before delivery.

Capture once

Capture the authorized amount with a stable idempotency key. Retries must not double-charge or double-deliver. The workspace SDK exposes AcceptorClient capture and release helpers; service delivery requires verified spending authority and configured provider access.

SDK · Gateway API · Payment methods.

Signed delivery notifications

A verified merchant owner can configure an enabled HTTPS receiver on the merchant domain or a subdomain. The actual webhook contract describes redemption.captured and redemption.released notifications, their ACS-Signature header, stable event IDs, retry budget, and actual receipt logs. Configuration does not establish successful delivery; no historical events are backfilled. Verify the exact raw request body with the one-time webhook secret and deduplicate eventId before side effects. Delivery is at least once and can arrive out of order. Use the merchant portal to inspect actual pending, queued, delivered, or failed attempts.