HSBC Corporate (HSBCnet)

OB Standards

This Section applies to ASPSPs that have implemented OB Standards

-Have you Implemented OB Standards?	Yes No
Open Data - Which version have you Implemented?	None V2.2 V2.3 V2.4
Read/Write API Specification Implemented or planning to implement (Lowest version = Current, Highest version = Planned)	V3.0 V3.1 V3.1.1 V3.1.2 V3.1.3 V3.1.4 V3.1.5 V3.1.6 V3.1.7 V3.1.8 V3.1.9 V3.1.10 V3.1.11 V4.0
Read/Write API - Which date are you planning to implement your latest version?
Have you implemented v4.0 information flows, if not date planned to Implement?	Already Implemented Planning to implement Not planning to implement
Dynamic Client Registration - Which version have you Implemented or planning to implement? (Lowest version = Current, Highest version = Planned)	None V3.1 V3.2 V3.3
DCR - Which date are you planning to implement your latest version?
Have you implemented Trusted beneficiaries, if not date planned to Implement?	Already Implemented Planning to implement Not planning to implement
Have you implemented Reverse Payments, if not date planned to Implement?	Already Implemented Planning to implement Not planning to implement
Have you implemented ECA Standard?	Already Implemented Planning to implement Not planning to implement
ECA Implementation details	NA
Have you implemented Bulk/File Payments?	Already Implemented Planning to implement Not planning to implement
Have you implemented VRP – Sweeping, if not date planned to Implement?	Already Implemented Planning to implement Not planning to implement
Have you implemented VRP non-Sweeping, if not date planned to Implement?	Already Implemented Planning to implement Not planning 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?	Current Accounts and Currency Accounts - From the start of the previous year (Note: In Q2 of each year, data going further back than the start of the previous year, will become unavailable. For example: from Q2 2024 only data from January 2023 onwards will be returned) Credit Cards and Global Wallet - 12 months
Have you implemented TRIs (Transactional Risk Indicators), if not, date planned to Implement?
What is your approach to Implementing TRIs?	Accept payload with TRI fields – Process all fields Accept payload with TRI fields – Ignore all fields Reject payload with TRI fields – Error back to TPP Accept payload with TRI fields – Process few fields (Provide list of accepted fields)	Please refer to our Developer Portal (https://develop.hsbc.com/) where you can access our Implementation Guide which includes fields we do and don't support.

SCA-RTS 90-day reauth Implementation

Which date are you planning on implementing the SCA reauthentication exemption?	Implemented on 27/04/2023
What is your approach to token management to enable application of the reauthentication exemption? (see link to FCA guidance)	TBC	- 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	Accounts Transactions (90days) Balances Standing orders Direct debits Beneficiaries Products Offers Parties Scheduled Payments Statements
Article 10A - Endpoints not exempt of SCA-RTS	Transactions (more than 90days) Standing orders Direct debits Beneficiaries Products Offers Parties Scheduled Payments Statements
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)		Planned / In-progress / Implemented / TBC

Security Profile

-Which Security profile have you Implemented or planning to implement? (Lowest version = Current, Highest version = Planned)	OB Security Profile (Legacy) FAPI (ID2) FAPI 1 Advanced Other (Please define)
Security Profile - Next Planned Version Implementation Date
CIBA Profile - Implemented or planning to implement (Lowest version = Current, Highest version = Planned)	None CIBA CIBA FAPI Profile
CIBA Profile - Next Planned Version Implementation Date
Security Profile Certification date?
Token Endpoint Authentication Methods Supported	client_secret_post client_secret_basic client_secret_jwt tls_client_auth Private_key_jwt
Planned date to Cease support for client id and client secret token endpoint authentication	31 Aug 2020
POST-BREXIT POST TRANSITION - Certificates Accepted (from 1st Jul 2021)	eIDAS QWAC eIDAS QSealC OB legacy (obtransport, obsigning) OBWAC OBSeal Other (Please define)

Customer Journey

-What is your approach to Implementing OBL Customer Experience Guidelines (CEG)? (tick all that apply)	Already Implemented Planning to implement or upgrade Not planning to implement CEG
Which version have you implemented or planning to implement? (Lowest version = Current, Highest version = Planned)	V3.1.2 V3.1.3 V3.1.4 V3.1.5 V3.1.6 V3.1.7 V3.1.8 V3.1.9 V3.1.10 V3.1.11 V4.0
Which date are you planning to implement your latest CEG version?
Redirection Model	App to App redirection Decoupled authentication Embedded Flow Bespoke User Journeys

PSD2

-Which Directory are you using as your Trust Framework?	Open Banking
Are you caching the Directory?	No
Transaction IDs Supported	01 Feb 2021	HSBC generates a Unique Transaction ID from a set of Immutable fields, which is passed on to TPPs via the AP
Are you Seeking Fallback Exemption?	Yes No
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)

ASPSP Dev Portal and Contact Details

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

Key Implementations

High Cost Credit	N/A