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.| Status | API enum | Definition |
|---|---|---|
| Smart Ranking | SMART_RANKING | The Consumer authorizes Paylead to reorder the Offer feed based on their purchase habits. Enables Offer Smart Ranking. |
Pool
The Pool view groups Cashbacks at every stage from creation to disbursement.| Status | Definition |
|---|---|
Not Attributed | The Cashback was discarded because the same purchase generated several candidates from different Consumer IDs (e.g. one bank feed + one account aggregator). Paylead keeps exactly one Cashback per purchase via the Reward Attribution engine; the others are flagged Not Attributed and never paid out. |
Pending Validation | The Cashback is awaiting the merchant’s validation window (typically 30 days). |
Cancelled | The Cashback is no longer eligible (refund, dispute, matching issue, or technical cancellation). |
Validated | The merchant has not cancelled the Cashback. It will be invoiced at the end of the cycle. |
Pool | The Cashback is pooled in the Consumer’s wallet, awaiting transfer. |
Paid | The Cashback has been credited to the Consumer’s bank account. |
Vouchers
Vouchers cover the gift-card flow: a Consumer reserves a voucher, pays for it, and either uses it or refunds it.| Status | Definition |
|---|---|
Reserved | The Consumer has requested a voucher. A unique ID is generated via the third-party voucher service and held for 15 days. |
Confirmed | The Consumer has paid for the voucher. The voucher is confirmed. |
Cancelled | The voucher was cancelled: either the Consumer cancelled the booking, or the 15-day reservation expired without payment. |
Ready | The voucher PDF, including the activation code, has been sent to the Consumer. |
Refunding | Paylead has asked the merchant to refund a confirmed voucher. Only the merchant can accept or reject. |
Refunded | The merchant accepted the refund claim. |
Refund rejected | The merchant rejected the refund claim. |
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.| Status | Definition |
|---|---|
Cancelled | The Gift was cancelled, only possible while in Pending Validation. |
Pending Validation | The Gift is awaiting validation. |
Validated | The Gift is validated. |
Pool | The Gift is pooled in the Consumer’s wallet, awaiting transfer. |
Paid | The Gift has been credited to the Consumer’s bank account. |
Offers
| Status | Definition |
|---|---|
Active | The Offer is live and visible to Consumers. |
| Published | The Offer has been created but its start date is in the future. Consumers cannot see it yet. |
| Deactivated | The Offer was manually deactivated by a Program Manager. |
| Ended | The Offer end date has passed. |
Completed | The Offer budget cap has been reached. |
Campaigns
| Status | Definition |
|---|---|
| Available | The Campaign has been sent by the merchant and is awaiting review. Not visible to Consumers. |
| Accepted | The Program Manager converted the Campaign into an Offer. Visibility depends on the publication date of the resulting Offer. |
Rejected | The Program Manager rejected the Campaign. |
Bank synchronization
These statuses describe the state of the Consumer’s bank connection. Several of them trigger the Scraping Error Webhook.| Status | Definition |
|---|---|
UNKNOWN | The sync status is unknown, usually because the Consumer has not yet linked an account. |
DISABLED | The synchronization has been disabled on this connection. |
ERROR | A sync error occurred: bad credentials or an action required from the Consumer. |
CHALLENGE_REQUIRED | The Consumer must enter a one-time code sent by their bank to acknowledge the sync. |
SCRAPING | The Consumer’s bank account is currently being synced. |
SUCCESS | The Consumer’s bank account sync succeeded. |
SCA_REQUIRED | A complete SCA (Strong Customer Authentication) flow must be performed by updating the connection. |
SCA_REQUIRED_AND_OTP | An SCA flow must be performed, with an additional one-time-password step. |
WEBAUTH_REQUIRED | A complete authentication flow is required via a redirect. |
WRONG_PASS | The credentials are invalid or obsolete. The Consumer must re-enter them. |
ACTION_NEEDED | The Consumer must perform a specific action on the bank’s website or app (e.g. accept updated terms). |
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.