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

This page has been created and maintained by the relevant ASPSP, and OBIE takes no liability for the completeness nor accuracy of this data.

Note to ASPSP: Please indicate which brands this applies to and/or duplicate this page per brand if relevant.


ASPSPYorkshire Building Society
BrandYorkshire Building Society and Chelsea Building Society
Date25/03/19
Developer portal (s)https://developers.ybs.co.uk/

Announcements

Improvement
Delivery date
  • API live for PISP Standing Orders

  • API live for CBPII

  • AISP transactions for last 24 hours
 
Implementation of SCA for web and API interfaces 


Change to Production:

Improvement
Delivery date
  • API live for PISP Standing Orders

  • API live for CBPII

  • AISP transactions for last 24 hours
 
Implementation of SCA for web and API interfaces 




On-boarding

Supports dynamic client registration (Y/N)

Yes v1.0

The OpenBanking OpenID Dynamic Client Registration Specification - v1.0.0-rc2

Please note that for version 1.0 the required content-type for requests is "application/jwt"

Instructions for manual onboardingNo
OIDC .well-known endpoint

Production endpoints

For Yorkshire Building Society (YBS)

https://api.ybs.co.uk/open-banking/v1.0/.well-known/ybs/openid-configuration

For the Chelsea Building Society brand (CBS)

https://api.ybs.co.uk/open-banking/v1.0/.well-known/che/openid-configuration


Test Facility endpoints

For Yorkshire Building Society

https://sandbox.ybs.co.uk/open-banking/v1.0/.well-known/ybs/openid-configuration

For the Chelsea Building Society brand
https://sandbox.ybs.co.uk/open-banking/v1.0/.well-known/che/openid-configuration


Notes on testing

The Testing Facility is loaded with a set of Sample data which is documented in the following locations.

https://developers.ybs.co.uk/account-api-sample-data

https://developers.ybs.co.uk/payment-and-standing-order-api-sample-data-0

Other on-boarding notes

YBS implementation endopints, certificate support and Security Profile details are documented in the /wiki/spaces/AD/pages/984089014

Documentation URL


Getting Started Guide

https://developers.ybs.co.uk/getting-started

API Documentation

https://developers.ybs.co.uk/apis


AISP Swagger

https://developers.ybs.co.uk/sites/default/files/Account-v3.txt

AISP additional information regarding YBS implementation and capability.

https://developers.ybs.co.uk/exceptions-account-api


PISP Swagger

https://developers.ybs.co.uk/sites/default/files/Payment-v3.txt

PISP additional information regarding YBS implementation and capability.

https://developers.ybs.co.uk/exceptions-payment-and-standing-order-api

Account Information API

Note to ASPSP: Please add a column per brand if relevant

Swagger versionv3.0
Base URI

YBS https://ob-ybs.api.ybs.co.uk/open-banking/v3.0/aisp

CBS https://ob-che.api.ybs.co.uk/open-banking/v3.0/aisp

General variances to specification 

Currently transaction data is only refreshed daily therefore transactions will only be visible the following day.

Our systems log and count the number of AISP requests for each PSU within a 24 hour period measured from midnight to midnight. However, we leave it up to AISPs to declare whether the PSU is present and to count the number of access requests for each PSU in a given 24 hour period and for the AISP to operate within the stated 4 times in a 24 period limit. We believe that our implementation enables the AISP to count the number of unattended access requests in compliance with SCA-RTS Article 36(5). We have not agreed a higher frequency of access requests with any AISPs as allowed by Article 36(5)(b). A TPP can indicate to us that the customer is present by populating the x-fapi-cusotmer-ip-address header if this header is not populated the call is assumed to be unattended and will count against the quota. When the quota has been reached subsequent requests during the period will get a http response code of 429.

Non-functional limitationsYBS do not support eIDAS or eIDAS like certificates currently. 
RefAreaFieldAvailable (Y/N)Exception/Notes (inc details on classification codes, field limits, and field formats)





















Payment Initiation API

Swagger versionv3.0
Base URI

PISP

YBS https://ob-ybs.api.ybs.co.uk/open-banking/v3.0/pisp
CBS https://ob-che.api.ybs.co.uk/open-banking/v3.0/pisp


CBPII

YBS https://ob-ybs.api.ybs.co.uk/open-banking/v3.0/cbpii

CBS https://ob-che.api.ybs.co.uk/open-banking/v3.0/cbpii


General variances to specification

Confirmation of Funds for PISP (and CBPII) and Standing order functionality is not yet available in Production. 

When specifying the Source and Destination accounts for a payment the following restrictions apply

  1. Source Account Number (10 digits) – Destination Account Number (10 digits) for YBS & CBS accounts
  2. Source Account Number (10 digits) – Destination Account Number (8 digits) for external


We currently require all PISP calls to be attended and check this by confirming that the x-fapi-cusotmer-ip-address header has been populated. As all payments require PSU authentication unattended payments are not possible.



Non-functional limitations

Yorkshire Building Society execute payments on a Day +1 so payment execution will be on the day after payment initiation.

YBS do not support eIDAS or eIDAS like certificates currently. 

RefAreaFieldAvailable (Y/N)Exception/Notes (inc details on classification codes, field limits, and field formats)















Open Data API

Swagger versionv1.0
Base URI

https://openapi-ybs.api.ybs.co.uk/open-banking/v1.0/fca-service-metrics/pca

https://openapi-che.api.ybs.co.uk/open-banking/v1.0/fca-service-metrics/pca

General variances to specification YBS have only implemented the FCA Service Metrics endpoint.
Non-functional limitations
RefAreaFieldAvailable (Y/N)Exception/Notes (inc details on classification codes, field limits, and field formats)















  • No labels