Subscriptions & plans
Define plans, amounts, and intervals once. Apply them to customers without rebuilding logic for each billing cycle.
Industries / Software
Your customers sign up once, but the relationship keeps moving. Plan payment, billing, and customer context around the entire lifecycle.
Signup
Choose the service
First payment
Connect access to collection
Ongoing service
Keep billing context visible
The recurring layer
Recurring revenue lives or dies on the connection between the plan, the payment, and the customer. Zapi keeps all three tied together across every cycle.
Define plans, amounts, and intervals once. Apply them to customers without rebuilding logic for each billing cycle.
Charge on the cadence that matches your product — monthly, annual, or a custom schedule per customer.
Failed charges retry on a sensible schedule and notify the customer, recovering revenue without a person chasing each decline.
Vary the charge with what the customer actually consumed, so the plan flexes to real usage instead of a flat guess.
Get notified the moment a subscription changes, a payment succeeds, or a renewal is due, so your product reacts instantly.
Bill customers in the currency they expect, with conversion handled at the point of each recurring charge.
Build for the long term
A subscription is not a single charge — it is a relationship that moves through stages. Plan how each stage connects to the payment and the customer record.
01 / LIFECYCLE
Decide how ongoing service and payment collection relate before a customer starts. The plan, the interval, and the first charge are designed together.
02 / LIFECYCLE
Connect payments, invoices, and the customer relationship in your operations, so a renewal never arrives without the history behind it.
03 / LIFECYCLE
Track active subscriptions, churn, and recurring revenue alongside one-off payments, so your team sees the full picture in one place.
Built for software businesses
From a single-tier app to a usage-based platform, the same lifecycle adapts to how your software actually earns.
Charge teams for seats and tiers, with upgrades, downgrades, and proration handled cleanly across cycles.
Meter API calls, compute, or storage and bill on real usage without building a metering system from scratch.
Combine a base subscription with usage overages, so customers pay for the capacity they actually consume.
Offer monthly and annual plans side by side, with trials that convert to paid without a manual handoff.
Good to know
What software teams ask before they put recurring revenue on Zapi.
Yes. A trial starts a customer on a plan without charging, and when the trial ends the first payment is collected automatically. Access and billing stay connected, so there is no manual step between the trial and the paid subscription.
Zapi retries failed charges on an automatic dunning schedule and notifies the customer, so you recover revenue without manually chasing each decline. You stay informed about which subscriptions need attention and can pause access when appropriate.
Yes. You can combine a flat subscription with usage-based overages, or bill entirely on metered consumption. The plan flexes to what the customer actually used each cycle, with the metering tied to the same payment record.
Yes. Recurring charges and one-off payments live in the same records, connected to the same customer profile, so your team sees the full revenue picture — renewals, upgrades, and incidental purchases — in one place.
Related products
The recurring layer that runs every subscription cycle.
The payment API that collects every recurring charge.
Keep subscriptions, plans, and history on one profile.
Bill a customer once with an invoice and a payment page.
Collect the first payment that starts a subscription.
Track recurring revenue, churn, and active subscriptions.
Start building with Zapi
One integration for payments, payouts, and virtual accounts. Start in test mode and grow from there.