Launch a loyalty program
Prove one purchase earns exactly once and remains traceable.
Start this proof loopProve one correct loyalty loop before production.
Use isolated test data to exercise earning, returns, reward gifting, idempotent retries, and signed delivery without moving production customer value.
Free evaluationIsolated test valueNo production commitment
Choose the proof loop your team needs first.
The selection carries into Sandbox Lab. After sign-in, progress comes only from persisted Sandbox records—never from visiting a page or clicking a checklist.
Integrate the API
Prove scoped access, idempotent commerce, and a signed outcome.
Start this proof loopGift a reward
Prove a recipient-bound entitlement without creating transferable value.
Start this proof loopExchange with a partner
Prove both sides reconcile one governed exchange.
Start this proof loopLearn with synthetic value, then keep the receipt.
The free evaluation Sandbox is an isolated place to configure and test. It does not move production customer value, activate a Production environment, or create an SLA or support commitment.
- 1
Open an evaluation workspace
Create or select a Sandbox organization and keep its environment ID and scoped key separate from every Production credential.
- 2
Create one test program and member
Use synthetic identifiers, explicitly enroll the member, and activate only the Sandbox program configuration you intend to prove.
- 3
Send one purchase twice
Use one stable source reference and idempotency key. The retry must recover the original result without issuing value twice.
- 4
Return, gift, and observe
Exercise an exact line return, a recipient-bound catalog-entitlement gift, and at least one signed webhook delivery.
- 5
Save the evidence
Keep request IDs, source references, resulting transaction IDs, balance effects, webhook event IDs, and the owner of every unresolved exception.
Test the outcomes customers and operators will notice.
Identical purchase retry produces one award
Partial return uses original line references
Insufficient balance fails without partial value movement
Gift decline or expiry restores eligible original lots
Duplicate webhook event ID changes downstream state once
Rotated webhook secret leaves the endpoint disabled until reactivated
Nothing crosses implicitly.
Sandbox
- Synthetic members, orders, gifts, and destinations
- Sandbox-scoped keys, program configuration, and webhook endpoints
- Repeatable test evidence without production liability
- Free evaluation access; no public usage allowance is promised here
Production
- New credentials and environment-specific configuration
- Real customer value and merchant operating ownership
- Readiness evidence, approver, rollback, and reconciliation
- A scoped quote and executed terms before commitment
Leave with a reviewable proof pack.
inputsProgram version, synthetic member, source references, exact request bodies, environment, and credential scopes.
outcomesHTTP status, request ID, transaction or gift state, balance effect, webhook event ID, and any replay result.
exceptionsExpected failure, actual response, owner, decision, and the evidence needed before Production.
boundaryA written statement that the run used Sandbox data and is not production-scale, availability, certification, or customer-adoption evidence.