In your banking app
The invoice is already on the statement.
Your business clients get the merchant's itemised tax invoice on every matched card purchase.
- No slips to keep, photograph or chase.
- Each purchase is itemised, so they see what was bought as well as what was spent.
- Their accountant gets records already matched to the bank statement.
- Later adjustments to an invoice are matched back to the original purchase, so the books stay reconciled.
The screen is a concept: one way a bank might present it. How it works in your app is up to you. Try opening the Brew & Co invoice.
How it works
Alongside your core, never inside it.
Merchant tillstill provider API · OAuth 2.0
Your card transactionsyour API · read-only
Your business client's detailsname · address · VAT numberfor invoices over R5,000
Your core banking: untouched
Match each purchaseHold the invoice record
unmatched items go to reviewAPI · webhooks
Your banking appinvoice on the statement line
Your client's accountingXero · QuickBooks · invoice attached
Out of PCI scope. Built to PCI DSS anyway.
We don't hold card numbers, but we build to the standard regardless. Because security and trust matter.
Built for SARS VAT Modernisation
Structured, itemised invoice data: the direction SARS's e-invoicing consultation points.
Get in touch
Payperwise is in development. We're looking for a bank partner to pilot with.
Tell us about your bank and what you're looking at, and we'll set up a call.