Open Banking Accout Connection (AIS)

Open Banking Account Connection - also referred to as AIS (Account Information Service) - is the process of granting consented access to bank account data through API. This page describes the consent process:

• Getting a consent link
• Directing the person who gives the permission to the consent link for approval
• Tracking and managing the resulting consent status.

Once consent has been granted, data retrieval is described in two follow-on pages depending on your needs:

• Data Aggregation and Enrichment (AIS)
  Standardized and enriched transactions and balances data from any account type(cash, card, loan, savings, securities)
• Insight Report (VIEW)
  Delivered as a webpage view or as JSON.

How the AIS consent flow works

1. You sign a JWT (RS512) describing the details of the requested consent:
   1. Account types and data baskets
   2. Consent period
   3. Identifier of the person/organization approving the consent (optional)
   4. UI display configurations (optional).
2. You POST it to Feezback's Link Generation Service (LGS), which validates it and returns a link.
3. You redirect the user to the link (from your app/website) or send that link to the user via offline channels (email, SMS, in-app, a QR code, wherever makes sense for your product).
4. The user opens the link and gets redirected for authentication and approval at their bank portal/app .
5. You receive a webhook with the final consent status.
6. Once the consent is valid, you can access the connected accounts data.

Environments

Consent flow variants

This page covers both consent flow variants — they use the same /link mechanism and largely the same JWT shape, differing mainly in what happens after consent is granted:

Main differences:

1. Account types and data baskets requirements:
   flow.accountTypes and flow.dataBasketsare required for the AIS (ais/user) variant, but ignored for VIEW (view_ais/user). VIEW defaults to requesting all data baskets and account types regardless of these claims. The rest of this page uses ais/user in examples; swap the srv value for the VIEW variant.
2. User authentication requirements
   While AIS accepts both authenticated and non-authenticated users, VIEW requires to submit a phone number for 2FA authentication.

Prerequisites

Before you start make sure to:

1. Complete Feezback onboarding to receive your TPP_ID and setup your environments access.
2. Configure a webhook endpoint for consent status updates.

How to create a consent link

1. Create a JSON with the relevant consent configurations:

{
  "sub": "user-123",
  "iss": "tpp/{TPP_ID}",
  "srv": "ais/user",
  "ttl": 1800,
  "flow": {
    "id": "default",
    "dataBaskets": ["ACCOUNTS", "BALANCES", "TRANSACTIONS"],
    "accountTypes": ["CACC", "CARD", "SVGS", "LOAN", "SCTS"],
    "timePeriods": ["TWELVE_MONTHS"],
    "userWasAuthenticated": true,
    "context": "your-internal-reference-id",
    "redirects": {
      "success": "https://example.com/success",
      "failure": "https://example.com/failure",
      "ttlExpired": "https://example.com/expired"
    }
  }
}

2. Sign the JWT with RS512, ES256, or EdDSA — your choice — then send it to /link. The response is always JWE-encrypted regardless of anything you put in the request.

curl --location --request POST 'https://{ENVIRONMENT}.feezback.cloud/link' \
  --header 'Content-Type: application/json' \
  --data-raw '{
    "token": "{GENERATED_JWT_TOKEN}"
  }'

3. Use the returned link to send the user into the consent flow.
4. Wait for the user to grant consent — track progress via the consent-status webhook.
5. Once the consent is valid, continue to Data Aggregation & Enrichment to pull raw account data, or Insights Report (Page View or JSON) if you used the VIEW flow.