ACSISS Platform

Creating CDR consent

Initiate the ACSISS-hosted consent flow for your customer. Call the consumer consent endpoint - ACSISS returns a redirect URL that takes your customer through the accredited CDR consent wizard.

From the end client’s perspective, the consent journey is designed to be straightforward:

  • The Platform initiates the ACSISS consent journey and provides the end client with the consent link.

  • The end client completes the ACSISS-hosted consent flow, where they identify themselves and select the bank/institution and accounts they want to share.

  • The end client authenticates with their bank and provides the required consent to share their banking data with the Platform via ACSISS.

  • The consent is granted by the account holder / authorised person for the relevant bank account. For business accounts, the bank may require the person completing the journey to be appropriately authorised, including through the bank's Nominated Representative process where applicable.

  • The end client can see what data is being requested, the institution/account being connected and the relevant consent information before completing the authorisation.

  • Once consent is successfully established, ACSISS retrieves the authorised data and makes it available to the Platform through the APIs.


Use a Unique ID to Identify Your Client

When creating accounts, we strongly recommend providing an obfuscated identifier that represents your client. This makes it easier to match the account and transaction data SISS returns with the corresponding client in your system.


Share Data using Business Disclosure Consent

Share Data using Consumer Disclosure Consent


What happens next

Redirect your customer's browser to the redirectUri returned in the response. They complete the ACSISS-hosted CDR consent wizard, then are redirected back to your redirectUri with the consent result.