Plans & pricing
Define plans, amounts, and intervals once. Apply them to customers without rebuilding logic for each cycle.
Revenue / Billing
Revenue is a relationship, not a one-time event.
Connect the recurring payment conversation to your customer, their plan, and the operations behind every billing cycle.
Customer billingSAMPLE
Current cycle
Monthly service
ETB 1,000 / month
Billing context connected to customer
The recurring layer
Everything a recurring relationship needs.
Billing is more than a scheduled charge. Zapi keeps the plan, the payment, and the customer context connected across every cycle.
Billing cycles
Charge on the cadence that matches your business — monthly, annual, or a custom schedule per customer.
Proration
Upgrade, downgrade, or mid-cycle changes are calculated fairly, so the customer pays only for what they use.
Automated retries
Failed charges retry on a sensible schedule, recovering revenue without a person chasing each decline.
Customer notifications
Keep customers informed about upcoming charges, renewals, and issues before they become support tickets.
Revenue analytics
See active subscriptions, churn, and recurring revenue alongside your one-off payment activity.
The lifecycle
Keep the whole relationship in view.
Ongoing revenue introduces more questions than a single payment. Plan how each answer connects to the customer experience.
01 / CUSTOMER LIFECYCLE
Plan
What is the customer paying for, and when?
02 / CUSTOMER LIFECYCLE
Collect
How does a payment connect to the active billing cycle?
03 / CUSTOMER LIFECYCLE
Understand
What does your team need to know when the relationship changes?
Built for recurring revenue
One billing model, many kinds of business.
From software to services, the same lifecycle adapts to how your revenue actually recurs.
SaaS subscriptions
Charge for access on a recurring plan, with upgrades and downgrades handled cleanly.
Memberships
Renew memberships on a schedule and keep status connected to payment outcomes.
Retainers
Bill clients for ongoing service and tie each cycle to the work delivered.
Usage-based
Vary the charge with usage and let the plan flex to what the customer actually consumed.
Good to know
Billing, explained.
What teams ask before they put recurring revenue on Zapi.
Yes. You can bill monthly, annually, or on a custom cadence per customer. Each subscription carries its own plan, amount, and interval, so your billing follows your business model rather than the other way around.
Zapi retries failed charges on an automatic schedule and notifies the customer, so you recover revenue without manually chasing each decline. You stay informed about which subscriptions need attention.
Mid-cycle changes are prorated automatically. The customer pays only for what they use, and the next cycle reflects the new plan — no spreadsheets, no manual reconciliation.
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 in one place.
Related products
Explore more of Zapi.
Payments
The payment API that collects every recurring charge.
Invoicing
Bill a customer once with an invoice and a payment page.
Checkout
Collect the first payment that starts a subscription.
Payment Links
Send a one-off charge alongside a recurring relationship.
Customers
Keep subscriptions, plans, and history on one profile.
Reporting
Track recurring revenue, churn, and active subscriptions.
Start building with Zapi
Build what moves your business forward.
One integration for payments, payouts, and virtual accounts. Start in test mode and grow from there.