Billing & the ledger

Billing is one of the parts of a SaaS backend that's deceptively easy to get subtly wrong — a discount that doesn't reconcile, a refund that doesn't reverse cleanly, tax computed inconsistently between the cart and the invoice. The platform models money on a real double-entry ledger rather than mutating a single “balance” field.

What's built in

Plans, subscriptions, invoices, usage-based charges and entitlements, backed by the ledger — with dunning (retrying and chasing failed payments), reconciliation, and refunds as first-class operations rather than manual database edits.

Real payment processing

Razorpay and Stripe are both wired in for real payment collection. Card and payment details never touch MergeMind's own servers — they're handled directly by the PCI-compliant processor. See Security & Trust for what that means for your compliance posture.

Subscriptions

Plans and subscription lifecycles (create, upgrade, downgrade, cancel, renew) are handled by the same billing service every vertical built on the platform uses — including MergeMind Commerce's own subscription stores, proven live in Case Study #001.