- Created by Adam Pretlove , last modified by Marcin Pieniążek on Nov 18, 2024
You are viewing an old version of this page. View the current version.
Compare with Current View Page History
« Previous Version 93 Next »
This Section applies to ASPSPs that have implemented 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? | v4.0 Read/Write API delivery on or after includes all endpoints for AIS, PIS Domestic (SIP, FDP, SO), Confirmation of funds (CBPII). Sweeping VRPs and PIS International expected in Q1 2025, will be confirmed in a future update. | |
Have you implemented v4.0 information flows, if not date planned to Implement? |
| |
Dynamic Client Registration - Which version have you Implemented or planning to implement? (Lowest version = Current, Highest version = Planned) |
| |
| DCR - Which date are you planning to implement your latest version? | ||
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 | NA | |
Have you implemented Bulk/File Payments? |
| |
Have you implemented VRP – Sweeping, if not date planned to Implement? |
| MRO completed, VRP - Sweeping now live |
Have you implemented VRP non-Sweeping, if not date planned to Implement? |
| Contact: nav.khan@hsbc.com; marcin.pieniazek@hsbc.com |
| PISP - Single Payment Limit | - | For the latest details on payment limits, refer to our Implementation Guide on our Dev Portal. |
| PISP - Daily Payment Limit | - | For the latest details on payment limits, refer to our Implementation Guide on our Dev Portal. |
| How many months of transaction do you provide? | PCA and Savings - 6 years; Credit Cards – 18 months billed and 1 month unbilled | |
| Have you implemented TRIs (Transactional Risk Indicators), if not, date planned to Implement? | ||
| What is your approach to Implementing TRIs? |
|
Which date are you planning on implementing the SCA reauthentication exemption? | Implemented on 22/08/2022 | |
|---|---|---|
What is your approach to token management to enable application of the reauthentication exemption? (see link to FCA guidance) | Issue a long-lived refresh token during one final SCA | - Any AIS consents created after the Implementation Date will no longer need to be re-authenticated every 90 days; their access expiry date will be the same as the consent expiry date, if one is provided - For any pre-existing consents, the same will apply the first time re-authentication takes place after the Implementation Date. For example, if a customer re-authenticates a pre-existing consent in November 2022, the access expiry date will be aligned to the consent expiry date, if one is provided - Consent Expiry Date is an optional field. If consent expiry date is not populated, the consent will never expire (unless revoked by the TPP). If consent expiry date is populated, its maximum value must be before 19/01/2038. Any value above 19/01/2038 will get 500 Internal Server Error (ErrorCode\":\"UK.OBIE.UnexpectedError\",\"Message\":\"Consent Exception) - In line with HSBC’s current implementation, access and refresh tokens will continue to be used. Access tokens will continue to have a TTL of 60 minutes. The expiry date for refresh tokens issued after the Implementation Date will be aligned to the consent expiry date, if one is provided. If a consent expiry date is not provided, refresh tokens issued after the Implementation Date will not expire - There will be no change to the data clusters available to TPPs without customer present. For the avoidance of doubt, only Balances and Transactions less than 90 days’ old will be accessible without customer present. All other data points will only be available within 60 minutes after SCA |
| Article 10A - Endpoints exempt of SCA-RTS |
| |
| Article 10A - Endpoints not exempt of SCA-RTS |
| |
| Article 10A - Maximum time period after authentication | 60 minutes | Please specify the time period in minutes |
| SCA-RTS implementation status (updated by OBL 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) |
| On the 14th November 2024, HSBC updated its FAPI-defined endpoints (/token, /authorize) to the OIDF FAPI 1.0 – Advanced specification. HSBC will maintain a period of backwards compatibility with FAPI 1.0 Implementers Draft 2 for these endpoints. This means that HSBC will start validating fields specified in FAPI 1.0 – Advanced, if they are provided by TPPs (for example the ‘nbf’ claim), but will not reject requests where they are not provided. To ensure no disruption to service, TPPs must check they support the default character encoding of UTF-8 for API responses, as is already specified in the Read / Write standard. HSBC will no longer return the default encoding in its API response headers. These changes apply to both the v3.1.11 and v4.0 (once deployed) implementations. FAPI endpoints will be updated on our sandbox, on or after 09th December 2024. The sandbox will not provide backwards compatibility. IMPORTANT: Backwards compatibility for FAPI 1.0 Implementers Draft 2 will cease on 14th February 2025 across both v3.1.11 and v4.0 implementations. At that point, TPP alignment to FAPI 1.0 Final will become mandatory, and HSBC will enforce the provision of fields specified in FAPI 1.0 Final (such as the ‘nbf’ claim) by TPPs. |
|---|---|---|
| Security Profile - Next Planned Version Implementation Date | ||
| CIBA Profile - Implemented or planning to implement (Lowest version = Current, Highest version = Planned) |
| |
| CIBA Profile - Next Planned Version Implementation Date | ||
| 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 OBL 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? |
| |
| Redirection Model |
|
| -Which Directory are you using as your Trust Framework? | Open Banking | |
|---|---|---|
| Are you caching the Directory? | No | |
| Transaction IDs Supported | - Option 2 Implemented | HSBC generates a Unique Transaction ID from a set of Immutable fields, which is then passed on to TPPs via the API |
Are you Seeking Fallback Exemption? |
| |
| Article 10 - Maximum time period after authentication | 60 minutes | |
| Article 10 - Endpoints exempt of SCA | Accounts. Balances. Transactions (last 90 days only) | |
| Major Milestones | ||
| Brand(s) |
Location of Well Known Endpoints | OB Technical Directory | |
|---|---|---|
Modified Customer Interface URL (if applicable) | ||
| Dev Portal URL | https://develop.hsbc.com/ | |
| Test Facility URL | https://develop.hsbc.com/ | |
| Brand Landing Pages URL | [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) | openbankingsupport@hsbc.com |
High Cost Credit | Implemented |
|---|
- No labels