ASPSP	TSB Bank Plc
Brand	TSB
Date	22nd July 2019
Developer portal (s)	Sandbox: https://developer.tsb.co.uk Production: https://apis.developer.tsb.co.uk

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.

Announcements

Change to Production:

Improvement	Delivery date

On-boarding

Supports dynamic client registration (Y/N)	Y
Instructions for manual onboarding	Sandbox Only https://developer.tsb.co.uk/start Note: Open Banking developer must log in using the 'Open Banking Log In' button, which requires an Open Banking login - See 'How to Enrol' guide on Open Banking website: https://openbanking.org.uk/directory/
OIDC .well-known endpoint	Sandbox: https://sandbox.tsb.co.uk/sandbox/openbanking/.well-known/openid-configuration Production: https://apis.tsb.co.uk/apis/open-banking/v3.1/.well-known/openid-configuration
Notes on testing
Other on-boarding notes	New Organisations onboarding will automatically be subscribed to a holding plan (limited daily calls) until we can review your application. Once reviewed successfully we'll then promote you to our standard plan which enables you to consume our APIs fully. Please contact us for further information if required.
Documentation URL	Sandbox: https://developer.tsb.co.uk Production: https://apis.developer.tsb.co.uk

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

Swagger version	v3.1.0
Base URI	Sandbox: https://sandbox.tsb.co.uk/sandbox/openbanking/open-bankng/v3.1/ Production: https://apis.tsb.co.uk/apis/open-banking/v3.1/
General variances to specification
Non-functional limitations

Ref	Area	Field	Available (Y/N)	Exception/Notes (inc details on classification codes, field limits, and field formats)

Swagger version	v3.1.0
Base URI	Sandbox: https://sandbox.tsb.co.uk/sandbox/openbanking/open-banking/v3.1/ Production: Coming Soon
General variances to specification	GET/domestic-payments/{DomesticPaymentID} returns a 500 response when using a Client Credentials Grant Access Token. The interim workaround is to use the Access Token granted from the Authorization Code exchange (or use the Refresh Token to generate a new Access Token).
Non-functional limitations

Ref	Area	Field	Available (Y/N)	Exception/Notes (inc details on classification codes, field limits, and field formats)

Swagger version	N/A
Base URI	N/A
General variances to specification	N/A
Non-functional limitations	N/A

Ref	Area	Field	Available (Y/N)	Exception/Notes (inc details on classification codes, field limits, and field formats)