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
You’ll find the full list of the API endpoints that we support in the API section of this site.
Once a customer has provided consent, the Authorization Code we issue will be valid for 60 seconds.
We support Open Banking ETSI -like certificates and eIDAS certificates (QWAC and QSEAL) . We will support Open Banking legacy certificates until the end of the adjustment period on 30 June 2021.
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 firstname.lastname@example.org.
You’ll find all you need to know about accessing our test environment on our Open Banking Implementation Guide.
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.
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.
No, our test data is static. For example, any payments made from a test account will not affect the account balance.
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.
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.
Yes, we take part in the Open Banking Dispute System. Find out more
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.
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.
We will use the Open Banking Service Desk to cascade information regarding outages or performance degradation to all TPPs.