Connect payments, verification, billing and transactions in one platform.
Most payment problems are not payment problems. They are reconciliation problems — three systems holding three versions of the same transaction. ScanPay keeps one record and lets every service read from it.
- Transaction
- SPV-8F2A41C9
- Origin
- Website checkout
- Collection
- Complete
- Verification
- Verified
- Billing entry
- Posted
- Webhook delivered
- 200 OK
One reference, read by every service that touched the transaction.
What sits where.
Collection methods on top, the shared transaction layer in the middle, business workflows underneath.
One transaction, end to end.
Initiated
A payment is created by a checkout, an app, or a billing run.
Processed
The payment moves through the gateway and the method used to collect it.
Verified
Details are confirmed and the shared transaction record is updated.
Distributed
Webhooks notify your systems, and billing or escrow act on the same record.
One integration, more services over time.
Start with the service you need now. Adding another later does not mean a second integration, a second reconciliation process, or a second source of truth.
- Same authentication across gateway, verification and billing
- Same reference format across every service
- Same webhook contract for every transaction event
// Every service writes to the same transaction
scanpay.webhooks.on("transaction.verified", (e) => {
console.log(e.reference, e.source);
// -> SPV-8F2A41C9 "gateway"
// -> SPB-2E4471DA "billing"
// -> SPE-3C90F72E "escrow"
});
// And the same lookup works for all of them
await scanpay.transactions.get("SPV-8F2A41C9");What the platform makes possible.
Sell and release
Collect the payment, verify it, and release the order from the same record.
Bill and activate
Generate the invoice, take the payment, verify it, update the account.
Hold and complete
Structure a transaction between two parties and complete it on agreed terms.
Reconcile once
Match your ledger against one reference instead of three separate exports.
Transaction infrastructure FAQs.
It is the layer that connects payment collection, payment verification, escrow and billing so they share one API, one set of webhooks and one transaction record.
When collection, verification and billing each keep their own records, reconciliation becomes guesswork. A shared reference means your finance team, your support team and your systems are reading the same thing.
Yes. Businesses commonly start with one service — often M-Pesa collection or payment verification — and connect others later without changing how they integrate.
Yes. A REST API covers initiating payments, requesting verification and querying transaction status, and webhooks push transaction events to your systems as they change.
Continue exploring
Related ScanPay services that connect to this one.
Build on ScanPay transaction infrastructure.
One API, one transaction record, and room to add services as your operation grows.