The sandbox lets you try your rewards integration with configured test merchants before connecting production data. Use it to validate account creation, offer activation, purchases and reward notifications, and check which scenarios your fixtures can reproduce. Start with the cashback quickstart or branded rewards quickstart using the fixtures agreed with Percents.
Send requests to https://sandbox.percents.com with your sandbox issuer token and approved source IPs. Production uses https://prod.percents.com.
Authorization: token tok_11111111-1111-4111-8111-111111111111:api_test_secretWith the configured test merchants and offers, you can:
- Browse offers.
- Register cardholder accounts in advance.
- Let supported activity or purchase calls create missing accounts.
- Record offer activation activity.
- Submit purchases and inspect the resulting webhooks.
- Look up purchases to verify how your integration handles the result.
- Test branded balance availability and a later eligible spend with a suitable fixture.
Follow the earn and spend walkthrough for the branded scenario.
Before testing:
- Confirm the fixture's rate, dates, activation policy and availability delay.
- Recreate test accounts and purchases after the daily sandbox purge. Do not rely on old IDs or balances.
- Use the SDK appearance playground only for presentation. Its demonstration data does not process purchases or qualify rewards.
The purchase field merchantId normally carries the merchant identifier supplied by the card network or processor. For this sandbox fixture, use this field as a test override: send the configured test merchant's public mp_ ID to force a match to that merchant, bypassing normal merchant matching. Also send the fixture descriptor:
{
"merchantId": "mp_33333333-3333-4333-8333-333333333333",
"merchantDescriptor": "BRANDED V2 mp_33333333-3333-4333-8333-333333333333"
}Replace the sample ID in both fields with your configured sandbox merchant ID. The override makes earn/spend tests repeatable but does not validate production merchant recognition. In production, continue sending the actual network or processor merchant identifier and purchase descriptor. Do not send the sandbox override. Confirm the matching setup with Percents for other sandbox fixtures.
You can validate only the scenarios your configured fixtures support.
| Scenario | Sandbox limitation |
|---|---|
| Refunds, clawbacks and issuer debits for spent value | Changing a purchase state does not reproduce every outcome. Confirm a supported fixture with Percents first. |
| Mixed bulk responses | Submit valid and deliberately invalid input together, then inspect the failed rows. This tests input validation. |
| Processing failures, delays and notification ordering | The sandbox does not provide controls for every outcome. Invalid input does not simulate these conditions. |
Use the documented HTTP responses and retry rules for outcomes you cannot force in sandbox.