Tesco Bank

Owned by Adam Pretlove (Unlicensed)
Last updated: Nov 08, 2024 by Debbie Chapman
OB Standards

This Section applies to ASPSPs that have implemented 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
  • v3.1.9
  • v3.1.10
  • V3.1.11
  • V4.0

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

Have you implemented v4.0 information flows, if not date planned to Implement?

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

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 

Have you implemented ECA Standard?

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

ECA Implementation details


Contact: [enter contact details for the relevant person(s) at your organisation]

[You can use this space to provide your status with respect to the Standard]

Have you implemented Bulk/File Payments?

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

Have you implemented VRP – Sweeping, if not date planned to Implement?

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

Have you implemented VRP non-Sweeping, if not date planned to Implement?

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

Contact: [enter contact details for the relevant person(s) at your organisation]

[You can use this space to provide implementation details relevant to VRP]
PISP - Single Payment Limit£
PISP - Daily Payment Limit£
How many months of transaction do you provide?

Have you implemented TRIs (Transactional Risk Indicators), if not, date planned to Implement?

What is your approach to Implementing TRIs?
  • Accept payload with TRI fields – Process all fields
  • Accept payload with TRI fields – Ignore all fields
  • Reject payload with TRI fields – Error back to TPP
  • Accept payload with TRI fields – Process few fields (Provide list of accepted fields)  

SCA-RTS 90-day reauth Implementation

Which date are you planning on implementing the SCA reauthentication exemption?

27 September 202227 September 2022

What is your approach to token management to enable application of the reauthentication exemption? (see link to FCA guidance)

We will implement the exemption by issuing refresh tokens with no expiry date.

We will implement the exemption by issuing refresh tokens with no expiry date.

Existing consents

  • The first time that the 90 day refresh token is exchanged for an access token following our change, the new refresh token issued will have an unlimited expiry. Subsequent refresh tokens issued for the consent will continue to have unlimited expiry. The TPP can then go on to access exempt data for the consent on an ongoing basis, subject to consent expiry or revocation.
  • As long as the ‘old’ refresh token is exchanged before its original 90 day expiry, the customer will not need to re-authenticate with us. If it has been more than 90 days since the customer authenticated for the consent, we will not allow the refresh token to be exchanged for a new non-expiring one.
  • We will continue to ask for SCA when accessing non-exempt data under the consent, if it has not been done within 5 minutes.


New consents

  • Consents set up and authorised after our change goes live will use non-expiring refresh tokens for their lifetime. We will still require customers to complete SCA with us at authorisation, but customers will no longer need to come back to us every 90 days to re-authenticate.
  • We will ask for SCA when accessing non-exempt data under the consent, if it has not been done within 5 minutes.

We will continue to request SCA for non-exempt data requests.

Article 10A - Endpoints exempt of SCA-RTS

  • Accounts

  • Transactions (90days)

  • Balances

  • Standing orders

  • Direct debits

  • Beneficiaries

  • Products

  • Offers

  • Parties

  • Scheduled Payments

  • Statements


Article 10A - Endpoints not exempt of SCA-RTS

  • Transactions (more than 90days)

  • Standing orders

  • Direct debits

  • Beneficiaries

  • Products

  • Offers

  • Parties

  • Scheduled Payments

  • Statements


Article 10A - Maximum time period after authentication
Please specify the time period in minutes
SCA-RTS implementation status (updated by OBL PS team only)

IMPLEMENTED


Security Profile


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

(Lowest version = Current, Highest version = Planned)

  • OB Security Profile (Legacy)
  • FAPI (ID2)
  • FAPI 1 Advanced
  • 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 authenticationn/a
POST-BREXIT POST TRANSITION - Certificates Accepted (from 1st Jul 2021)
  • eIDAS QWAC
  • eIDAS QSealC
  • OB legacy (obtransport, obsigning)
  • OBWAC
  • OBSeal
  • Other (Please define) 

Customer Journey

-What is your approach to Implementing OBL 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
  • v3.1.9
  • v3.1.10
  • V3.1.11
  • V4.0

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

PSD2
-Which Directory are you using as your Trust Framework?Open Banking
Are you caching the Directory?No
Transaction IDs SupportedNoNo transaction IDs provided in transaction response, consistent with online/mobile channels.

Are you Seeking Fallback Exemption?

  • Yes
  • No


Article 10 - Maximum time period after authentication5 minutes for those endpoints NOT covered by an exemption (i.e. direct debits, beneficiaries etc.) and 90 days if exempt.
Article 10 - Endpoints exempt of SCA

Accounts, Balances, Transactions (< 90 days)

Resources covered (delete as appropriate): Accounts, Balances, Transactions
Major MilestonesSCA is already in place at log in for the existing Online and Mobile channels and was in place pre-PSD2.Production date for SCA in the Open Banking channel to be provided.
Brand(s)

ASPSP Dev Portal and Contact Details

Location of Well Known Endpoints

OB Technical Directory and OB Implementation Guide

Modified Customer Interface URL (if applicable)



Dev Portal URLhttps://developer.tescobank.com/
Test Facility URL

Brand Landing Pages URL
[You can use this space to explain your guidance on using Brand logos]

ASPSP Support Desk Email or Phone Number

(including queries about consent success rates) 

apisupport@tescobank.com
Key Implementations

High Cost Credit

Tesco - HCC - Nov 19.xlsx