Sharing business account data

Business accounts behave differently from personal accounts in the consent flow. When an individual shares their own accounts, the institution only needs to verify their identity. When the account holder is a business — a company, trust, or partnership — the institution also needs to verify that the person consenting has authority to share the business's data.

Many institutions require the business to appoint a representative for data sharing before any business accounts will appear in the consent flow. The name for this role, who can appoint one, and how the appointment is done all vary by institution and by market. If a business user reaches the consent flow before this setup is complete, they'll typically see no eligible accounts — and they may abandon the flow assuming your product is broken.

How to succeed with business accounts

1. Identify business customers early. Know before the consent flow whether a user will be sharing business accounts, so you can set expectations up front.
2. Tell them what to prepare. A short heads-up — "your bank may need you to appoint a data sharing representative first" — prevents most drop-off. See Preparing your business customers.
3. Point them at the right guide. Send the per-institution page for their bank or retailer so they follow the exact steps, not a generic explanation.

In this section

• Australia (CDR): nominated representatives — what the role is and how appointment works.
• Preparing your business customers — a playbook for reducing drop-off.
• Per-institution guides for Australian banks and energy retailers, starting with ANZ.

Guides for other markets will be added as Fiskil expands coverage. For API behaviour and integration detail, see the developer documentation.