Use cases
The common shape is the same: the calls are already happening, and nothing downstream can turn them into a number anyone will sign.
What is in the way
An estate of services other institutions already consume informally, with no record of who called what and no way to charge for it.
What Wanda does about it
Metering per consumer, quotas per plan, and statements that reconcile in Pula. Self-hosted in-country, so residency is a deployment fact rather than a contractual promise.
What is in the way
Open banking and partner APIs that are already live, priced by negotiation rather than by usage, and reconciled by spreadsheet.
What Wanda does about it
An effective-dated price book, tax computed per line, immutable statements and credit notes as the only correction. The audit trail is the product.
What is in the way
Per-call products where the unit of sale is the call, and where a disputed invoice is a disputed count.
What Wanda does about it
Idempotent metering with producer-assigned identity, so a retried call is not a second charge, and re-runnable rating so a disputed figure can be recomputed rather than argued.
What is in the way
A gateway that handles traffic well and knows nothing about money, plans or statements.
What Wanda does about it
Wanda decides and meters behind what you already run. The gateway keeps its job and the commercial layer stops being a spreadsheet.
Pula is a first class currency here rather than a locale setting. Tax follows the rate in force on the day, and splits a line when a statutory rate changes mid period. The platform deploys in-country, which for a bank or a ministry is a requirement rather than a preference. Wanda runs BotsKYC, the identity and compliance platform in the same group, so the first estate it bills is one we are accountable for ourselves.
If it is none of them, that is worth a conversation too. The shape that does not fit is usually the one that teaches us something.