What does Recurring handle?
The full subscription lifecycle, not just the happy path. Trials, pauses, resumes, and three ways to cancel, including canceling with the unused portion credited back. Change plans mid-cycle and the math is handled fairly and automatically: upgrades charge the difference, downgrades credit it, and credits apply themselves before the next charge. Nobody gets shorted, and nobody opens a support ticket about a proration.
Invoices arrive branded with your logo, tax-aware, and served on a hosted page your customers can actually pay from. Standalone invoicing, with no subscription attached, runs on the same rails. Every customer notification (receipts, failed payments, renewals, trial endings, card expirations) goes out under your name, worded your way. The billing edge cases are where subscription revenue quietly leaks; the point of this module is that you stop thinking about them.
How does dunning work when a payment fails?
Failed charges enter automatic recovery tuned to the customer behind the card: patient with your reliable subscribers, faster-moving with the risky ones. Recovered payments rejoin the billing cycle on their own, and built-in guards make sure a dead subscription cannot keep quietly accruing losses. You set the policy in settings; the machine runs it every night.
Every recovered payment is revenue you already earned. Ask your current billing provider what their recovery rate is and how they would prove it; here the recovery numbers are tracked and yours to inspect. Account Updater integration (Visa VAU, Mastercard ABU) is on the near-term roadmap to catch reissued cards before they ever decline.
What about usage-based and complex pricing?
Metered usage billing, coupon and promotion engines, subscription bundles, scheduled future-dated plan changes, and multi-phase pricing schedules are all module features, not integrations. Analytics ship with the module: MRR, churn rate with alert thresholds, churn prediction, and cohort forecasting.
For finance teams, ASC 606 revenue recognition is built in, per merchant and across a portfolio. Your controller closes the month from a report, not from a spreadsheet reconstructed out of billing exports.
What can customers do without contacting you?
A magic-link customer portal covers the routine work: pay invoices with the card on file or a one-off card, update payment methods against the PCI-scoped vault, preview a plan change with its proration before confirming, pause or cancel, with retention offers surfaced at the exit. The same portal handles the rest of the account: live usage meters, coupon codes, account credit with statement downloads, self-serve add-on items, receipt PDFs for every payment, and the customer's own billing profile. Acquisition is handled the same way: hosted checkout, shareable payment links, and an embeddable pricing-table widget backed by a public catalog API. With the QorElementals expansion, the same capabilities become embeddable components (plan picker, subscription manager, invoice viewer, usage dashboard) that render inside your own product.
Every task a customer handles in the portal is a ticket your team never staffs, and the retention offer at the exit is a cancel you may not take.
Add it up across a year of billing: card updates, invoice copies, plan questions, cancellations. Either a person handles each one, or the portal does, at any hour, without a queue. Merchants coming off manual billing tell us this is the change they feel first.
Want to see the portal wearing your branding? Talk to Sales and we will set one up on demo data.
How does it compare to Stripe Billing and Adyen?
The feature bar was drawn deliberately against both, and the parity list has largely shipped: subscription schedules, bundles, coupon and promotion engines, customer balances, and credit notes are module features today. But two structural differences never show up in a feature matrix. First, economics: a billing layer priced on top of someone else's processing stacks two margins; Recurring runs on the processor QorPay owns, so there is one. Second, tenancy: Recurring is portfolio-native, so an ISO or platform runs billing across every account from one view while each account stays fully isolated. Stripe Billing was built for one merchant at a time; this was built for a book of them.
What's available through the API?
Everything the portal does, the REST API does: subscriptions, plans, customers, and a public catalog API for your storefront. Your systems hear about every billing event through signed webhooks, with a delivery log you can audit and a test-fire button so you never wonder whether the pipe works. When something does not arrive, you can see why and replay it, instead of filing a ticket and waiting.