Verification

Banks hold a trove of data about us. They collect our identity details, record our transaction data, and maintain our account balances. You can use this data for KYC, AML, and other compliance use cases.

Verification Guide

Leverage bank data for compliance

Common use cases include:

  • Verify address: Verify address from connected accounts to avoid manual address verification.
  • Verify user's identity: Match the logged in name from connected accounts to the name on a driver licence or passport. This avoids the need for biometric verification in an AML process.
  • Verify bank account: Verify the account holder and account number.
  • Reduce fraud: Fetch data directly from the source to reduce the risk of fraud with paper and digital documents.
  • KiwiSaver withdrawals: Fetch transaction data to automate and collect evidence for hardship applications.
  • Income verification: Collect transaction data to support the source of funds in an AML¬†process.

Used by:

Response Sample

Consumers connect their financial accounts to your application via Akahu's OAuth connection flow.

Upon completion of that connection flow, your application holds a user token that enables programmatic interactivity with connected accounts via Akahu's API. The user token is scoped to the specific permissions granted by the consumer.

Other Use Cases

Payments

Genie

Transaction Data

Data

Talk with our team

Using the API

Keen to get started right now? Create a personal app which will grant you instant API access to your own accounts.

If you want access to a full app, contact us and we'll set it up.

Get in touch

Contract services

Our team can provide contract services to explore or build the functionality that you have in mind.

We'd love to discuss the options with you.

Get in touch