Versions Compared

Old Version 77

changes.mady.by.user Praveen Ponnumony

Saved on

compared with

New Version Current

changes.mady.by.user Praveen Ponnumony

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Panel
titleColorBlack
borderStyledashed
titleOB Standards

This Section applies to ASPSPs that have implemented OB Standards


Page Properties
iconfalse
idTC-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

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

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?No update currently planned

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

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]

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: not applicable

[You can use this space to provide implementation details relevant to VRP]
PISP - Single Payment Limit£See product description page on website
https://uk.virginmoney.com/
PISP - Daily Payment Limit£See product description page on website
https://uk.virginmoney.com/
How many months of transaction do you provide?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.
Are you planning to implement TRIs(Transactional Risk Indicator enhancements included in v3.1.10), if so, implementation date?We currently have no plans to implement the additional TRIs
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)  



...

Panel
borderStyledashed
titleSCA-RTS 90-day reauth Implementation


Page Properties
idSCA-RTS


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

22nd September 2022

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

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

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 authentication5,256,000 minutesPlease specify the time period in minutes
SCA-RTS implementation status (updated by OBIE PS team only)


Planned / In-progress / Implemented / TBC



...

Panel
titleColorBlack
borderStyledashed
titlePSD2


Page Properties
idTC-PSD2


-Which Directory are you using as your Trust Framework?Open Banking
Are you caching the Directory?Yes
Transaction IDs SupportedOption 1

Are you enrolled to Dispute Management System?

  •  Yes
  •  No

Are you Seeking Fallback Exemption?

  •  Yes
  •  No


Article 10 - Maximum time period after authentication10 years (3650 days) for AISP (as long as the customer has allowed access for at least that length of time)
Article 10 - Endpoints exempt of SCA

Balances, transactions, standing orders and direct debits


Major Milestones

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


Brand(s)

Virgin Money (merged)




...

Panel
titleColorBlack
borderStyledashed
titleASPSP Dev Portal and Contact Details


Page Properties
idTC-C


Location of Well Known Endpoints

Virgin Money (merged):

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



Modified Customer Interface URL (if applicable)

n/a
Dev Portal URLhttps://developer.virginmoney.com  
Test Facility URLhttps://cb.sandbox-api-nc.cybservices.co.uk/open-banking/v3.0/.well-known/openid-configuration
Brand Landing Pages URL

 Brand logo for merged Virgin Money APIs

[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) 

OpenBankingResponse@cybg.com 

Support requests should be raised via our Service-Now Support Portal:
https://virginmoney.com/openbankingsupport

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



ADDITIONAL ASPSP INFORMATION
What products are available under the Merged and Stand-Alone Virgin Money APIs?A comprehensive list of products supported by each set of APIs is provided in this document
View file
nameVirgin Money Open Banking Available Accounts v3.3.pdf
height250



...