Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Panel
titleColorBlack
borderStyledashed
titleOB Standards

This Section applies to ASPSPs that have impletemented OB Standards

Page Properties
iconfalse
idTC-OB Standards


-Have you Implemented OB Standards?
  •  Yes
  •  No

Open Data - Which version have you Implemented?
  •  None
  •  V2.2
  •  V2.3
  •  V2.4

Read/Write API Specification Implemented or planning to implement

(Lowest version = Current, Highest version = Planned)

  •  V3.0
  •  V3.1
  •  V3.1.1
  •  V3.1.2
  •  V3.1.3
  •  V3.1.4
  •  V3.1.5
  •  V3.1.6
  •  V3.1.7
  •  V3.1.8

Read/Write API - Which date are you planning to implement your latest version?

Dynamic Client Registration - Which version have you Implemented or planning to implement?

(Lowest version = Current, Highest version = Planned)

  •  None
  •  V3.1
  •  V3.2
  •  V3.3
Dynamic registration implementation is in progress. Date TBC
DCR - Which date are you planning to implement your latest version?

Have you implemented Trusted beneficiaries, if not date planned to Implement?

  •  Already Implemented
  •  Planning to implement
  •  Not planning to implement 

Have you implemented Reverse Payments, if not date planned to Implement?

  •  Already Implemented
  •  Planning to implement
  •  Not planning to implement 

PISP - Single Payment Limit£
PISP - Daily Payment Limit£
How many months of transaction do you provide?



...

Panel
titleColorBlack
borderStyledashed
titleSecurity Profile


Page Properties
idID-Production


-Which Security profile have you Implemented or planning to implement?

(Lowest version = Current, Highest version = Planned)

  •  OB Security Profile (Legacy)
  •  FAPI
  •  Other (Please define) 

Security Profile - Next Planned Version Implementation Date

CIBA Profile - Implemented or planning to implement

(Lowest version = Current, Highest version = Planned)

  •  None
  •  CIBA
  •  CIBA FAPI Profile

CIBA Profile - Next Planned Version Implementation Date
 

Security Profile Certification date?
 

Token Endpoint Authentication Methods Supported
  •  
    client_secret_post
  •  
    client_secret_basic
  •  
    client_secret_jwt
  •  
    tls_client_auth
  •  Private_key_jwt

Planned date to Cease support for client id and client secret token endpoint authentication


Following discussion with OBIE, agreed not to stop supporting Client Secret for all certificate types pending stabilisation of eIDAS. Date TBC.





Panel
borderStyledashed
titlePost Brexit Certificate Implementation


Page Properties
idStandards-Production


POST-BREXIT TRANSITION - Certificates Accepted (1st Jan 2021 - 30th Jun 2021)
  •  eIDAS QWAC
  •  eIDAS QSealC
  •  OB legacy (obtransport, obsigning)
  •  OBWAC
  •  OBSeal
  •  Other (Please define) 

POST-BREXIT POST TRANSITION - Certificates Accepted (from 1st Jul 2021)
  •  eIDAS QWAC
  •  eIDAS QSealC
  •  OB legacy (obtransport, obsigning)
  •  OBWAC
  •  OBSeal
  •  Other (Please define) 

Planned Implementation Date to Satisfy FCA's Post Transition

 


TPP PSU Migration Outcomes Supported (see eIDAS Migration Playbook)

N/A - We support client_secret_post

Certificate is not bound to consent so no migration is required other than to use a compliant certificate.

If a TPP needs any support in this process please contact us at openbankingAPI@santander.co.uk
POST-BREXIT Certificate Implementation Status (updated by OBIE IES team)

Ready

  • Ready – ASPSP accept eIDAS certs and OB Certs(OBWAC/OBSeal)



...

Panel
titleColorBlack
borderStyledashed
titleCustomer Journey


Page Properties
idTC-CJ


-What is your approach to Implementing OBIE Customer Experience Guidelines (CEG)?

(tick all that apply)

  •  Already Implemented
  •  Planning to implement or upgrade
  •  Not planning to implement CEG
Santander designs are looking to adhere to CEG but are also accounting for other regulatory commitments that fit outside of the CEG

Which version have you implemented or planning to implement?

(Lowest version = Current, Highest version = Planned)

  •  V3.1.2
  •  V3.1.3
  •  V3.1.4
  •  V3.1.5
  •  V3.1.6
  •  V3.1.7
  •  V3.1.8

Which date are you planning to implement your latest CEG version?TBC
Redirection Model
  •  App to App redirection
  •  Decoupled authentication
  •  Embedded Flow
  •  Bespoke User Journeys

Options on 90 day re-authentication?

90 day re-authentication




Panel
titleColorBlack
borderStyledashed
titlePSD2


Page Properties
idTC-PSD2


-Which Directory are you using as your Trust Framework?Open Banking
Are you caching the Directory?Yes
Transaction IDs Supported

Option 1 Supported

ALL Accounts (except Credit Cards) - Live

Credit Card Accounts -  Live 

ASPSPs provide a Unique, Immutable TransactionID from their core system

Are you enrolled to Dispute Management System?

  •  Yes
  •  No

Are you Seeking Fallback Exemption?

  •  Yes
  •  No


Article 10 - Maximum time period after authentication90 days
Article 10 - Endpoints exempt of SCA

Accounts, Balances, Transactions, Beneficiaries, Direct Debits, Standing Orders, Products, Offers, Parties, Scheduled Payments, Statements

We are continuing to allow Customer non present access to these data endpoints as long as a valid consent token exists.
Major Milestones

Credit Card Accounts (AIS): 14 Aug 2019

App-to-app: 27 Aug 2019

Corporate Customers >6.5m 12 Sept 2019

Savings Accounts: 13 Sept 2019

Cahoot Accounts: 13 Sept 2019

CHAPS Payments 13 Sept 2019

Dynamic Registration: TBC

CBPII Endpoints 14 Sept 2019

International Payments 14 Sept 2019

Credit Card Accounts (PIS): 29 Oct 2019

HCCR Update - In order to display  balance amount in accordance with the HCCR regulation Santander will add the Balance Including Pending and Overdraft Remaining elements in the JSON response for all balance requests for applicable Retail and Business accounts. Deployment date 10th December 2019







3.1.5 AIS is scheduled for launch 30/08/20.

Corporate functionality for Batch and BACS is due for end of July & Multi-Authorisation for end of September. If you or your Corporate customers want to access these services beforehand please contact openbankingAPI@santander.co.uk and we will discuss our contingency mechanism with you.

The customer balance including the overdraft will be sent in the JSON file as type 'InterimAvailable'.The remaining overdraft will be returned to TPPs in the JSON file as a creditline item and mapped as follows:

OBCreditLine1

OBReadBalance1/Data/Balance/CreditLine/Included - this item will be set to "false".

OBReadBalance1/Data/Balance/CreditLine/Type - set to "Available"

OBReadBalance1/Data/Balance/CreditLine/Amount/Amount - set to the amount of the Overdraft Remaining

OBReadBalance1/Data/Balance/CreditLine/Amount/Currency - set to the currency code of the account balance

The creditline items for Pre-Agreed will remain as is but the item OBReadBalance1/Data/Balance/CreditLine/Included will be set to "false"


Brand(s)



...

Panel
titleColorBlack
borderStyledashed
titleASPSP Dev Portal and Contact Details


Page Properties
idTC-C


Location of Well Known Endpoints

OB Technical Directory

Modified Customer Interface URL (if applicable)



Dev Portal URL

https://developer.santander.co.uk

https://sandbox-developer.santander.co.uk/sanuk/external-sandbox/

Test Facility URL

ASPSP Support Desk Email or Phone Number

Business/Technical: openbankingAPI@santander.co.uk



...