Data requests

Data requests let you ask a customer to securely share information from their bank account with you, without you ever needing to see or store their banking credentials.

Your customer approves exactly what they want to share directly in their bank app, and Volley delivers the data to you via our API.

How it works

1. Create a data request. Call the Volley API to create a request for the type of data you need and whether the request is one-off or ongoing.
2. Present it to your customer. Redirect them to the hosted consent page, or use the embed or mobile SDK to keep them in your app.
3. They approve. The customer selects their bank, is taken to their bank app, and approves or declines the data sharing request.
4. Pull the data. Once approved, Volley fetches the data from the customer's bank and makes it available via API. For ongoing requests, you can call the API again at any time to get updated data.

Request types

Volley supports two types of data request: Account verification and Transaction history.

Account verification

Account verification requests let you retrieve a customer's bank account details and identity information. This includes the account holder name, account number, and contact details held by their bank.

Account verification is used for confirming account ownership before making a payout, or verifying a customer's identity as part of onboarding.

Transaction history

Transaction history requests allow you to read transactions from a connected bank account for a given date range.

Transaction data is useful for affordability checks, income verification, expense categorisation, or aggregating a user's bank accounts within your app.

One-off and ongoing access

Data requests can be either one-off or ongoing:

A one-off request fetches data once at the point of consent. Volley will retrieve all data relevant to the request once, and then the connection to the bank is ended. You are able to retrieve data fetched from a one-off consent via the Volley API for up to 14 days afterward. One off requests are the best option for point-in-time checks like identity verification or a single affordability assessment.

An ongoing request keeps the consent active for a defined period, allowing you to fetch updated data at any time without asking the customer to re-approve. This is suited to use cases like continuous transaction monitoring, recurring affordability checks, or keeping account details in sync.

The customer can revoke an ongoing consent at any time through their bank app or the Volley dashboard at my.volley.nz.