Alviyora Invoicing runs the whole billing cycle — invoices, recurring subscriptions, split billing, payment links and debit orders — behind one API and one clean console. Money settles directly with your payment provider. It never passes through us.
No card required · ZAR · Built in South Africa
Built as an engine first, so the same system bills ten customers or ten thousand without changing shape.
Sequential numbering per organisation, line items snapshotted at issue, and a hosted invoice page your customer can open years later.
Products, prices and subscriptions with trials and a billing anchor day. The monthly run raises invoices on schedule, once, idempotently.
One customer, several payers, percentages that must sum to exactly 100. Each payer gets their own invoice — which is what makes per-payer chasing possible.
Branded pay pages per invoice, card payments through Paystack, and DebiCheck mandates for recurring collection.
Every movement is an append-only row. Mistakes are corrected by contra entries, never by editing history, so the balance always reconciles.
A REST API keyed per organisation, and signed webhooks delivered through an outbox so an unreachable receiver can never lose an event.
Sign up, get your API key, and add your payment provider credentials. They are encrypted at rest before they touch the database.
Create customers and payers, then issue invoices from the console or push them over the API. Subscriptions raise theirs automatically.
Send a payment link, run a debit order batch, or record an EFT by reference. The ledger updates and your webhook fires.
Not policy promises — properties of the schema and the code paths.
Payments settle directly from the provider into your own bank account. We are never in the flow of funds.
Card and bank details are never stored — not even simulated ones. The schema has nowhere to put them; only the provider's opaque token and a last-four.
Provider keys are encrypted with a master key held separately from the application secret, and are never echoed back by the API.
Every API request carries an organisation's own key and every query is scoped to it. There is no code path that returns another tenant's row.
Every payload is signed with a per-endpoint secret, so your receiver can prove the event came from us.
Ledger entries record the actual person who made them, including when support acts on your behalf.
No. You connect your own payment provider account, and funds settle directly into your bank account. We handle the invoicing and the record-keeping, never the float.
Paystack for card payments and Netcash DebiCheck for debit orders, with a simulator for testing. The adapter layer means new providers plug in without changing your integration.
Yes. The console does everything the API does — customers, invoices, payments, subscriptions, payment links and gateway setup. The API is there when you want to automate it.
South African Rand today. Every amount carries its currency in the schema, so more can be added without rewriting the ledger.
Yes, and it is a first-class concept rather than a workaround. Assign percentages that sum to 100, and each payer receives their own invoice for their share.
Your invoices and ledger are yours. Everything is reachable over the API, so you can export the full history at any time.
Create an organisation and get your API key in under a minute.