What is Transactions?
Understand the receipt-challenge model from participant upload to operator review and reward unlock.
Transactions is OmniLab's receipt-challenge app. It is designed for campaigns where participation depends on a proof of purchase instead of a tap, click, or pure game action.
A participant submits a receipt, OmniLab extracts the purchase data, applies your acceptance policy, then either validates the receipt automatically or routes it to an operator before rewards become available.
The operator tool currently shows several French labels
In the current product, operators commonly see labels such as Liste des Sessions, Validation de Session, and Progression in the receipt-backend screens.
The core flow
The objects you configure
| Object | What it does | Where you usually see it |
|---|---|---|
Receipt Game | The touchpoint itself: appearance, validation rules, reward logic, dates, and advanced settings. | Build -> Touchpoints |
Acceptance Policy | Decides whether the extracted receipt data is eligible to continue. | Configuration -> Receipt Acceptance Policy |
Validation Policy | Decides whether an eligible receipt is approved automatically or sent to manual review. | Configuration -> Receipt Validation Policy |
Challenge Rule | Defines what a participant must achieve to unlock a reward, such as reaching a spend threshold. | Configuration -> Rules |
Winning Option | Defines the reward path that can be unlocked and linked to a receipt-game reward. | Configuration -> Winning Options |
Session | The participant's running record of submissions, validated spend, pending spend, and unlocked outcomes. | Participant page and operator tool |
Receipt Submission | One uploaded image plus its extracted data and validation status. | Participant receipt list and operator review view |
What participants see
On the participant side, the receipt challenge appears as a dedicated Pages touchpoint. The page can show a header image, title, subtitle, details, current validated amount, pending amount when manual review is active, and a button to upload a receipt.
Before the upload starts, OmniLab shows a photo-quality reminder: the image should be clear, sharp, centered on the receipt, and include the merchant name and amount.
If the receipt is accepted immediately, the participant sees a success state. If it needs manual review, the participant sees a pending message and, in manual mode, a QR-based host validation step can appear.
What operators see
The receipt-backend operator flow is built around three views:
Liste des Sessionsfor searching and filtering participants.Validation de Sessionfor checking receipt status, totals, reward progress, and individual submissions.Progressionfor aggregated metrics such as total sessions, valid submissions, total amount, average basket, and remaining reward availability.
From the session view, operators can open one receipt and choose Valider, Refuser, or Modifier depending on what the OCR found and what the policy allows.
When Transactions is the right app
Transactions is usually the right choice when you need at least one of these outcomes:
- prove a real-world purchase before a reward is unlocked
- require a spend threshold such as "Spend 30 EUR"
- restrict participation to named retailers or store areas
- validate receipts on-site with staff before a prize is released
- measure validated spend as part of campaign performance
Example campaign
Imagine a shopping-center activation:
- the participant must spend at least
30 EUR - only partner merchants are eligible
- one validated receipt unlocks a tote bag
- higher spend unlocks a second reward later in the week
In that setup, the receipt challenge is the control layer between real purchase behavior and the reward stock. A game alone would not be enough because the campaign needs proof of purchase and merchant filtering.
Related
Your first receipt challenge
Build and test a first end-to-end setup from campaign to receipt submission.
Create a receipt game
Create the touchpoint and fill the participant-facing basics.
Acceptance policy overview
See which receipt checks run before a submission can count.
Manual validation queue
Understand how operators review sessions and receipts after submission.