Core banking · Bank-grade scope
The core-banking platform with an audit chain for a spine.
Bank-grade scope, fintech-native VAS, and an embedded accounting substrate your auditors will actually trust.
Four things you can check rather than believe
Every claim on this site is a mechanism with an artefact behind it. These are the four worth attacking first.
- Your auditor cannot be told a different number than your regulator
- Six reporting frameworks are projections of ONE fact set. A framework is a view, not a second ledger, so two frameworks cannot disagree about what happened.
How this works - A rewritten history is visible, not deniable
- Audit and ledger rows each commit a SHA-256 over their predecessor. An independent verifier recomputes from origin and raises a fork as a blocking alarm.
How this works - One tenant cannot read another, even by mistake
- Isolation is FORCED row-level security in PostgreSQL, not application code remembering to filter. A query with no tenant context returns nothing, not everything.
How this works - Money never moves twice on a retry
- Every money POST carries an idempotency key; a replay returns the original outcome marked already-processed. Amounts are integer minor units end to end.
How this works
What the platform is
Seven loan verticals
Unsecured, mortgages, consolidations, vehicles, SME, invoice discounting, trade finance — each a full domain package with IFRS 9 staging and Basel 3.1 capital built in.
Embedded accounting
Every rand movement writes a double-entry fact in the same transaction. Your AFS traces to origin facts over a signed hash chain — in six reporting frameworks.
ISO 20022 native
pain, pacs, camt and admi are the internal message shapes, not a translation layer. SAMOS, PayShap, SADC RTGS, SWIFT MT+MX, DebiCheck, card and QR.
Wallets and VAS
Multi-currency wallets, airtime to insurance premiums, with VAS margin on the same audited ledger as loan interest.
Regulator-inspectable
A SARB PA inspector walks from any AFS line to the origin event, the workflow, the identity and the mandate — cryptographically tamper-evident.
Payment rails, natively
ISO 20022 is the internal shape, so a rail is an adapter at the edge rather than a translation layer through the middle. Status is stated per rail — nothing here is aspirational.
| Rail | Message shape | Status |
|---|---|---|
| SAMOS (SARB RTGS) | pacs.008 / pacs.002 / camt.054 | ✓ Live |
| PayShap (rapid payments) | Proxy resolution, request-to-pay | ✓ Live |
| DebiCheck | Authenticated mandates, TT1 / TT2 / TT3 | ✓ Live |
| SADC-RTGS | Cross-border ZAR settlement | ✓ Live |
| SWIFT MT + MX | MT103 / MT202 with MX co-existence | ◐ In build |
| Card (issuing and acquiring) | ISO 8583 bridge onto the ISO 20022 spine | ◐ In build |
| QR (interoperable) | EMVCo payload parse and emit | ✓ Live |
| EFT (collections and payouts) | Batch origination with camt.053 reconciliation | ✓ Live |
How the payments layer is built
Six reporting frameworks, one set of facts
The same origin facts render every framework. A framework is a projection, not a second ledger — which is why the numbers agree.
IFRS (full)
Primary statements, notes, IFRS 9 ECL staging
IFRS for SMEs
Reduced-disclosure variant off the same facts
SA GAAP-legacy comparatives
Restatement bridge for historical series
SARB BA returns
BA 100/120/125/200/900 mappings
Tax (SA income tax + VAT)
Permanent and temporary difference tracking
Management (internal)
Segment and product-line P&L
How the accounting substrate works
Where to next
Wynk Systems is a bank-grade core-banking platform. Registered in South Africa.
This site is informational: nothing on it constitutes an offer, a quotation, or credit advice.