Implementer Options

Identifier Description Decision
IO1 Mandate the TPP to sign requests on application level no
IO2 Supported Single Payment products
  • sepa-credit-transfers: yes
  • instant-sepa-credit-transfers: no
  • target-2-payments: no
  • cross-border-credit-transfers: no
  • pain.001-sepa-credit-transfers: no
  • pain.001-instant-sepa-credit-transfers: no
  • pain.001-target-2-payments: no
  • pain.001-cross-border-credit-transfers: no
IO3 Supported Bulk Payment products
  • sepa-credit-transfers: no
  • instant-sepa-credit-transfers: no
  • target-2-payments: no
  • cross-border-credit-transfers: no
  • pain.001-sepa-credit-transfers: no
  • pain.001-instant-sepa-credit-transfers: no
  • pain.001-target-2-payments: no
  • pain.001-cross-border-credit-transfers: no
IO4 Supported Periodic Payment products
  • sepa-credit-transfers: yes
  • instant-sepa-credit-transfers: no
  • target-2-payments: no
  • cross-border-credit-transfers: no
  • pain.001-sepa-credit-transfers: no
  • pain.001-instant-sepa-credit-transfers: no
  • pain.001-target-2-payments: no
  • pain.001-cross-border-credit-transfers: no
IO5 Supported SCA Approaches
  • Redirect: yes
  • OAuth2: no
  • Decoupled: no
  • Embedded: no
IO6 OAuth2 required as a pre-step for PSU authentication no
IO8 Support of TPP Messages on operational issues yes
IO9 Requirements regarding the selection of the SCA Approach to be applied not applicable
IO10 Transaction fees transported via the XS2A-Interface no
IO11 Supported SCA Methods
  • SMS_OTP: yes
  • CHIP_OTP: no
  • PHOTO_OTP: yes
  • PUSH_OTP: no
IO12 Configuration of supported SCA methods – applicable SCA Approaches
  • SMS_OTP
    • Redirect/Oauth2: yes
    • Embedded: no
    • Decoupled: no
IO13 Configuration of supported SCA methods – TPP Redirect Preferred
  • true
    • Redirect/Oauth2: yes
    • Embedded: no
    • Decoupled: no
  • false
    • Redirect/Oauth2: yes
    • Embedded: no
    • Decoupled: no
  • unused
    • Redirect/Oauth2: yes
    • Embedded: no
    • Decoupled: no
IO14 Authentication Requirements for the Decoupled SCA Approach not applicable
IO15 PSU-ID required in message
  • Payment Initiation Request: no
  • AccountInformationConsentRequest: no
  • Payment Cancellation: no
  • Signing Basket: no
IO16 PSU-ID-Type required in message
  • Payment Initiation Request: no
  • AccountInformationConsentRequest: no
  • Payment Cancellation: no
  • Signing Basket: no
IO17 Support of multicurrency accounts
IO18 Representation of account
  • IBAN: yes
IO19 PSU-Corporate-ID required in message, if a corporate account is affected
  • Payment Initiation Request: no
  • AccountInformationConsentRequest: no
  • Payment Cancellation: no
  • Signing Basket: no
IO20 PSU-Corporate-ID-TYPE required in message, if a corporate account is affected
  • Payment Initiation Request: no
  • AccountInformationConsentRequest: no
  • Payment Cancellation: no
  • Signing Basket: no
IO21 Support of future dated payments yes
IO22 Support of SCA exemption no
IO23 Support of sessions (combination of AIS and PIS) no
IO24 Support of PSU messages in relevant scenarios no
IO25 Grouping restrictions for Signing Baskets not applicable
IO26 SCA required for Payment Cancellation yes
IO27 Multi level SCA supported for Use Cases
  • Payment Initiation: no
  • Consent Establishment: no
  • Signing Baskets: no
  • Payment Cancellation: no
IO28 SCA approach supported for multi level SCA not applicable
IO29 ASPSP enforces explicit start of authorisation never
IO30 Support of optional account information access rights
  • allPsd2 related services for all ac-counts: no
  • only access rights in request, accounts handled between PSU and ASPSP afterwards: no
  • list of available accounts: no
  • list of available accounts with balances: no
IO31 Support of formats for account information.
  • xml: no
  • JSON: yes
  • Text: no
IO32 Support of optional Endpoints for AIS
  • accounts?withBalance: yes
  • accounts/{account-id}?withBalance: yes
  • accounts/{account-id}/transactions?withBalance: no
  • accounts/{account-id}/transactions/{resourceId}: no
IO33 Support of optional Query parameters for AIS
  • entryReferenceFrom: no
  • bookingStatus=pending: yes
  • bookingStatus=both: yes
  • deltaList: no
IO34 Support of Balance Types
  • openingBooked: no
  • expected: no
  • interimAvailable: yes
  • forwardAvailable: no
  • nonInvoiced: no
  • closingBooked: no
IO35 Conditions for delivery of a transaction list directly in the Response always
IO36 Conditions for delivery of a transaction list as a separate download with only a link in the response never
IO37 Redirect after first SCA-Factor not applicable
IO38 Implicit start of transaction authorisation supported yes
IO39 API steering links of type “startAuthorisationWith…” supported (i.e. creation of authorisation sub-resources and delivery of missing data at the same time supported) no
IO40 PSU Authentication data delivered via the XS2A-Interface (Embedded Approach) shall be encrypted at application level not applicable
IO41 Access to Multi-currency Account Details
IO42 Card Number supported to identify sub-accounts no