Recurring payments with LiqPay in Laravel: automate subscription billing

If you bill customers every month, manual invoicing leaks revenue. Cards expire, renewals get missed, and someone on your team chases payments that should collect themselves. LiqPay recurring tokens fix that — and Laravel makes the integration clean.

Here is the business case first. Automated recurring billing lifts collected revenue, shortens the gap between a renewal date and cash in the account, and removes hours of finance work each week. For a subscription product with 500 active members, recovering even 3% of failed renewals pays for the integration in the first month.

How the LiqPay recurring flow works
LiqPay supports subscription charges through a saved card token. On the first payment the customer authorizes the card; LiqPay returns a token tied to that mandate. After that, your Laravel app charges the token on each cycle with a server-to-server request — no checkout page, no customer action.

What we build in Laravel
- A billing service that signs every LiqPay request with your private key and verifies the signature on each callback, so no forged status can mark an invoice paid.
- An Eloquent subscription model with states: active, past_due, canceled. State changes are driven by LiqPay callbacks, not guesswork.
- A scheduled command (php artisan schedule) that finds subscriptions due today and dispatches a charge job per subscriber onto a queue, so 2,000 renewals never block a web request.
- Dunning logic: on a failed charge we retry on a schedule, email the customer, and move the record to past_due before cancellation.
- A reconciliation report that matches LiqPay settlements against your invoices, so finance closes the month in minutes.

Reliability details that matter
Every charge job is idempotent, keyed by subscription and billing period, so a queue retry never double-charges a card. Callbacks are logged raw before processing, which means a disputed payment always has an audit trail. We test the failure paths — declined card, expired token, network timeout — not just the happy path.

This same pattern works for memberships, SaaS plans, donations, and B2B retainers. We can connect it to your existing Laravel app or build the billing layer from scratch, plus wire Nova Poshta or Ukrposhta if physical fulfillment follows the charge.

Want predictable recurring revenue without the manual chase? Talk to MaxiMoruM about a LiqPay billing integration: https://maximorum.com/