Privacy Policy Acceptance
At enrollment, a Consumer accepts the Program’s terms, which authorizes Paylead to match Offers from their transaction data. On top of that baseline, they can grant one optional consent. Shift displays the user-friendly label; the API uses the enum value.Pool
The Pool view groups Cashbacks at every stage from creation to disbursement.Vouchers
Vouchers cover the gift-card flow: a Consumer reserves a voucher, pays for it, and either uses it or refunds it.Rewards
Every Reward carries a Consumer-facing status surfaced in the bank app (Pending, Validated, Pool, Paid, Cancelled) and a technical status used by your back-office for accounting and Ventilation. For the full definitions of both tracks and how they map, see the canonical Reward status flow.
Gifts
Gifts follow the same lifecycle as Cashbacks but are issued directly by the Program Manager (welcome bonus, loyalty incentive, one-off promo) instead of being matched against a transaction.Offers
Campaigns
Bank synchronization
These statuses describe the state of the Consumer’s bank connection. Several of them trigger the Scraping Error Webhook.The legacy
SCRAPING status name persists for historical reasons. Paylead’s data collection today relies primarily on PSD2 and regulated account aggregators. See the Scraping entry in the glossary.What’s next
Customer support workflow
Use these statuses to diagnose a Consumer complaint before opening a ticket.
Reward attribution
Why some Cashbacks end up
Not Attributed and how the dedup engine decides.Ventilations and invoices
See how
Validated → Paid In → Paid Out drives the payout flow.Reward lifecycle
Surface the Consumer-facing track in your bank app.