Introduction

The Revisit Developer API gives your backend the same loyalty business the merchant app runs: programs, customers, earning and redeeming, refunds, checkout holds, wallet passes, gift cards and tickets, campaigns, reports and billing. One bearer key, one business, and every action lands in the same balances and history the counter and the wallet pass show.

Base URL#

Every call goes to https://app.revisit.cards/v1/developer over HTTPS. The merchant app's own /v1 routes are internal and may change without notice: call only /v1/developer.

What you can build#

• Stamp from the till: your POS earns for each paid order, once per order even when it retries.
• Join at checkout: enroll a customer by your own id on your website or order form, then hand them an Apple or Google Wallet pass.
• Refunds that add up: take back stamps, points or credit for a refund, and let the owner decide when the reward was already used.
• Hold at checkout: reserve part of a balance while a payment is pending, then confirm or release it.
• Passes at scale: issue gift cards, offers, event tickets, boarding and transit passes from your own system.
• Campaigns and reports: send wallet push or SMS campaigns under the shop's rules and read the dashboard's numbers.

Not in this release#

There are no SDKs and no outbound webhooks yet: you call the API and read status. Background work (imports, exports, displays) answers 202 with a reference you read later.