Going live

Certification

Demonstrate these on UAT before Perx enables your vendor slug in production. Your progress is saved in this browser.

Required checks0 / 15

Earn

A signed sale.completed is accepted and the points appear in the Perx dashboard
Sale with a known member returns pointsEarned > 0
Sale with an unknown phone returns 200 with a warningAnd your UI does not show staff an error — this is a normal outcome.
Sale with no customer returns 200 and raises no error
Phone is sent as +9607123456 and matchesConfirm your code never emits a bare 960… form — it will silently fail to match.
Line items carry sku, and an item-based stamp reward advances
A PERX- discount code on an order marks the reward redeemed

Reliability

The same transaction.id sent twice returns duplicate and does not double-count
With Perx unreachable, the sale completes and the event queues and delivers on recovery
A queued event is re-signed with a fresh timestamp before it is retried
A 4xx is dead-lettered and alerted, not retried forever

Security

A tampered body is rejected with 401Proves you sign the raw bytes rather than a re-serialisation.
A timestamp skewed by 10 minutes is rejected with 401
After the merchant rotates the secret, the old one 401s and the new one works once pasted
Sales from a multi-store merchant land on the correct Perx outlet

Optional— only if you built that capability

A refund reverses the correct number of points
Eligibility → redeem → discount on bill → earn, in one sale
A full catalog snapshot syncs and appears in the merchant reward builder

What happens after

Send your Perx contact the request IDs for a few representative deliveries — a successful earn, a duplicate, and a rejected signature. That is usually enough to sign off, because Perx can trace each one end to end. Your slug is then enabled in production and merchants can connect you.