Skip to main content
​
12-02-2026 (v1.7.0)

​
Bank Accounts V4 Support

Updates the response types for the Bank Accounts APIs to comply with the CDR Bank Account Detail V4 API. For customers who are already returning the V3 structure, we will not enable V4 on your Data Holder environment until you’ve informed us your API has been upgraded. The Data Holder platform will smoothly transition to support the V4 structure once it is available. To summarise the changes in structure:
  • BALANCE_TRANSFER is added as a new lendingRateType option
  • The type of the feature isActivated field has been changed from a boolean to an enum
  • FUNDS_AVAILABLE_AFTER has been added as a new feature type
  • OTHER and UNCONSTRAINED are added as new repaymentType enum values for the loan field and lendingRates elements
  • OTHER and UNCONSTRAINED are added as new loanPurpose enum values for the loanPurpose field of the lendingRates elements
  • applicabilityConditions within rate tiers is converted to an array. The additionalValue and rateApplicabilityType fields are added to the conditions as well. For reference on how to use the applicabilityType and what the appropriate use of additionalValue is for the type, refer to the CDS
  • applicabilityConditions is added to the root-level lending rate and deposit rate elements
  • minimumValue and maximumValue within rate tiers is changed from a number to a string
  • Removed the VARIABLE fee type
  • Fees and Discounts reworked significantly. Instead of specifying one of amount, balanceRate, accruedRate, or transactionRate, there is now a feeMethodUType and corresponding fields for determining the fee value. Similar changes are made to the discount structures. Refer to documentation for full reference.

​
Deprecation of industry-specific account list APIs

The Banking Get Accounts and Energy Get Accounts APIs have been deprecated. New integrations should use the List Accounts Available For Sharing API. This is part of an effort to unify the APIs required for authorising a consent across industries and jurisdictions. It also significantly simplifies the response required to complete an authorisation. The industry-specific fields were not used for the consent flow. Customers using the industry-specific APIs can continue to do so, without disruption.
​
06-02-2026 (v1.6.0)
Adds documentation for Microsoft (Entra ID) as an SSO provider for the Fiskil Console
​
07-03-2025 (v1.5.0)
  • Adds "open-status" filter to Energy Fetch Accounts for Customer API. This parameter is required to support the CDR Get All Accounts API which has a filter on account open-status. Valid values are "ALL", "OPEN", or "CLOSED". Only requested accounts with the matching open state should be returned.
​
06-08-2024 (v1.4.0)
  • Updates customer search response “phoneNumber” field description to support SMS delivery of authentication OTP
  • Removes unnecessary fields “givenName”, “familyName”, “updatedAt”, “address”, “emailVerified”, “email”, and “phoneNumberVerified” from customer search response
​
06-08-2024 (v1.3.3)
  • Clarification of banking Scheduled Payments **PaymentSet.To** properties. Full payee and account details should be returned with **accountID** and **payeeID** fields.
  • “Energy” tag added to energy industry endpoints.
​
05-08-2024 (v1.3.2)
  • Adds "is-owned" & "open-status" parameters to Obtain balances for a specified list of accounts (POST /v1/banking/customer/ {customerId}/accounts/balances) request
  • Adds "is-owned" & "open-status" parameters to Obtain direct debit authorisations for a specified list of accounts (POST /v1/banking/customer/{customerId}/accounts/direct-debits)request
  • Adds "is-owned" & "open-status" parameters to Obtain scheduled payments for a specified list of accounts (POST /v1/banking/customer/{customerId}/payments/scheduled) request
​
05-08-2024 (v1.3.1)
  • Adds “users” property to BankingAccountDetailV3 response object in API spec