Frequently asked questions

Our APIs

How do I register my app to use Tesco Bank APIs?

We only support dynamic app registration through our APIs – there’s no manual process for this. You’ll find all the details you need on our Implementation Guide

    What Open Banking APIs does Tesco Bank support?

    You’ll find the full list of the API endpoints that we support in the API section of this site.

      How long is the Authorization Code valid for?

      Once a customer has provided consent, the Authorization Code we issue will be valid for 60 seconds.

        What certificates are supported?

        We support Open Banking ETSI -like certificates (OBWAC and OBSEAL) and eIDAS certificates (QWAC and QSEAL).

          Why do I get the error message "The software statement does not match the network certificate" when I try to register with you?

          This is probably because of the way that the roles are formatted in your certificate. Under the ETSI standard, s5.2 defines that RolesOfPSP must be a sequence of RoleOfPSP, which is a sequence of roleOfPspOid, roleOfPspName. We do not accept multiple roles being supplied in one sequence. If that doesn't resolve the error then please contact us at

            Testing with us

            How do I access your test environment?

            You’ll find all you need to know about accessing our test environment on our Open Banking Implementation Guide.

              How do I register to use your test environment?

              Just like our production environment, we only support dynamic app registration through our APIs. You’ll need to hold valid OBIE certification in order to register your app with our test environment.

                What will I be able to test?

                You’ll be able to test all of the API endpoints that are available in our production environment, with the exception of the customer authentication flow, which has been amended for testing purposes. You’ll also be able to query our static test data and invoke all error responses.​

                  Can I see dynamic changes to the test data?

                  No, our test data is static. For example, any payments made from a test account will not affect the account balance.

                    Do you have any limits on how often or when I can use the test environment?

                    We won’t limit your usage time or the number of API calls to the test environment and we do our best to ensure it’s available around the clock. We’ll let you know in advance about any planned maintenance via the support section. To make sure we can provide a stable and reliable test environment for all of our users, we ask that you use the test environment for integration testing only.


                      How do I get in touch with you if I have a query?

                      The easiest way to get in touch is to email us. You’ll need to be enrolled with the Open Banking Directory for us to be able to provide you with any technical API support and we currently only provide support in English.​

                        What information do I need to provide in my email?

                        If you’re emailing us with a technical query, please provide: organisation name, date / time of occurrence, summary of the issue, API name and version impacted by the issue.

                          When will you respond to my email?

                          We’ll always get back to you as quickly as possible. Our response time will be based on the information that you’ve provided in your email. We’ll usually assign your email a rating and let you know when you can expect to hear from us once we’ve reviewed your query ticket.

                            How will you let me know if the channel is not working or has performance issues?

                            We will use the Open Banking Service Desk to cascade information regarding outages or performance degradation to all TPPs.