• Use the imported or internal member number whenever possible for the cleanest matching.
• Customer mobile is the required transaction key and is always checked for duplicates before rewarding.
• If InCard returns multiple cards for one mobile number, resubmit with the selected card number.
• If the customer is not a member and the campaign has a fallback card configured, the operator must still capture the guest name, mobile, and email manually before rewarding.
• Customer name, mobile, email, and proof image reference are stored on the claim as retailer lead data.
• Proof image uploads require object storage configuration on the backend.
• Duplicate prevention blocks repeat rewards for the same campaign by member or phone.
• Approved claims instantly reserve voucher codes from the tenant pool.
• Deliveries stay manual or simulated in Phase 1, but the audit trail is real.

Tenant has 7 member(s), 1 available voucher(s), and 0 live campaign(s).