How PAMO works
Payment orchestration and merchant operations across existing payment rails.
Merchant sets the amount. Customer chooses how to pay. Existing providers move the money. PAMO brings it together.
Zimbabwe already has the railway lines. EcoCash is one rail. InnBucks is another. Banks and card networks operate others. PAMO does not build another railway and ask consumers to move onto it — PAMO builds the interchange that connects those existing rails around the merchant.
Different payment rails underneath. One merchant experience on top.
The transaction journey
Merchant creates payment request
Amount, currency, description
PAMO
Creates a unique dynamic payment request and QR
Customer chooses payment rail
The customer only picks how to pay
EcoCash / InnBucks / Bank / Card
Existing participating provider (simulated here)
Payment provider processes transaction
The provider moves the money
PAMO receives confirmation
Normalised into one record
Merchant receives confirmation + transaction record
One consistent ledger
The problem is fragmentation, not access
A shop can take US$625 through EcoCash, US$375 through InnBucks, US$500 through bank payments and US$250 through cards in a single day. That is US$1,750 of digital sales spread across separate systems, histories, settlement processes and fee structures.
- EcoCashMobile money rail
- InnBucksMobile money rail
- BankBank transfer rail
- CardCard network rail
What PAMO is not
PAMO is not
- A new digital wallet
- A bank or mobile-money provider
- A replacement for EcoCash, InnBucks or banks
- A place to hold a PAMO balance
Customers never
- Deposit or top up into PAMO
- Transfer funds into PAMO before paying
- Leave their existing provider