Co-branded Wallet App

The Co-branded Wallet App is a turnkey wallet experience: EFT Corporation builds and operates the app; you brand it, distribute it under your name, and sign up customers. It's the fastest path to having a QR-payment wallet in market without committing to a full app build.

If you want to embed Scan to Pay flows inside an app you already own, see Converged Wallet App instead. If you have engineers and want to build your own UI against the Remote API, see Remote API overview.

What you get

Component	Detail
Native apps	iOS and Android builds, distributed through your developer accounts on the App Store and Google Play
Your brand	App icon, splash screen, primary colour palette, app name — applied throughout the UI
Scan to Pay engine	QR scanning, merchant lookup, card vault, AMT / 3DS authentication, transaction history — all built in
Card provisioning	Customers add their bank cards (any South African issuer) via the in-app flow
VAS	Optional airtime, data, electricity, bill payments — configured per your product preferences
Customer support routing	In-app help, FAQ, contact form pointing at your support team
Push notifications	Transaction receipts, balance alerts, marketing (optional)
Analytics	Standard usage analytics — installs, MAUs, transaction volume — delivered weekly

Who this is for

You are…	Is co-branded right?
Issuing bank without app engineering capacity	Yes — fastest path to a competitive wallet
Fintech wanting to launch quickly	Yes — focus on customer acquisition, not app development
Bank with an existing app	Probably not — use Converged to embed inside your existing experience
Wallet operator with engineers	Probably not — build with Remote API for full UX control
Acquirer	No — acquirers don't issue wallets; this isn't your product

How it works

   You                          EFT Corporation
   ───                          ───────────────
        │                              │
   provide brand assets                │
   ─────────────────────────────────►  │
   (logo, colours, app name,           │
    Apple/Google dev accounts)         │
                                       │  build branded apps
                                       │  test on sandbox
                                       │
                                       │  publish to your store accounts
                                       │  under your developer identity
        │                              │
   sign up customers                   │
   market the app                      │
        │                              │
   customer downloads, registers,      │
   adds card, scans QR, pays           │
        │                              │
                                       │  runs against Scan to Pay
                                       │  Remote API + Card Provisioning
        │                              │
   monthly settlement + reporting      │
   ◄─────────────────────────────────  │

The split is clean: you own customer acquisition and brand. EFT Corporation owns the technology and operations.

What's white-labelled vs fixed

White-labelled:

App name, icon, splash screen
Primary colour palette (within accessibility constraints)
Help / support contact details
Card art (via Send Brand Indicator)
Push notification copy
T&Cs / privacy policy (your legal team's)
Available VAS products (configured by Operations)

Fixed (for platform consistency and compliance):

Core payment flows — QR scanning, card entry, AMT / 3DS UI
PIN entry screen (PinSecLib requires its own UI for PCI compliance)
Scan to Pay attribution mark, visible on the payment confirmation screen
Security flows — auth, lockout, biometric unlock
Webhook / acquirer integration (operationally invisible to you)

What you provide

To kick off a co-branded app, you'll need to provide:

Item	Format
App name	Text, 30 chars max
App icon	PNG, 1024×1024, no transparency
Splash screen	PNG, 3 sizes (1x / 2x / 3x), no transparency
Primary colour	Hex code (we'll also need a contrasting secondary)
Brand wordmark	SVG and high-res PNG
Apple Developer account	Your team ID — we'll add EFT Corp engineers as collaborators
Google Play Console account	Same — your team adds us as a release manager
Support email / phone	Where in-app help routes
Privacy policy URL	Required by App Store and Play Store
T&Cs URL	Surfaced on first launch

A standard onboarding takes 6-8 weeks from brand sign-off to first store submission.

What you do operationally

Once the app is live, your day-to-day responsibilities are:

Marketing the app — customer acquisition, installs, sign-up
Tier-1 customer support — answering "how do I add a card", "where's my transaction" via your support channel
Brand and content updates — colour changes, copy changes, marketing campaigns
Reviewing analytics — installs, transactions, drop-off
Settlement reconciliation — matching the platform's settlement reports against your books

EFT Corporation handles:

App engineering — bug fixes, OS upgrades, new platform features
Platform operations — uptime, monitoring, incident response
Tier-2 / tier-3 support — anything your tier-1 escalates that's platform-related
Compliance — PCI DSS, PSD2 (where applicable), card-scheme rules
Card on-boarding pipeline — adding new issuers, BIN rules, scheme updates

Pricing model

Co-branded wallet pricing is bespoke and depends on:

Expected transaction volume
Whether you want VAS revenue share
Geographic scope (SA-only vs. cross-border)
Brand and customisation depth

Talk to your account manager or [email protected] for a quote.

Limits to be aware of

Constraint	Detail
No code customisation	You can't ask for custom features beyond the white-label scope. If you need bespoke flows, use Converged or Remote API.
One brand per app	Each branded app is a single brand. To run multiple brands, you'd need multiple app submissions.
South Africa only	The current platform serves South African issuers and merchants. Cross-border roadmap is on request.
EFT Corp owns the codebase	You don't get source code. The trade-off for low integration cost.

Migrating to deeper integration

If you launch with Co-branded and later want to move to Converged or a Remote-API build:

The platform-side data (cards, transaction history, MSISDN profiles) migrates automatically — customers keep their wallet across the transition.
You'll need to publish a new app or update the existing one. Customers re-authenticate.
We help with the migration plan; expect 3-6 months for a Converged migration, 6-12 months for a from-scratch Remote-API build.

What's next

Embed Scan to Pay inside an existing app → Converged Wallet App
Build your own UI against the API → Remote API overview
What the platform's actually doing under the hood → Purchase flow
How card art is configured → Card provisioning
Get a quote → [email protected]