Fraud & Usage Limits
Velocity fraud rules and per-reward usage quotas on spending, all configuration-driven — and where referral fraud is handled
Two optional guard rails protect spending: daily velocity limits and per-reward quotas. Each is independent — configure only the ones you want — and a tripped limit refuses the redemption before any customer code is sent, with the reason stated plainly.
Daily Velocity Limits
Three independent ceilings, each per customer, each measured over the calendar day. They live under Settings → Redemption → Daily guards; leave a field blank for no limit.
Limit | What you choose | Refuses when |
|---|---|---|
Points per redemption | A maximum points amount for any one redemption | One redemption asks for more |
Redemptions per day | A maximum count | The customer already made that many today |
Points per day | A maximum total | Today's spending plus this request would cross it |
Failed attempts never count against the customer — only completed redemptions consume the day's allowance. Changes take effect on the next redemption.
Per-Reward Quotas
For specific rewards, cap how many times one customer can ever redeem them:
- One welcome voucher per customer, ever.
- Two birthday treats per customer.
- Rewards without a quota stay unlimited.
The quota counts the customer's completed redemptions of that reward across all time — failed attempts do not consume it.
Referral Fraud Is Separate
Referral programs have their own fraud rules — self-referral, capture velocity per referrer, family and shared-contact matches, allow and block lists — and their own review queue. They are described on Approvals & Fraud Review.
Start loose, tighten with data
Last updated on