Test the receipt flow
Dry-run the participant and reviewer journeys after you publish, before the campaign starts.
Catch problems before participants do by walking the full journey yourself. A draft campaign can't be opened, so publish it first, then test both what participants see and what reviewers do before the start date.
Publish first, then test before the start date
You can't open a draft campaign. Publish it, then walk both the participant upload flow and the reviewer side yourself — acting as a test participant — before the campaign's start date. Don't wait until real participants arrive to find out that a rule or the review queue is confusing.
Pre-launch checklist
Open the receipt challenge as a participant
Once the campaign is published and before its start date, open the receipt challenge from its participant link and view it as a test participant.
Confirm that the title, subtitle, details, and upload text match what the campaign promises participants.
Submit one clearly eligible receipt
Use a real sample receipt that should pass the challenge.
Check that the on-screen guidance is clear to follow: the image must be clear, sharp, centered on the receipt, and show the merchant and amount.
Submit one receipt that should fail
Also test at least one receipt that should be turned away, such as:
- wrong merchant
- amount that is too low
- blurred photo
This confirms the challenge rejects the right receipts for the right reasons.
Test the reviewer handoff
When to use this: only when the challenge uses manual review.
Open the session through Liste des clients or Scanner un QR Code, then approve or reject the receipt from Validation de Session.
A receipt challenge is not really launch-ready until you have run through this reviewer loop at least once.
Check what the participant sees and the reward state
Confirm what the participant sees after submitting:
- success, with the reward unlocked
- a pending state waiting for review
- a rejection message
- a prompt to resubmit when the receipt was unreadable
Recommendation
Keep a short test pack of receipts before every major launch: one clearly valid, one clearly invalid, and one intentionally hard-to-read. That catches most configuration problems early.