- Created by Praveen Ponnumony on Jul 12, 2024
You are viewing an old version of this page. View the current version.
Compare with Current View Page History
Version 1 Current »
This Section applies to ASPSPs that have impletemented OB Standards
| -Have you Implemented OB Standards? |
| |
|---|---|---|
| Open Data - Which version have you Implemented? |
| |
Read/Write API Specification Implemented or planning to implement (Lowest version = Current, Highest version = Planned) |
| |
| Read/Write API - Which date are you planning to implement your latest version? | version 4.0 in 2025. | The current Open Banking standard, version 3.1.6, will be updated to version 4.0 in 2025. |
Dynamic Client Registration - Which version have you Implemented or planning to implement? (Lowest version = Current, Highest version = Planned) |
| Dynamic Client Registration is supported and described in the TPP Developer Portal of The Bank of London: https://priora.saltedge.com/docs/open_banking/tbol/v3.1/tpp_onboarding#tpp-register |
| DCR - Which date are you planning to implement your latest version? | 2025. | The latest DCR version will be implemented along with the latest Open Banking standard version in 2025. |
Have you implemented Trusted beneficiaries, if not date planned to Implement? |
| |
Have you implemented Reverse Payments, if not date planned to Implement? |
| |
Have you implemented ECA Standard? |
| |
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? |
| |
Have you implemented VRP – Sweeping, if not date planned to Implement? |
| |
Have you implemented VRP non-Sweeping, if not date planned to Implement? |
| Contact: [enter contact details for the relevant person(s) at your organisation] [You can use this space to provide implementation details relevant to VRP] |
| PISP - Single Payment Limit | £ | |
| PISP - Daily Payment Limit | £ | |
| How many months of transaction do you provide? | ||
| Are you planning to implement TRIs(Transactional Risk Indicator enhancements included in v3.1.10), if so, implementation date? | Not planning to implement | |
| What is your approach to Implementing TRIs? |
| Not applicable |
Which date are you planning on implementing the SCA reauthentication exemption? | SCA reauthentication is not implemented. | Following the FCA recommendation under PS21/19, this dedicated interface enables the SCA exemption under SCA-RTS Article 10A for AISPs. If the AISP creates a consent longer than 90-days, then AISP must reconfirm PSU consent, and must not access information without the PSU actively requesting it unless the PSU has reconfirmed their consent within the previous 90 days. |
|---|---|---|
What is your approach to token management to enable application of the reauthentication exemption? (see link to FCA guidance) | Not applicable | Not applicable as SCA reauthentication is not implemented. |
| Article 10A - Endpoints exempt of SCA-RTS |
| |
| Article 10A - Endpoints not exempt of SCA-RTS |
| |
| Article 10A - Maximum time period after authentication | The dedicated interface enables the SCA exemption under SCA-RTS Article 10A for AISPs, allowing them to create consents that last longer than 90 days. However, AISPs must reconfirm customer consent under Article 36(6) of the SCA-RTS. AISPs must not access information without the customer actively requesting it unless the customer has reconfirmed consent within the previous 90 days. | |
| SCA-RTS implementation status (updated by OBIE PS team only) | IMPLEMENTED | Planned / In-progress / Implemented / TBC |
-Which Security profile have you Implemented or planning to implement? (Lowest version = Current, Highest version = Planned) |
| |
|---|---|---|
| Security Profile - Next Planned Version Implementation Date | ||
| CIBA Profile - Implemented or planning to implement (Lowest version = Current, Highest version = Planned) |
| not applicable |
| CIBA Profile - Next Planned Version Implementation Date | as part of version 4.0 in 2025. | Next planned version of Security Profile will be implemented together with the updated version of Open Banking standard (4.0) in 2025. |
| Security Profile Certification date? | ||
| Token Endpoint Authentication Methods Supported |
| |
| Planned date to Cease support for client id and client secret token endpoint authentication | ||
| POST-BREXIT POST TRANSITION - Certificates Accepted (from 1st Jul 2021) |
|
-What is your approach to Implementing OBIE Customer Experience Guidelines (CEG)? (tick all that apply) |
| |
|---|---|---|
Which version have you implemented or planning to implement? (Lowest version = Current, Highest version = Planned) |
| |
| Which date are you planning to implement your latest CEG version? | version 4.0 in 2025. | The latest version of CEG will be implemented together with the updated 4.0 version in 2025. |
| Redirection Model |
|
| -Which Directory are you using as your Trust Framework? | Open Banking Directory | |
|---|---|---|
| Are you caching the Directory? | Yes | |
| Transaction IDs Supported | Yes |
|
Are you enrolled to Dispute Management System? |
| |
Are you Seeking Fallback Exemption? |
| The Bank of London will be applying for Exemption from providing a fallback mechanism. |
| Article 10 - Maximum time period after authentication | The maximum time period for fetching account information after authentication is indicated in the `ExpirationDateTime` parameter included in the /consent request. | Please specify how long the AISP has from the time when they receive the access token (after PSU authentication). This is the period the AISP must submit their first request before SCA will be re-applied to endpoints NOT exempt of SCA under Article 10. ASPSPs should consider that this timeline is consistent with the time limit applied by the ASPSP in the existing online PSU interface (i.e. before the PSU is logged out) |
| Article 10 - Endpoints exempt of SCA | AIS endpoints Transactions: | |
| Major Milestones | Transition to updated version of Open Banking standard 4.0 in 2025 | |
| Brand(s) | The Bank of London Group Limited |
Location of Well Known Endpoints | https://priora.saltedge.com/docs/open_banking/tbol/v3.1/open_id#wellknown-well-known | The Well Known Endpoints are located in the TPP Developer Portal on the OpenID page. |
|---|---|---|
Modified Customer Interface URL (if applicable) | Not applicable | Not applicable as Bank of London after 6 months after Live launch will apply for Exemption for the fallback channel. |
| Dev Portal URL | https://priora.saltedge.com/docs/open_banking/tbol/v3.1 | |
| Test Facility URL | https://priora.saltedge.com/docs/open_banking/tbol/v3.1 | The Test Facility URL can be found in the TPP Developer Portal in the “Sandbox” section. Provider code for tests - tbol_sandbox |
| Brand Landing Pages URL | https://thebankoflondon.com/ | [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) | compliance@saltedge.com |
- No labels