Content Comparison

•  Yes
•  No

•  None
•  V2.2
•  V2.3
•  V2.4

•  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

No update currently planned

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

•  None
•  V3.1
•  V3.2
•  V3.3

No update currently planned

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

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

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

Not applicable

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]

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

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

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

Contact: not applicable

[You can use this space to provide implementation details relevant to VRP]

£

See product description page on website
https://uk.virginmoney.com/

£

See product description page on website
https://uk.virginmoney.com/

For 5 minutes, the API will return transaction details for any period that the customer provides consent for. If ‘fromBookingDateTime’ is not specified, we will default to 90 days.
After 5 minutes, transaction details will only be returned for a 90 day period.

We currently have no plans to implement the additional 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)  

22nd September 2022

Long-lived refresh token from 22nd September 2022

AIS consents created after 22nd September 2022 - TPPs will be issued with long-lived refresh tokens, which will have a ten-year (3,650 days) expiry date, unless a shorter expiry date is provided by the AISP. This will allow them to refresh Access Tokens for a period of 10 years without requiring customer re-authentication.

Existing AIS consents will require a final re-authentication, where TPPs will present a valid short-lived refresh token (90 days) at which point they will be issued with a long-lived token, which will have a ten-year expiry date, unless a shorter expiry date is provided by the AISP.

*No further authentication will be required during the ten-year period, unless
• there is suspected fraud or unauthorised access or
• a PSU has revoked the access

*We reserve the right to request re-authentication of AIS consents for reasons including, but not limited to, the above stated reasons

• Accounts

• Transactions (90days)

• Balances

• Standing orders

• Direct debits

• Beneficiaries

• Products

• Offers

• Parties

• Scheduled Payments

• Statements

• Transactions (more than 90days)

• Standing orders

• Direct debits

• Beneficiaries

• Products

• Offers

• Parties

• Scheduled Payments

• Statements

5,256,000 minutes

Please specify the time period in minutes

Planned / In-progress / Implemented / TBC

•  OB Security Profile (Legacy)
•  FAPI (ID2)
•  FAPI 1 Advanced
•  Other (Please define) 

No update currently planned

•  None
•  CIBA
•  CIBA FAPI Profile

N/A

No certification currently planned

• client_secret_post

• client_secret_basic

• client_secret_jwt

• tls_client_auth

•  Private_key_jwt

N/A

•  eIDAS QWAC
•  

• eIDAS QSealC
•  OB legacy (obtransport, obsigning)
•  OBWAC
•  OBSeal
•  Other (Please define) 

•  Already Implemented
•  Planning to implement or upgrade
•  Not planning to implement CEG

•  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

No update currently planned

•  App to App redirection
•  Decoupled authentication
•  Embedded Flow
•  Bespoke User Journeys

Open Banking

Yes

Option 1

•  Yes
•  No

10 years (3650 days) for AISP (as long as the customer has allowed access for at least that length of time)

Balances, transactions, standing orders and direct debits

January 2023:

B, Clydesdale and Yorkshire Bank branded open banking services decommissioning following completion of our rebranding programme.  These accounts can now be accessed via the Virgin Money (merged) API services.

July 2020:

Virgin Money APIs launched
Domestic Immediate and Domestic Scheduled now includes Bacs and CHAPS.

March 2020:

QWAC/QSEAL eIDAS support

September 2019:

AISP endpoint APIs uplift to v3.1.2
Domestic Immediate Payments PISP uplift to v3.1.2
App to App redirect

August 2019:

Confirmation of Funds (PISP) API

Virgin Money (merged)

Virgin Money (merged):

https://api.openbanking.virginmoney.com/open-banking/v3.0/.well-known/openid-configuration

n/a

https://developer.virginmoney.com  

https://cb.sandbox-api-nc.cybservices.co.uk/open-banking/v3.0/.well-known/openid-configuration

Image Modified Brand logo for merged Virgin Money APIs

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

OpenBankingResponse@virginmoney.com

Support requests should be raised

via the Open Banking Service Desk by choosing Clydesdale Bank as the ASPSP and stating the ticket relates to our merged APIs.

A comprehensive list of products supported by each set of APIs is provided in this document