Integration paths for salary, accounting, devices, and tenant APIs.

Standard salary payout foundations, accounting exports, API access, and custom provider integration paths.

Current and planned rails

Integrations are treated as controlled add-ons, with provider credentials separated from platform billing credentials.

Flutterwave bulk transfer support is the first salary payout foundation, with funding controls required before live tenant payroll use.

Preferred-bank or payment-provider payroll funding should sit behind a provider interface and explicit commercial setup.

Dedicated tenant funding references are the reliable first rail before salary disbursement begins.

Flutterwave Direct Debit or E-mandate is treated as an approved automated NGN rail, not assumed available for every tenant.

Journal CSV plus QuickBooks, Sage, or Zoho-compatible exports can be added when target formats are confirmed.

Fingerprint and face device support requires confirmed hardware, consent design, device mapping, and security review before launch.

Standard salary payout foundations, accounting exports, API access, and custom provider integration paths.

Integrations are treated as controlled add-ons, with provider credentials separated from platform billing credentials.

Flutterwave bulk transfer support is the first salary payout foundation, with funding controls required before live tenant payroll use.

Preferred-bank or payment-provider payroll funding should sit behind a provider interface and explicit commercial setup.

Dedicated tenant funding references are the reliable first rail before salary disbursement begins.

Flutterwave Direct Debit or E-mandate is treated as an approved automated NGN rail, not assumed available for every tenant.

Journal CSV plus QuickBooks, Sage, or Zoho-compatible exports can be added when target formats are confirmed.

Fingerprint and face device support requires confirmed hardware, consent design, device mapping, and security review before launch.