How Stitch Works
The technical rationale behind multi-source payment aggregation, built as a proof-of-concept for Zap by Paystack.
Why Stitch?
Have you ever wanted to transfer an amount, but you didn't have the complete amount in any of your banks? But you now started sending from one bank to another just to complete the balance...

Stitch helps in the sense that you don't have to do this manually, it can help you just pull your funds together seamlessly.
The Buffer Pattern
At the heart of Stitch is a Paystack Virtual Account that acts as an escrow buffer. It decouples the collection of funds from the disbursement of funds:
- Collection: Multiple small, transfers from the user's linked banks flow into the virtual account.
- Disbursement: Once the target amount is fully collected, a single clean transfer is sent to the recipient.
This staging-area approach ensures the merchant only receives a complete payment — never partial amounts that would corrupt their reconciliation ledger.
Why Paystack?
Paystack is uniquely positioned to solve this problem beautifully because of two massive advantages:
- They own Zap: An app that already lets you send money from any of your bank accounts.
- They own Virtual Accounts: The exact buffer infrastructure needed to make Stitch work natively exists within their systems. It's a plug-and-play addition to their ecosystem.
Why One Alert Matters
From the merchant's perspective, receiving three small alerts instead of one clean ₦5,000 alert creates reconciliation chaos. Their POS or accounting system expects one transaction per purchase — not a scattered collection of micro-transfers.
Stitch solves this by ensuring the merchant's experience is indistinguishable from a normal, single-source payment. They receive one alert, one line item, one reference number.