Accounting software example
Scroll inside the preview to explore. The fork adds application sign-in, persistent books and optional sandbox imports. Tax views are illustrative working papers, not SARS filing tools.
Choose how the feed connects.
Most use cases can start with the direct API. Organisation verification is not required for direct v1 or v2 use.
Direct API · v1
Quick integrationSaved login: bank credentials are encrypted and stored under Banklink-controlled keys.
No saved login: use saveCredentials: false and supply fresh credentials for each sync. This does not disable transaction storage.
Recurring feeds into your ledger, with API responses, Pulses or webhooks.
v1 API reference ↗Node.js SDK · v2
Your keys, your resultsOne-off: syncOnce uses a temporary key and saves no bank login or transaction history.
Recurring: saved logins are encrypted under your customer key. Your app approves each job and decrypts the results.
Control each client fetch from your job runner and keep results in your system.
v2 SDK guide ↗Hosted link or access request
Banklink supplies the pagesLink requests save an encrypted bank login for later fetches. Access requests fetch once without keeping credentials or transactions.
Organisation verification is required only for live hosted requests. Sandbox hosted requests need no verification.
Send a client a consent and bank-login page instead of building one.
Hosted requests ↗Sign in with BankLink
In developmentA separate Connect flow, not the same as a hosted bank-login page. This prototype is not enabled in these starters and is not a production integration option yet.
An account-selection and permission handoff for people who already use BankLink.
What would this cost in your product?
50 clients × 1 profile × 22 refreshes
1 100 successful fetches / month
Lowest published monthly option
Growth · R19,98 per client / month
git clone https://github.com/banklinkorg/banklink-examples.git
cd banklink-examples/accounting
node scripts/setup.mjs
docker compose up --build