capabilities.work

Decoupled Authentication then List Accounts

A 5-step recipe with Fintecture. We can help you get access.

Recipe · 5 steps

Decoupled Authentication then List Accounts

with Fintecture

Run decoupled PSU authentication, poll to completion, then enumerate accounts.

  1. Read the provider to confirm it supports the decoupled authentication model.
  2. Trigger provider authorization, which initiates a decoupled authentication request on the PSU's bank mobile app and returns a session id to poll.
  3. Poll the decoupled authentication status. COMPLETED proceeds to list accounts, FAILED routes to the failure step, and PENDING loops back.
  4. List the accounts linked to the connection now that the PSU has authenticated.
  5. Terminal failure handling — re-read the decoupled status so the failing state is captured in the workflow outputs.
What you'll need to have ready
  • accessToken: A valid AIS-scoped bearer access token.
  • providerId: Identifier of the bank provider to authenticate against.
  • customerId: The connection (customer) identifier to read accounts from once authenticated.
  • psuType: PSU segment, either "retail" or "corporate".
For your developer

Arazzo workflow fintecture:decoupled-auth-accounts, 5 operations: getResV1Provider → getAisV1ProviderAuthorization → getAisV1ProviderAuthorizationDecoupled → getAisV1CustomerAccounts → getAisV1ProviderAuthorizationDecoupled. Specs on APIs.io.

More recipes with Fintecture

Account Holders and Identity VerificationConnect, List Accounts, and Pull TransactionsOnboard Customer and Initiate PaymentCustomer Verification with PollingList Providers and Initiate PaymentRefund a Completed PaymentCreate Payment and Poll StatusRequest To Pay and Track StatusSandbox Test PaymentSettlement Reconciliation