Test the receipt flow
Dry-run the participant and operator journeys before you publish the campaign.
Use Preview while the campaign is still a draft
For Transactions, a proper dry run means testing both the participant upload flow and the operator side. Do not wait until publication to discover that the rule logic or queue handling is confusing.
Pre-launch checklist
Open the receipt challenge in Preview
Start from the touchpoint preview link while the campaign is still a draft.
Confirm that the title, subtitle, details, and upload copy match the public campaign promise.
Submit one clearly eligible receipt
Use a real sample receipt that should pass the challenge.
The participant-side instruction should be easy to follow: the image must be clear, sharp, centered on the receipt, and show the merchant plus amount.
Submit one deliberately failing receipt
Also test at least one negative case, such as:
- wrong merchant
- too-low amount
- blurred photo
This is the fastest way to confirm whether the challenge fails in the way you intended.
If the challenge is manual, test the operator handoff too
Open the session through Liste des clients or Scanner un QR Code, then validate or reject the receipt from Validation de Session.
A Transactions setup is not really launch-ready until this operator loop has been tested at least once.
Check the participant outcome and reward state
Confirm what the participant sees after submission:
- success and unlocked reward
- pending state waiting for review
- rejection message
- incomplete resubmission prompt when relevant
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.