Integrations and source ownership

• Issuing and advising banks. Receive issuance receipts, amendments and presentation decisions through the agreed channel.
• Payment provider. Submit disbursements under a stable key and receive verified disbursement and repayment events.
• Credit bureaus and KYC services. Import reports as application evidence with their reference and expiry.
• General ledger. Export disbursements, allocations and write-offs for accounting.
• Identity provider. Map staff sign-in to team members; removing a leaver’s access must also remove their platform access.

Each connection needs an agreed source of truth, a field mapping, a stable event identifier and a retry policy. A repeated provider event must not create a second disbursement or repayment, and an uncertain outcome must never trigger an automatic resend. Keep credentials in the approved secret store and grant the smallest scope the connection needs. Queue rejected records with their source identifier and a visible reason.

Test a provider timeout, a duplicate event and a revoked credential before turning on schedules. Availability depends on each provider’s API, commercial access and configuration.

Use the implementation plan to agree acceptance criteria for each connection.