...
| Warning |
|---|
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. |
| Page Properties | |||||||||
|---|---|---|---|---|---|---|---|---|---|
| |||||||||
|
Announcements
Improvement | Delivery date |
|---|---|
| |
Implementation of SCA for web and API interfaces 07Implementation of v3.1 |
Change to Production:
Improvement | Delivery date | |
|---|---|---|
Implementation of SCA for web and API interfaces 07Support for OBWAC and OBSEAL certificates Version 3.1 upgrade for AISP, PISP, CBPII and Dynamic Client Registration |
On-boarding
Account Information API
Note to ASPSP: Please add a column per brand if relevant
| Swagger version | v3.01 |
|---|---|
| Base URI | |
| 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. In day transactions will have description detail updated on the subsequent day - Transaction ID will remain consistent |
| Non-functional limitations | YBS do not support eIDAS or eIDAS likecertificates currently. |
| Ref | Area | Field | Available (Y/N) | Exception/Notes (inc details on classification codes, field limits, and field formats) |
|---|---|---|---|---|
Payment Initiation API
| Swagger version | v3. |
|---|
| 1 | |
| Base URI | PISP |
|---|
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- Source Account Number (10 digits) – Destination Account Number (10 digits) for YBS & CBS accounts
- 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 |
|---|
external payments on a Day +1 so payment execution will be on the day after payment initiation. YBS do not support |
eIDAS |
certificates currently. |
| Ref | Area | Field | Available (Y/N) | Exception/Notes (inc details on classification codes, field limits, and field formats) |
|---|---|---|---|---|
Open Data API
| Swagger version | v1.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 |
| Ref | Area | Field | Available (Y/N) | Exception/Notes (inc details on classification codes, field limits, and field formats) |
|---|---|---|---|---|