ASPSPs provide a Unique, Immutable TransactionID from their core system
ASPSPs generate a Unique TransactionID from a set of Immutable fields
ASPSPs specify field(s) for TPP to generate a Unique Transaction Identifier
ASPSPs provide neither a TransactionID nor the method by which TPPs can generate one
Customer Journey
Implementing Customer Experience Guidelines?
Yes
Implementing Bespoke User Journeys?
Yes
Implementing App to App?
Yes
App to App Implementation Date?
Options on 90 day re-authentication?
Not supported. Max consent = 90 days
Support Embedded Flow?
No
PSD2
Dispute Management System?
Yes
FCA Adjustment Period - Maintaining Screen Scraping?
Seeking Fallback Exemption?
Yes
Adjusted or Fallback Interface?
No
Adjusted or Fallback URL?
N/A
Contact Email or Phone Number?
Dev Portal URL?
Test Facility Implementation Date?
- TBC
Production Interface Implementation Date?
- TBC
Contingency Measures
Please specify the location of the guidance that explains your strategy and plans for when your dedicated interface is unavailable. This should be a URL to your dev portal or artefact that provides TPPs with the information they require
Article 10 - Maximum time period after authentication?
Please specify how long the AISP has from the time when they receive the access token (after PSU authentication). This is the period the AISP must submit their first request before SCA will be re-applied to endpoints NOT exempt of SCA under Article 10. ASPSPs should consider that this timeline is consistent with the time limit applied by the ASPSP in the existing online PSU interface (i.e. before the PSU is logged out)
Article 10 - Endpoints exempt of SCA
Please specify which AIS endpoints will be exempt from SCA under Article 10. (delete as appropriate): Accounts, Balances, Transactions, Beneficiaries, Direct Debits, Standing Orders, Products, Offers, Parties, Scheduled Payments, Statements
Authentication Method - Open Banking Channel (Browser)?
Decoupled
Authentication Method - Open Banking Channel (APP)?