Sainsburys Bank PLC.

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?

18th October 2022

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

We are setting the refresh token to never expire but we still need to rotate, as certs will only be issued for 2 years.  This means that as long as TPP gets data from us at least every couple of years the customer will never be prompted for an SCA again.

Example approach:
Issue a long-lived refresh token during one final SCA, with refresh token rotation implemented.

[Please use this space to provide more details on your approach]

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

Planned / In-progress / Implemented / TBC
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 authentication

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

Sainsbury’s Bank (SB) will implement all Customer Experience Guidelines that apply to SB with one exception.

Question #14 of the Customer Experience Guidelines Checklist (section 6 of https://www.openbanking.org.uk/wp-content/uploads/Customer-Experience-Guidelines-V1-2.pdf) asks:

  • "Do you provide access to all account information made available to the PSU through your existing online channel(s), irrespective of the channel through which the TPP is presenting their service to the PSU?"

All mandatory fields specified in API are returned. However, some fields – e.g. name, address – are not mandatory in API, and are not returned via API. Name and address are shown via statement channel, therefore "all account info made available” via the statement channel is NOT available via API.

If Question #14 were reworded to specify only the mandatory API fields, then SB’s response would be “Yes”.

Some other elements will not be implemented until  

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?YesFor one hour
Transaction IDs Supported Sainsburys Bank provide a Unique, Immutable TransactionID from their core system

Are you Seeking Fallback Exemption?

  • Yes
  • No


Article 10 - Maximum time period after authentication10 minutes
Article 10 - Endpoints exempt of SCA

GET /Accounts

GET /accounts/{AccountId}

GET /accounts/{AccountId}/balances

GET /accounts/{AccountId}/transactions

Access to accounts endpoints allows retrieval of the AccountId to call balance and transaction endpoints 


Major Milestones

Live (non SCA)   

Live (including SCA) December 2019


Brand(s)

ASPSP Dev Portal and Contact Details

Location of Well Known Endpoints

OBIE Sandbox Directory - Defined in the Auth Server, also defined in the Implementation guide

OBIE Production Directory - Defined in the Auth Server, also defined in the Implementation guide


Modified Customer Interface URL (if applicable)



Dev Portal URLdeveloper.sainsburysbank.co.uk
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) 

openbanking@sainsburysbank.co.uk
Key Implementations

High Cost Credit

N/A