Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 72 Next »

OB Standards

This Section applies to ASPSPs that have impletemented 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

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?


Security Profile


-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 


Post Brexit Certificate Implementation
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

This info will be provided shortly


TPP PSU Migration Outcomes Supported (see eIDAS Migration Playbook)

Dynamic certificate authentication process.

Outcome 4: You can continue to use your OBseal for client authentication

Outcome 5: Continue using the key pair for client authentication

Outcome 8: Switch to a new OBseal to use with private-key-jwt

POST-BREXIT Certificate Implementation Status (updated by OBIE IES team)

Ready


Customer Journey

-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

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
Our payment journeys currently follow the exact journey as customer would get in their online banking.  The Customer Experience Guidelines says they payment journeys should be 2 step.  We will not be introducing the 2 step journeys until October 2019.

Options on 90 day re-authentication?

90 DaysA TPP can re-authentication any time up until the expiry date.  The customer will be made to re-authenticate every 90 days otherwise access to the data will be removed.
PSD2
-Which Directory are you using as your Trust Framework?Open Banking
Are you caching the Directory?No
Transaction IDs SupportedYesThe TransactionID is retrieved from our core system

Are you enrolled to Dispute Management System?

  • Yes
  • No

Are you Seeking Fallback Exemption?

  • Yes
  • No


Article 10 - Maximum time period after authenticationN/ANo SCA applied on AISP
Article 10 - Endpoints exempt of SCA

N/A

For article 10 we are only going with the 90 days re-authentication but not restrictions on payment types (DDs, SOs) or data for more than 90 days away.

Please note: We do not display statements

Major MilestonesVersion 3.1 was implemented in June 2019 and Security Conformance SUITE certification was achieved on August 2019
Brand(s)

ASPSP Dev Portal and Contact Details

Location of Well Known Endpoints

OB Technical Directory

The Well Known Endpoint for our Sandbox is: https://sandbox.caterallen.co.uk/.well-known/openid-configuration 

It is also indicated in the support section together with other relevant info: https://sandbox.caterallen.co.uk/store/site/pages/faq.jag 


The Production Well Known Endpoint is:

https://developer.caterallen.co.uk/.well-known/openid-configuration

It is also indicated in the support section together with other relevant info: 

https://developer.caterallen.co.uk/store/site/pages/faq.jag 

Modified Customer Interface URL (if applicable)



Dev Portal URL

Prod: https://developer.caterallen.co.uk/store/  

For Production URL we are live with AIS, PIS and CBPII.

Full live proving has been provided for AIS and PIS. For CBPII endpoints we are in Managed Rollout phase testing. Please contact us for further information.

Test Facility URLSandbox: https://sandbox.caterallen.co.uk/store/

ASPSP Support Desk Email or Phone Number

07727855715 / caterallenopenbanking@santander.co.uk

alessandro.greco@santander.co.uk 


Key Implementations

High Cost Credit

Cater Allen - HCC.xlsx

  • No labels