Subscriptions and recurring billing inside your system
We build the part of your system that bills subscriptions: plans, cycles, retries when a payment fails, and access granted or suspended according to billing status.

Who it's for
For companies that sell subscriptions or monthly plans and track billing and access in spreadsheets.
What it solves
- A payment fails, but the customer keeps access because nobody noticed.
- The customer pays late and stays locked out until someone unlocks the account by hand.
- A plan change mid-cycle turns into a pro-rata calculation in a spreadsheet.
- Card, boleto and Pix payments arrive by different routes, each tracked separately.
What we do
- Plans and cycles
- Price, billing period, trial, plan changes and cancellation, with pro-rata amounts calculated by the system.
- Billing through your PSP
- Each cycle raises a charge in the chosen method, card, boleto or Pix, through your gateway or bank.
- Declined payments
- Retries and customer reminders follow the dunning schedule your company sets.
- Access tied to billing
- Subscription status decides access: paid unlocks, overdue beyond the grace period suspends, a later payment reactivates.
- Pix Automático
- If your PSP offers the feature, the payer's authorisation and the charges join the same cycle.
- Cards without storing the number
- The card is tokenised at the gateway; your system keeps only the reference.
What you get
- A subscription module connected to your PSP or gateway, in production
- A history for each subscription: charges, retries, plan changes and cancellations
- A report of declined charges and suspended subscriptions
- Automated tests for renewal, failure, plan change and cancellation
- Documentation of the billing rules as implemented
How we do it
Mapping
Plans, access rules, payment methods and what happens when a charge fails.
PSP review
We check what your gateway or bank offers for recurring billing.
Development
Cycles, charges, retries and access, tested in the sandbox.
Subscription migration
Active subscriptions move into the new system without anyone being charged twice.
Follow-up
Checking the first billing cycles and tuning the dunning schedule.
Technology examples
- API Pix
- OpenAPI
- Webhooks
- PostgreSQL
- RabbitMQ
In Brazil, we handle
- Pix
- The Central Bank of Brazil's instant payment system.
Related services
FAQ
Who decides how many times to retry a charge?
Your company. The dunning schedule and the grace period before suspension are business decisions. We implement the rules and make them easy to change.
Can we use Pix Automático?
It depends on your PSP offering the feature on your account. If it does, the payer's authorisation and the charges join the subscription cycle; the Pix connection itself is covered under Pix integration.
We already use a subscription platform. Would you replace it?
Not necessarily. We can connect your system to it, or bring recurring billing inside your system when the platform limits your rules. That choice comes after the mapping.
What if a customer pays outside the cycle, with a one-off Pix?
The payment has to be matched to the right subscription. Payment reconciliation finds it and marks the open cycle as paid.
Write to Balkan
Talk to us about your project