Versions Compared

Key

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

Announcements


Improvement
Delivery date
Production
Improvement
Delivery date

Production API available for integration. For more information on how to integrate with our API or to access test accounts please contact openbankingsupport@vanquisbank.co.uk

 
eIDAS certificates are now supported in our Test facility 
eIDAS certificates are now supported in Production 
Implemented Payment Initiation APIs v3.1.7 are now Implemented  

Change to Production:

Implemented Account Information Service APIs v3.1.8

Implemented SCA-RTC v3.1.10


Change to Production:


Improvement
Delivery date

Production API available for integration. For more information on how to integrate with our API or to access test accounts please contact openbankingsupport@vanquisbank.co.uk

 New internally-hosted test facility available which provides closer alignment to production interface 

or to access test accounts please contact openbankingsupport@vanquisbank.co.uk

 
New internally-hosted test facility available which provides closer alignment to production interface 
Allowed AISP to send expiration date in the account access consent call. 
  • As part of v3.1.10 Implementation, Vanquis will introduced a long lived refresh token of 60 years.
  • Consent will not be expire and if the consent is revoked then need to create new consent.
  • AISP/CBPII/PISP consents created after implementation of v3.1.10 will no longer require re-authentication every 90 days. The new rules in place will ask for customer reconfirmation with the TPP not ASPSP.
  • Consents issued and authorised before v3.1.10 implementation will remain valid for 90 days.
  • There are no changes to Vanquis current implementation of Access Tokens. Third parties should continue to pass OAuth credentials in a Get Access Token call.  In response, the Vanquis authorisation server issues an access token, reuse the access token until it expires. When it expires, you can get a new token.


Info
titleProduction and Test facility Full interface Specifications

General guidance notes:

  • For guidance on detailed documentation of the Read/Write Data API specifications please visit the appropriate section on the Open Banking Developer Zone
  • We are currently supporting version 3.1.10 for AISP & , CBPII and version 3.1.7 for PISP specifications of the Open Banking Standard
  • App-to-app redirection is only supported in Production not in the test facility.
  • This is reflective of the current state of Vanquis' payment service operations.
  • For all related implementation support please contact openbankingsupport@vanquisbank.co.uk
  • Dynamic Client Registration is enabled and is mandatory
  • Supported endpoint token methods: private_key_jwt
  • Supported grant types: client_credentials & authorisation_code
  • Display of data IDs (e.g. transactionid & statementid) in REST responses is enabled
  • The Open API test facility should not be used for load testing

...

Swagger version

We currently support version 3.1

See JSON version: https://raw.githubusercontent.com/OpenBankingUK/read-write-api-specs/v3.1.0/dist/account-info-swagger.json

See YAML version: https://raw.githubusercontent.com/OpenBankingUK/read-write-api-specs/v3.1.0/dist/account-info-swagger.yaml

Base URI

Production: https://mtls.data.openbanking.vanquis.co.uk/open-banking/v3.1/aisp/

Test facility: https://sandbox.mtls.data.openbanking.vanquis.co.uk/open-banking/v3.1/aisp/

General variances to specification Please see above "Tips/Notes for TPP's" section
Non-functional limitations
  • Live environment hence unsuitable for load testing
  • Transaction History - We support 6 months transaction history
  • Pagination - We do not support pagination
  • Re-authentication/Authorization - Access token lifetime is 10 minutes
  • Refresh tokens are supported, lifetime is 90 days60years


The following endpoints are implemented and will return data where applicable

...

Ref ResourceEndpointsNotes 
1Products
  • GET /accounts/{AccountId}/product
  • GET /products

2Party
  • GET /accounts/{AccountId}/party
  • GET /party

3

Beneficiaries

  • GET /accounts/{AccountId}/beneficiaries
  • GET /beneficiaries

4Direct Debits
  • GET /accounts/{AccountId}/direct-debits
  • GET /direct-debits

5Standing-orders
  • GET /accounts/{AccountId}/standing-orders
  • GET /standing-orders

6Scheduled payments
  • GET /accounts/{AccountId}/scheduled-payments
  • GET /scheduled-payments

7Statements
  • GET /accounts/{AccountId}/statements/{StatementId}/file
  • All other statements endpoints are implemented, only statement/file is not implemented.

...


The following endpoints are implemented and will return data where applicable

...

Swagger version

We currently support v.3.1.7

See JSON version: TBA

See YAML version: TBA

Base URI

Production: https://mtls.data.openbanking.vanquis.co.uk/open-banking/v3.1.7/pisp/domestic-payments/

Test facility: https://sandbox.mtls.data.openbanking.vanquis.co.uk/open-banking/v3.1.7/pisp/domestic-payments/

General variances to specification None
Non-functional limitations
  • Environment not suitable for load testing

The following endpoints are implemented and will return data where applicable

...