Skip to main content
Use the verified device and account to recognize repeat coupon use.

Where to integrate

Identify before applying a coupon and finalizing the order. Start with the SDK for your stack and retrieve the result on your backend.

What to read

Check the campaign’s redemption ledger and linked-account evidence. Use the current Risk Score and flags, plus High-Risk Events where relevant. Treat a missing or incomplete result as an explicit unverified state.

How to act

Reserve and consume an eligible redemption in the same transaction as the order. A device-based limit is an example application policy; define legitimate shared-device behavior and coupon eligibility explicitly.

Build the example

The runnable tutorial includes the starting app, the completed integration, and steps to test its behavior. Its application policy is stated separately from ShieldLabs detection. For implementation details, see Acting on results and Identification flow. Verify the expected domain, result age and account association, and consume protected actions atomically.