Capitec is live
Live keys can link Capitec accounts. The account holder scans a QR code in the Capitec app at every sign-in.
Capitec joins FNB, Standard Bank and Nedbank as a supported bank, subject to maintenance. Live API keys, the dashboard and the hosted link page can link Capitec accounts and fetch their transactions.
What changed
Section titled “What changed”- Link Capitec accounts.
POST /linkacceptsbankId: "capitec"with live keys. The only credential is{ username }: the account number or Online Banking username. - QR code sign-in. Capitec shows a QR code at every sign-in, which the account holder scans in the Capitec app. The hosted link page and the dashboard show it with a countdown. API callers get it on the progress stream (
Accept: application/x-ndjson) as anawaiting_qr_scanevent. - A new code without starting over. A code lasts 60 seconds. When one lapses, the stream sends
qr_expiredwith aretryId.POST /bank-progress/qr-retrywith it, within 15 seconds, shows a new code. - Transactions and balances. Every account on the profile, with balances, and up to two years of transactions.
- New error codes.
approval_not_given,online_banking_disabled,customer_action_requiredandqr_handoff_requiredcome with a message you can show the account holder.
Do I need to change anything?
Section titled “Do I need to change anything?”To link Capitec through your own UI, ask for the progress stream and show the QR code. See Capitec. The hosted link page needs no changes.
The old Capitec one-time PIN flow (mfa_required and POST /link/otp) is gone. It never worked with live keys. In the sandbox, Capitec now links in one step like the other banks.
Capitec can’t run unattended, so Pulses and scheduled syncs on a Capitec account are refused with qr_handoff_required. Nothing is charged. Billing top-ups stay FNB only.