What is ReBate Pay

ReBate Pay is subscription billing infrastructure: accept one-time payments, create subscriptions, handle refunds, and know what happened in real time via webhooks.

View as Markdown

If your product needs to charge for something — a one-time purchase, a monthly subscription, or usage-based billing — ReBate Pay exposes a developer API (/api/Product, /api/PaymentLink, …) your backend calls directly to create customers, products, prices, subscriptions, and payments, without handling the edge cases of payment processing yourself (retries, timeouts, duplicate charges).

You don't need to build your own checkout page: ReBate Pay provides Hosted Checkout (a ReBate Pay-hosted payment page) and Payment Links (a shareable payment URL that needs no code at all). Both notify your system via webhook once a payment completes.

Who this is for

  • First time integrating ReBate Pay — start with the Quickstart and complete your first Sandbox payment in about 10 minutes.
  • Want to see a real integration first — see the SDK examples in Framework Integration, or let an AI integrate for you through the MCP server.
  • Already integrating and need a specific API detail — jump straight to the API Reference.

What's available now

CapabilityStatusNotes
Sandbox payments, subscriptions, refundsAvailableFull API + Hosted Checkout, realMoney: false
Webhooks (signed, retried, dead-lettered)AvailableReal background delivery, not a synchronous callback
Customer Portal (self-service subscription management)AvailableMagic-link verification, no customer password needed
Usage billing / Credits / EntitlementsSandbox / Early AccessAPI is usable; not yet open in Production
Production (real charges)Planned / Not availableRequires KYB approval and external acceptance sign-off
Every capability mentioned in this documentation is labeled with a status like Available / Sandbox. This documentation defers to ReBate Pay's actual API behavior — if anything here disagrees with what the API actually does, trust the API Reference or the API's own response over this page.