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 74 Current »

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

Business Accounts are written against 3.1.10 specification 

Private Client Accounts are written against the 3.1 specification. We are aim to complete our private client upgrade by mid 2024. 

All consumers will be required update there subscriptions to include our new API products. This can be done by logging into the developer portal or by updating your App if you registered via DCR.

Read/Write API - Which date are you planning to implement your latest version?
Business Accounts completed June 2023
We'll look to migrate Private Client Accounts in mid 2024

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£20k for High Income clients 
£1m for High Net worth clients 
We perform checks on payments for security reasons and may call clients to verify information.
PISP - Daily Payment Limit£20k for High Income clients 
£1m for High Net worth clients 
We perform checks on payments for security reasons and may call clients to verify information.
How many months of transaction do you provide?2 Years 
Have you implemented TRIs (Transactional Risk Indicators), if not, date planned to Implement?Yes June 2024 
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)  

From June 2024 we will accept all TRI fields but will only process 'PaymentPurposeCode'.
The codes we'll process are the recommended UK Purpose Code in ISO 20022 Payment Messaging List.
As per the ISO 20022 requirement all payments relating to these types of payments need to include the appropriate payment codes. 

HLRP - Finance Property Loan Repayment 
HLST - Property Loan Settlement
PLDS - Property Loan Disbursement
PDEP - Property Deposit
PCOM - Property Completion Payment
PLRF - Property Loan Refinancing

SCA-RTS 90-day reauth Implementation

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

Mid 2023

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

  • With the inclusion of BCA in our product offering we'll update the token TTL to 365 days. This offering is currently in development and will be available with 3.1.10 specification 
  • Clients will have to re-authenticated after 365  days. 
  • We have deemed it a security risk to have open ended access to account information. 
  • Any consents granted to Private Client Accounts will have still have to re-authenticate after a 90 day period.

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


We will be upgrading our Private Client Accounts to the 3.1.10 specification in 2024.

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)


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) 
From end of November 2024 Investec Bank Plc will support FAPI (ID2) claims in our /token and /authorization. These endpoints will now validate the exp and nbf claims provided they are supplied in the requests independently and in isolation. 
From February 2025 we will make nbf and exp claims mandatory and validate the 60 min TTL 

Currently our live implementation is as follows

  • If only the nbf claim is supplied we will validate it
  • If only the expiry claim is supplied we will only validate that claim
  • if neither claim is supplied we'll still process request 

New implementation from Nov 2024 

  • both nbf and exp claims will still be optional 
  • If both claims are provided we'll validate both and validate that the exp claim is no longer than 60 minutes after the nbf claim

Final implementation from Feb 2025

  • both nbf and exp claims will be mandatory
  • if either claim is missing or time between both claims is longer than 60 mins we will reject the requests 


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 authenticationTBC
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
TBC depending on client usage of OB channel
PSD2
-Which Directory are you using as your Trust Framework?Open Banking
Are you caching the Directory?No
Transaction IDs SupportedNoTransaction ID's are a new field according to 3.2 specifications. We are currently still supporting 3.1

Are you Seeking Fallback Exemption?

  • Yes
  • No


Article 10 - Maximum time period after authenticationThe access token is valid for 10 minutes.AISPs will be able to access Account information endpoints without SCA for a 90 day period.
Article 10 - Endpoints exempt of SCA

None

 TPPs will be able to access Account information endpoints without SCA for a 90 day period.
Major MilestonesBusiness account offering in development using version 3.1.10
Brand(s)

ASPSP Dev Portal and Contact Details

Location of Well Known Endpoints 

https://developer.investec.com/uk/home  Developer Portal

Modified Customer Interface URL (if applicable)



Dev Portal URLhttps://developer.investec.com/uk/home
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) 

openapi@investec.co.uk
Key Implementations

High Cost Credit

Investec - HCC.xlsx

  • No labels