Bill by subscription, by usage, or by invoice

If your team builds invoices in a spreadsheet or a word processor, someone will have to format each line item, add up the totals, note which invoices they send, and follow up on each unpaid one by hand. That person's workload will grow with every client that you add.

Your team can create an invoice with line items, discounts, tax, and your logo. Wallet generates the PDF and sends it by email or through Channels with a payment link attached. The billing dashboard shows which invoices are paid, pending, overdue, or partly paid. When an invoice passes its due date, Wallet starts a reminder sequence for it.

To bill by API calls, storage, transaction volume, or compute time, you will need a metering system that adds up each customer's usage, applies tiered prices, and produces an accurate invoice at the end of each cycle. If your engineers build that system themselves, they will have to write and maintain every one of those parts.

You can define a usage meter for any metric that you track, such as API calls, gigabytes stored, messages sent, or transactions processed. Wallet adds up each customer's usage across the billing period and applies your tiered prices when it creates the invoice. Customers can check their current usage and projected cost before Wallet sends that invoice.

A business with customers across Africa, Europe, and North America will need to bill each customer in their local currency through a payment processor that serves their region. If that business keeps a separate billing system for each region, its finance team will have to set up and reconcile each system on its own.

When you bill a customer in their local currency, Wallet sends the payment through the processor for your billing entity's jurisdiction. An invoice to a customer in Ghana and an invoice to a customer in the UK both appear in the same Wallet dashboard, with the same reports and the same reconciliation steps.