Rails
Certified TCIB connectivity, as a service
Encrypted links to the switch on both production and disaster-recovery paths, monitored 24/7/365. The scheme never closes, and neither do we.
One integration. Sixteen countries. Money that moves in seconds.
PayNable connects banks, mobile money operators and fintechs to TCIB, the SADC real-time cross-border payment scheme. We build, certify and run the ISO 20022 rails, so you can open new payment corridors without rebuilding your core.
- SADC markets on one scheme
- 16
- SADC markets on one scheme
- clearing, every day of the year
- 24/7
- clearing, every day of the year
- API to integrate, not sixteen
- 1
- API to integrate, not sixteen
ZAR 4,250 → MZN 15,088
Johannesburg → Maputo · cleared in 2.1s
16 SADC member statesReal-time clearing, 24/7/365ISO 20022 nativepacs.008 credit transferspacs.004 returnsZAR settlement via SADC-RTGSBanks · mobile money · fintechsProduction + DR redundancy16 SADC member statesReal-time clearing, 24/7/365ISO 20022 nativepacs.008 credit transferspacs.004 returnsZAR settlement via SADC-RTGSBanks · mobile money · fintechsProduction + DR redundancy
Why TCIB
A payment from Johannesburg to Maputo shouldn't detour via New York.
Most cross-border payments in Southern Africa still hop between correspondent banks, often through dollar clearing, losing time and value at every stop. TCIB clears them inside the region, in real time, on one set of rules.
Illustrative R5,000 transfer. Correspondent fees vary by bank and route; TCIB fees are disclosed before the customer sends.
- Time to beneficiary
- 2–5 days
- Seconds
- Hops
- 3–5 intermediaries
- 1 regional switch
- Fees
- Deducted in transit
- Disclosed upfront
- Availability
- Banking hours
- 24/7/365
- Data
- MT messages, lossy data
- ISO 20022, rich data
How it works
Follow one payment, end to end.
Your bank sends simple API calls. PayNable does the ISO 20022, the screening, the connectivity to the regional switch, and the reconciliation afterwards. Pick a corridor and watch every hop.
Sender bank
Johannesburg
PayNable gateway
ISO 20022 · screening
TCIB switch
Regional clearing
Receiving gateway
PayNable or direct
Beneficiary bank
Maputo
Step 1 of 6
Customer hits send
Thandi Mokoena sends ZAR 5,000.00 to Lucas Mabunda in Maputo. Your core banking system makes one call to the PayNable API — no ISO 20022 work on your side.
Indicative rate 1 ZAR = 3.5500 MZN · sample data
POST /v1/payments
JSON{"amount": { "value": "5000.00", "currency": "ZAR" },"debtor": { "name": "Thandi Mokoena", "account": "620001234567" },"creditor": {"name": "Lucas Mabunda","country": "MZ","account": "MZ00 0001 2345 6789"},"reference": "Family support"}
The platform
We own the rails. You own the customer.
Everything between your core banking system and the regional switch, built once, certified once, and run by us around the clock.
Gateway
Speak your format. Send ISO 20022.
We map what your core already produces to schema-valid pacs.008 credit transfers and pacs.004 returns, and translate inbound payments back.
JSON / REST
ISO 20022
Comply
Screened before it moves
Sanctions and AML screening hooks, plus completeness checks on the originator and beneficiary data regulators expect on every cross-border payment.
E2E7Q4K91XAZAR 5,000.00
- Sanctions lists
- AML risk score
- Originator data (FATF R.16)
- Beneficiary data
- Duplicate detection
Settle
Every cycle, reconciled
Clearing totals, settlement obligations and returns matched automatically, per currency. Know your position before your treasury asks.
Net position · this cycle Reconciled
ZAR
MZN
NAD
BWP
ZMW
TZS
MWK
Console
One view of every corridor
Payments, returns, exceptions and corridor analytics in one dashboard, with full search by end-to-end ID.
Cleared today
12,418
Median clear
2.3s
Exceptions
3
- ZAR → MZN5,000.00Accepted
- NAD → BWP48,000.00Accepted
- ZAR → ZWG1,250.00Returned · pacs.004
Sample console data
Security & trust
Bank-grade by default. Auditable by design.
Cross-border payments carry regulatory weight on both sides of the border. Every layer of PayNable is built so your risk, compliance and audit teams can sign off with confidence.
- ✓ Schema valid
- ✓ Sanctions clear
- ✓ AML scored
- ✓ Travel-rule data complete
- ✓ Signed & logged
Private, encrypted links
Site-to-site IPSec tunnels to the switch, with separate production and disaster-recovery paths. Payment traffic never touches the open internet.
Validated before it leaves
Every message is checked against ISO 20022 schemas and scheme rules inside our perimeter, so malformed payments fail fast and never reach the switch.
Screened in both directions
Sanctions, AML and originator/beneficiary data checks on every payment, outbound and inbound, with hooks into your existing compliance tooling.
Traceable end to end
One end-to-end ID follows each payment and any return across every hop, with tamper-evident logs for audit and dispute resolution.
Always on
Real-time clearing is a 24/7/365 obligation. We run active monitoring and tested failover so your customers never see a closed sign.
Developers
You send JSON. We speak ISO 20022.
Your engineers integrate a clean REST API once. We own the message mapping, scheme rule changes and schema upgrades, so your roadmap isn't held hostage by XML.
POST /v1/payments
your request{"idempotencyKey": "e2e7q4k91xa","amount": { "value": "5000.00", "currency": "ZAR" },"debtor": {"name": "Thandi Mokoena","account": "620001234567"},"creditor": {"name": "Lucas Mabunda","account": "MZ59 0001 0000 0012 3456 7890 1","country": "MZ"},"reference": "Family support"}
pacs.008.001.05
what we send<FIToFICstmrCdtTrf><GrpHdr>…</GrpHdr><CdtTrfTxInf><PmtId><EndToEndId>E2E7Q4K91XA</EndToEndId></PmtId><IntrBkSttlmAmt Ccy="ZAR">5000.00</IntrBkSttlmAmt><Dbtr><Nm>Thandi Mokoena</Nm></Dbtr><DbtrAcct><Id><Othr><Id>620001234567</Id></Othr></Id></DbtrAcct><DbtrAgt>…</DbtrAgt><CdtrAgt><FinInstnId><Othr><Id>…</Id></Othr></FinInstnId></CdtrAgt><Cdtr><Nm>Lucas Mabunda</Nm></Cdtr><CdtrAcct><Id><IBAN>MZ59000100000012345678901</IBAN></Id></CdtrAcct><RmtInf><Ustrd>Family support</Ustrd></RmtInf></CdtTrfTxInf></FIToFICstmrCdtTrf>
A sandbox with simulated participants
Send and receive against simulated SADC banks before you touch scheme test environments.
Webhooks for every state change
Accepted, rejected, returned, settled: subscribe once and keep your core in sync.
Returns as first-class objects
Raise or receive a pacs.004 return with one call, linked to the original payment automatically.
New payment streams
Every corridor you open is a new line of revenue.
TCIB is open to banks and non-banks alike. Whatever kind of institution you are, PayNable gets you onto the rails and earning from regional flows.
Turn cross-border into a product line
- Launch outbound and inbound SADC transfers in your app and branches
- Win SME trade and payroll flows that currently leak to fintechs
- Earn transaction fees and FX margin on every corridor you open
Onboarding
From signed to live. We carry the load.
Joining a regional payment scheme means applications, approvals, connectivity, message certification and round-the-clock operations. We run that programme with you, and keep running it after go-live.
- 1
Apply and approve
Scheme application, participation agreement and notification to your central bank.
PayNable
- Prepare the application pack
- Coordinate with the scheme operator
- Track every approval to closure
You
- Sign the agreements
- Supply licences and regulatory approvals
- 2
Register
Your institution is registered on the scheme and issued its participant identifier.
PayNable
- Complete registration and master data
- Set up your corridors and currencies
You
- Confirm settlement arrangements: your own account or a sponsoring bank
- 3
Connect and integrate
Secure connectivity to the switch and one integration into your core.
PayNable
- Provision redundant encrypted links
- Map your core banking formats to ISO 20022
- Wire up reconciliation and reporting
You
- Integrate the PayNable API once
- 4
Test and certify
Run the operator's certification packs end to end before go-live.
PayNable
- Payments, returns and status flows
- Reconciliation and settlement checks
- Throughput and disaster-recovery tests
You
- User acceptance sign-off
- 5
Go live and grow
Switch on corridors and add markets as the scheme grows.
PayNable
- 24/7 operations and monitoring
- Scheme rule and schema change management
- New currencies and corridors on request
You
- Launch to customers and start earning
Where we're going
Africa first. Then every rail.
We build the rails, own them and run them. Once a market is live, the same gateway, compliance stack and operations team carry into the next one.
Pricing
Priced like infrastructure. You pay when money moves.
A one-off fee to integrate and certify, then a small fee per transaction. No per-seat licences, no surprise change requests when the scheme updates its rules.
Connect
Banks, mobile money operators and MTOs joining TCIB
Custom
Quoted per institution and corridor
- One-off ISO 20022 integration and certification fee
- Per-transaction pricing, tiered by volume
- Rails, Gateway, Comply and Console included
- 24/7 incident line
Scale
High-volume participants, PSPs and sponsoring banks
Custom
Quoted per institution and corridor
- Everything in Connect
- Lower per-transaction tiers
- Settlement and reconciliation automation
- Dedicated corridor success manager
- Priority 24/7 support
Sovereign
Central banks, ACHs and national switches
Custom
Quoted per institution and corridor
- National connection programmes
- ISO 20022 readiness for domestic institutions
- White-label gateway
- Data residency options
Let's open your first corridor.
Tell us who you are and where your customers send money. We'll come back with a clear path onto TCIB.
- 1A 30-minute call to understand your corridors and customers
- 2A readiness assessment of your core, compliance and settlement setup
- 3A fixed integration plan and quote, so you know the path to live
PayNable · Midrand, Johannesburg, South Africa · Reg. 2026/795370/07. Company details