Going Live
The final steps before rolling out to production.
1. Swap your credentials
Replace your sandbox credentials with the production ones provided by Fruga.
| Credential | Sandbox | Production |
|---|---|---|
| Partner Key | pk_test_... | pk_live_... |
| Signing Secret | sk_test_... | sk_live_... |
2. Update all integration points
Confirm that production credentials are in place everywhere they are used — both the Partner Key in your frontend widget initialisation, and the Signing Secret in your backend assertion and cashback claim signing. It is easy to update one and forget the other.
3. Verify your server clock
Fruga rejects signed requests with a timestamp more than 300 seconds from its own clock. Confirm that your production servers are NTP-synced before going live — clock drift is a common cause of intermittent 401 errors that are difficult to reproduce in development.
4. Confirm your userRef is consistent
The userRef in your JWT assertion and the userRef in cashback claim requests must be identical for a given user. Do a final check that both code paths are using the same value — typically a stable user ID from your database. A mismatch causes claims to appear against the wrong wallet, or not appear in the widget at all.
5. Point to the production API
Confirm your backend is sending cashback claims to https://api.fruga.com/cashback/claim and not a sandbox or staging URL.
6. Test with a real transaction
Before announcing the integration, trigger one real cashback claim end to end — load the widget as a real user, submit a claim from your backend, and confirm the balance appears correctly in the widget. This final check catches any environment-specific configuration issues that sandbox testing may not surface.