These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Neobank Backend
- Integrations
Integrations
Connect provider outcomes and account data to treasury records.
- Neobank Backend
- Banking provider
- Account data source
- Movement source
- Document source
Systems to connect
- Banking provider. Supply provider instruction identifiers, confirmations, settlements and corrections for submitted instructions.
- Account data source. Supply dated ledger and available balance snapshots for each provider-held financial account.
- Movement source. Supply stable event identifiers, occurrence dates, amounts and account references for reconciliation.
- Document source. Attach supporting files to the parent instruction with an appropriate visibility setting.
How connections are governed
Map each provider account identifier to the corresponding financial account. Preserve the source event identifier and event date when importing evidence or movements. A repeated operation uses its existing operation key; the team checks the recorded effect before any retry. Choose who can verify provider evidence and who investigates mismatches. Rehearse a delayed confirmation and a duplicate movement during implementation.
Set up Neobank Backend your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.