Basiq Pricing for Mortgage Brokers 2026

Basiq pricing combines a platform access fee with monthly charges per customer and separate charges for enrichment or affordability reports. It suits brokerages that need consented bank data, either through Basiq’s dashboard, an existing platform or a custom integration. Your buying decision depends on the complete commercial package and who owns the data-review workflow.

Basiq Pricing and Commercial Model

Basiq’s public pricing page, as at October 2026, separates customer data, enrichment and affordability reporting. Data and enrichment use a per-user, per-month billing unit. Affordability reports use a per-report unit, while platform access attracts a separate fee.

The pricing FAQ says a created user is billable for the full month regardless of their number of connections or activity. Its plans have a minimum duration of 12 months. Volume packages depend on committed user numbers and can include premium support and integration assistance.

Basiq’s terms state Australian dollars and exclude goods and services tax (GST) unless stated otherwise. The production agreement must identify the platform fee and selected products. Budget separately for your developer or platform supplier, ongoing maintenance and any implementation work outside that agreement.

The following items affect the commercial package you need.

Cost Component	Published Structure	Brokerage Implication
Development	Free initial sandbox testing	Simulated connections help development, but don’t prove live bank coverage
Production data	Monthly per-user data charge plus platform access	Several accounts for one customer don’t create separate connection charges under the published model
Enrichment	Separate monthly per-user product	Budget for categorisation when raw transaction data alone is insufficient
Affordability reporting	Separate per-report product	Repeated report generation creates a different cost driver from customer numbers
Support and implementation	Custom packages can include premium support and integration assistance	Define supplier responsibilities and support commitments in the agreement

Basiq’s testing documentation limits sandbox connections to 500. Its rate-limit guide separately caps sandbox enrichment at 100 requests per month. Production limits still apply, and exceeding platform limits can attract extra charges or errors.

For a direct purchase, Basiq’s pricing page directs production enquiries to its sales team. For an existing platform, the platform supplier’s contract controls what your brokerage pays. A supplier can bundle Basiq access with its own reporting or workflow charges.

Consent and Bank-Data Coverage

Basiq collects bank data as an accredited data recipient under the Consumer Data Right (CDR), with the consumer’s consent. The bank is the data holder. Your brokerage’s role depends on its access arrangement, so a broker receiving data as a trusted adviser has different obligations from a CDR representative.

The Office of the Australian Information Commissioner’s (OAIC) trusted-adviser guidance includes qualifying mortgage brokers. Consumers nominate the adviser and consent to disclosure. Trusted advisers aren’t CDR participants, although applicable privacy law and professional duties still govern their handling of the information.

Basiq documents a direct trusted-adviser route for qualifying mortgage broker firms. It also documents an individual-adviser route through a principal and representative arrangement, with an aggregator as an example. The named adviser appears in the consent flow, and the integration must pass the appropriate adviser details.

What the Borrower Authorises

Basiq’s Consent UI is a hosted consent interface that uses a full-page redirect. Its developer guidance says embedding that interface in an iframe isn’t supported. The application sends the borrower into the consent journey and receives them back with job identifiers after completion.

The borrower authorises the requested data sharing and selects the available accounts through the bank’s authorisation journey. Consent records must identify the intended use and recipient. Collection permission and permission to disclose data to a trusted adviser have distinct purposes.

The CDR recipient obligations describe consumer choice over data types and sharing duration, with a maximum of 12 months. Basiq documents consent extension and bank-connection reauthorisation flows. Ongoing collection needs valid consent and authorisation, rather than an assumption that an earlier connection stays usable indefinitely.

Basiq’s CDR policy allows consumers to modify or withdraw consent through the partner application. They can also contact Basiq in writing or use their bank’s consent dashboard. Expiry or withdrawal triggers deletion or de-identification under the policy, subject to data that Australian law requires retained.

Coverage for a Particular File

Basiq’s supported-institutions page lists 136 financial institutions across Australia and New Zealand as at October 2026. Its table distinguishes web connections from Open Banking. That platform-wide total doesn’t establish that a particular borrower’s institution, account or required history is available through CDR.

The Data product provides account information and transaction history. Its published account example includes the account holder and account number, currency, balances, account class and covered transaction intervals. Those fields help identify the source and period, but a field in an example isn’t proof that every connected institution supplies it.

A failed connection or missing account leaves an evidence gap in that file. Obtain the missing institution-issued statements or other evidence the target lender accepts. If a different connection method is proposed, it needs its own suitable permissions and privacy treatment.

For the wider collection process, read the Open Banking home-loan workflow. Basiq’s fit depends on whether its specific connection returns the accounts and period that your file requires.

Implementation and Broker Workflow

Basiq has a direct application programming interface (API) route and an official dashboard route. An existing platform can also mediate access under its own arrangement. Exporting a report is a manual handoff, not evidence of a native integration with your brokerage’s systems.

Route	Technical Owner	Data Direction and Broker Output
Direct API integration	Brokerage developer or contracted development team	Consented bank data enters Basiq, then the authorised application retrieves data or reports
Basiq dashboard	Basiq owns the interface, while the brokerage owns its operating process	The brokerage collects customer data and generates insight reports without implementing its own interface
Existing platform using Basiq	Platform supplier owns its integration	Basiq supplies the authorised platform, which controls the broker-facing output and available workflow
Manual report export	Broker or authorised staff member	A PDF or comma-separated values (CSV) report moves from the dashboard into the approved file-storage process

Basiq’s Data page describes consent links, customer-data viewing and connection-error troubleshooting in its dashboard. Its Insights page describes consolidated reports and PDF or CSV exports. These are documented routes, not a promise that every product or permission is included in one brokerage contract.

A Synthetic Home-Loan File

Consider an illustrative application from Priya, who uses a salary account and a separate savings account. Her credit card is held at another institution. The following sequence explains implementation responsibilities, not observed results from a live Basiq session.

1. The platform creates the customer record and launches Basiq’s consent interface. It identifies Priya’s nominated recipient and requests the data needed for the application.
2. Priya completes the bank authorisations for the relevant accounts. The platform records consent status and the connection job outcomes.
3. The technical owner retrieves accounts and transactions once the jobs complete. It records each source account, refresh time and available transaction period.
4. The application uses Basiq’s enrichment or insights products where contracted. It keeps the underlying transactions accessible alongside any grouped income or expense output.
5. The broker reconciles the output against Priya’s declarations. Transfers between her accounts aren’t automatically additional salary or living expenses.
6. If the credit-card connection fails, the broker obtains the missing statements. The technical owner records the failed job and handles the connection exception without treating missing transactions as zero expenditure.
7. The approved storage process retains the consent receipt, dated output and broker’s review notes. Access and retention follow the applicable data role, permissions and legal requirements.

Basiq’s documentation groups connections, consent and jobs separately from enrichment and reporting. Your developer must handle errors and expired permissions as part of the integration. A successful consent redirect alone doesn’t establish that every required account has returned complete data.

Assessment Evidence and Limitations

Basiq’s account data and insights can support income and expenditure review, but collection alone doesn’t establish lender acceptance or borrowing capacity. Basiq’s Insights product identifies income sources, groups expenses and supplies information about liabilities. The broker must reconcile those outputs with the facts of the application.

Evidence	What It Helps You Review	Reconciliation Required
Salary credits	Payment amounts, frequency and changes	Match payer descriptions and amounts to payslips and employment evidence
Account balances and identifiers	Ownership, available funds and source accounts	Separate available funds from actual savings where credit facilities affect availability
Categorised expenses	Spending groups and recurring payments	Review ambiguous merchants, reimbursements and spending across multiple accounts
Loan or credit-card information	Existing debts and repayment activity	Include facilities absent from connected accounts and reconcile declared limits
Transaction periods	Which dates the output covers	Fill missing periods and distinguish unreturned data from an absence of activity

In Priya’s illustrative file, a transfer into savings remains her own money moving between accounts. A different payer name on a salary credit needs reconciliation with her employment evidence. Neither case becomes verified income simply because the data has a category.

Basiq’s account documentation says balances exclude pending transactions, while available funds can include an overdraft or credit facility. Its account-retrieval guidance distinguishes the last retrieved data from a fresh connection refresh. Preserve the extraction date so a reviewer knows which information the report reflects.

The lender decides which evidence formats it accepts and applies its own serviceability calculation, including income treatment and repayment assumptions. A Basiq affordability report doesn’t establish that a lender uses the same calculation. Final credit judgement remains with the lender, while the broker remains responsible for reviewing and explaining the file.

Use the bank-statement analysis guide for the underlying interpretation method. Keep the source data and your corrections together so someone reviewing the file can follow why the assessed figures differ from an automated category.

Who Basiq Fits

Basiq fits a brokerage that wants consented bank-data collection and has an identified owner for the review process. The easiest buying route depends on whether you already have a suitable platform, need dashboard access or require a custom data path.

For an existing platform, choose its Basiq-backed workflow when its contracted outputs cover your file requirements and its supplier owns integration support. The brokerage still needs an authorised recipient arrangement and a process for missing accounts. Buying through a platform doesn’t transfer the broker’s evidence review to Basiq.

Direct implementation fits a brokerage with development capacity and a reason to control its own data flow. The deciding costs include the platform fee, customer volumes, selected insight products and ongoing maintenance. Basiq’s free sandbox supports development, while the production commitment and support terms determine operating cost.

For a brokerage needing a ready-made interface, Basiq’s dashboard is a documented option for collection and reporting. A dedicated broker platform is a better fit when your requirement is a complete assessment workflow with file management and lender-specific outputs. The existence of a dashboard doesn’t establish those additional functions.

Use another provider when its documented coverage or contracted support meets a requirement Basiq’s selected route doesn’t meet. Use institution-issued documents when consent is declined, an account is unavailable or the target lender needs a statement the selected output can’t supply. Buy the route that produces usable evidence for your files with a clear technical owner and an affordable operating commitment.