Certificate Renewal and Updates

This guide explains how to update and renew certificates for your bank registrations to maintain compliance with Open Banking requirements.

UK Certificates

OB_Seal, OB_Wac: These certificates can be generated through the Open Banking portal, provided your organisation is registered within the platform.

EU Certificates

Q_Seal, Q_Wac: These certificates must be purchased from a qualified and trusted QTSP (Qualified Trust Service Provider).

Ensuring you have valid and up-to-date certificates is essential for maintaining compliance with PSD2 regulations.

Getting Started

Prior to updating your certificates, we strongly recommend creating a test application within the Yapily Console. This allows you to thoroughly test the registration process for each banking group, minimising the risk of unforeseen impacts on your live application. Testing one institution per banking group is sufficient to ensure a smooth transition and prevent disruptions in your live environment. Please refer to the registration update process and its impact on consents outlined below for each banking group:

Country	Bank Group/Institution	Update Process	Downtime	Consent Impact	Bank SLAs if applicable	Developer Portal Link
Germany	N/A	Changing the certificates on Yapily UI is enough, this needs to be done for every institution. Process: Open your application on Yapily Console, find the German institution you want to update and press edit when found, change the certificates by using the dropdown and select the new ones, once done, press save registration.	N/A	No impact, unless the organisation identifier changes due to a re-brand or similar which would require a new registration	N/A	N/A
France	BPCE	Changing the certificates on Yapily UI is enough, this needs to be done for every institution from the group manually. Process: Open your application on Yapily Console, find the BPCE institution you want to update and press edit when found, change the certificates by using the dropdown and select the new ones, once done, press save registration.	N/A	No impact, unless the organisation identifier changes due to a re-brand or similar which would require a new registration	N/A	N/A
France	Arkea	To renew the certificates, you will need to change them on the Yapily Console UI, and go to the banks developer portal, where you have created applications for each Arkea group institution, there you will need to change the certificate chain for each institution and save, once saved, go to Yapily Console, and change the certificates there, the change should be immediate. Please keep in mind that there might be some downtime, as when you change the certificates on the developer portal the registration might stop working until you change the certificates on the Yapily UI	~15-30 Min downtime, until all the steps are completed, and the changes take effect.	As long as the credentials remain the same there will be no impact to consents.	N/A	https://getarkea.com/en/
France	Societe Generale	To renew the certificates you will need to login to the developer portal and update the certificates there, once updated go to Yapily Console and change the certificates there for each registration. please keep in mind that there might be some downtime, as when you change the certificates on the developer portal the registration might stop working until you change the certificates on the Yapily UI	~15-30 Min downtime, until all the steps are completed, and the changes take effect.	As long as the credentials remain the same there will be no impact to consents.	N/A	https://developer.societegenerale.fr/en/sb
France	Credit Agricole	To renew the certificates you will need to change them on Yapily UI, once the certificates are changed from the dropdown, a re-register button will appear, press it. This will make a PUT call to the bank, and update the certificates. This re-register button only needs to be done for one institutions from the group, once it is done, proceed with changing the other institutions in the group, but now it is enough to change the certificates, and press the “save existing registration”	N/A	As long as the credentials remain the same there will be no impact to consents.	N/A	N/A
France	LabanquePostale	To renew the certificate, it is enough to change them in the Yapily Console UI, by editing the registration and saving it. You do not have any specific action to deal with La Banque Postale as long as the following elements remain unchanged: - providerLegalId (accreditation number / global URN) - certificate authority (eIDAS certificate provider)	N/A	No impact to consents if the credentials remain the same and the global URN and certificate provider is the same.	2-5 days, depending on bank response.	N/A
France	BNP	To renew the certificate, it is enough to change them in the Yapily Console UI, by editing the registration, assigning the new certificates, and saving it.	N/A	No impact to consents. If the DN of the new certificate is identical to the DN of the current certificate, the consents granted for AIS will remain valid (until they reach their end-date).	N/A	N/A
Austria	N/A	To renew the certificate, it is enough to change them in the Yapily Console UI, by editing the registration, assigning the new certificates, and saving it.	N/A	No impact to consents as long as the Organisation Identifier remains the same.	N/A	N/A
Belgium	Belfius	To renew the certificates, you will need to send an email to Belfius and attach the public part of the certificates, they will add it on their side and you will be able to use the old certificates until they expire, and the new ones once they inform you that it has been added on their side.	N/A	No impact to consents.	1-3 days.	N/A
Belgium	KBC Belgium	To renew the certificate, it is enough to change them in the Yapily Console UI, by editing the registration, assigning the new certificates, and saving it.	N/A	No impact to consents.	N/A	N/A
Belgium	BNP Paribas	To renew the certificate, it is enough to change them in the Yapily Console UI, by editing the registration, assigning the new certificates, and saving it.	N/A	If the DN of the new certificate is identical to the DN of the current certificate, the consents granted for AIS will remain valid (until they reach their end-date).	N/A	N/A
Baltics	SEB Baltics (Estonia, Latvia, Lithuania)	To renew the certificate, it is enough to change them in the Yapily Console UI, by editing the registration, assigning the new certificates, and saving it.	N/A	No impact to consents.	N/A	N/A
Ireland	AIB	To renew the certificates, you will need to assign the new certificates in the Open Banking Directory organisation to the used Software Statement for the registration, once they are assigned, you can move forward to the Yapily UI, and change the certificates there on the registration, once done, save the registration.	N/A	No impact to consents if the registration software Statement ID remains the same.	N/A	N/A
Ireland	PTSB	To renew the certificates, you will need to assign the new certificates in the Open Banking Directory organisation to the used Software Statement for the registration, once they are assigned, you can move forward to the Yapily UI, and change the certificates there on the registration, once done, save the registration.	N/A	No impact to consents if the registration software Statement ID remains the same.	N/A	N/A
Italy	All Groups	To renew the certificate, it is enough to change them in the Yapily Console UI, by editing the registration, assigning the new certificates, and saving it.	N/A	No impact to consents.	N/A	N/A
Netherlands	ABN Amro	To renew the certificates you will need to login to the developer portal and raise a ticket with a change request for the certificates, ABN amro will provide a time slot when the certificates will be changed, once confirmation is received and certs are updated from their side go to Yapily Console and change the certificates there for each registration. please keep in mind that there might be some downtime, as when you change the certificates on the developer portal the registration might stop working until you change the certificates on the Yapily UI	~15-30 Min downtime, until all the steps are completed, and the changes take effect.	As long as the credentials remain the same there will be no impact to consents.	N/A	https://developer.abnamro.com/
Netherlands	Rabobank	To renew the certificates you will need to login to the developer portal and update the certificates there, once updated go to Yapily Console and change the certificates there for each registration. please keep in mind that there might be some downtime, as when you change the certificates on the developer portal the registration might stop working until you change the certificates on the Yapily UI	~15-30 Min downtime, until all the steps are completed, and the changes take effect.	As long as the credentials remain the same there will be no impact to consents.	N/A	https://developer.rabobank.nl/
Netherlands	Devolksbank	To renew the certificate, it is enough to change them in the Yapily Console UI, by editing the registration, assigning the new certificates, and saving it.	N/A	As long as the credentials remain the same there will be no impact to consents.	N/A
Nordics	BankData	To re-new BankData institutions you will have to send your new QWAC eIDAS to BankDara and schedule a time and date for the change. If your new QWAC eIDAS is issued by another QTSP than your current QWAC eIDAS, please inform them as soon as possible as they might have to install a full certificate chain with their IT partners. Once you receive confirmation from them that the certificate is changed, you will need to change the certificates on the Yapily UI.	~15-30 Min downtime, until all the steps are completed, and the changes take effect. 1-2 days to get a response from them to schedule the change window.	All consent-tokens will expire.		Email: api-dev-support@bankdata.dk
Nordics	BEC	To renew the certificates for BEC, you will need to enrol with the bank again, by doing a dynamic registration for each institution so that the new certificates are added. Both registrations will work until certificate expiry, but for the new registration, new consents will have to be created, for the old registration, consents will still be active until expiration date.	N/A	New consents will need to be generated for the new registration, active consents will still be usable while using old registration details.	N/A	N/A
Nordics	DNB	To renew the certificate, it is enough to change them in the Yapily Console UI, by editing the registration, assigning the new certificates, and saving it.	N/A	No impact to consents.	N/A	N/A
Nordics	Luminor	To renew the certificate, it is enough to change them in the Yapily Console UI, by editing the registration, assigning the new certificates, and saving it.	N/A	No impact to consents.	N/A	N/A
Nordics	Nordea	To renew the certificate, it is enough to change them in the Yapily Console UI, by editing the registration, assigning the new certificates, and saving it.	N/A	No impact to consents.	N/A	N/A
Nordics	SEB Sweden	To renew the certificates, you will need to send an email to SEB and attach the public part of the certificates, they will check on their side if any additional steps are needed, if so will add it on their side. Once confirmation is received from them, you will need to change the certificates on Yapily UI.	Possible ~30 min downtime, from when email is received and the certificates on Yapily UI are changed.	No impact to consents.	1-3 days.	openbanking@seb.lt
Nordics	Swedbank (Lithuania, Sweden, Latvia and Estonia)	To renew the certificate, it is enough to change them in the Yapily Console UI, by editing the registration, assigning the new certificates, and saving it.	N/A	No impact to consents.	N/A	N/A
Portugal	SIBS	To renew the certificate, it is enough to change them in the Yapily Console UI, by editing the registration, assigning the new certificates, and saving it.	N/A	No impact to consents.	N/A	N/A
Spain	Redsys	To renew the certificate, it is enough to change them in the Yapily Console UI, by editing the registration, assigning the new certificates, and saving it.	N/A	No impact to consents.	N/A	N/A
Sweden	Skandia	To renew the certificate, it is enough to change them in the Yapily Console UI, by editing the registration, assigning the new certificates, and saving it.	N/A	No impact to consents, unless a new application is created and different credentials used.	N/A	N/A
UK Institutions below:
UK	AIB	To renew the certificates, you will need to upload the new certificates to the Open Banking Directory, and associate them to the currently used Software Statement ID. Once done, it is enough to change them in the Yapily Console UI, by editing the registration, assigning the new certificates, and saving it.	N/A	No impact to consents, unless a new application is created on the developer portal, which would be considered a new registration with new credentials, as the consents and registration is tied to the client_id.	N/A	https://developer.aibgb.co.uk/
UK	Barclays	To renew the certificates, you will need to upload the new certificates to the Open Banking Directory, and associate them to the currently used Software Statement ID. Once done, it is enough to change them in the Yapily Console UI, by editing the registration, assigning the new certificates, and saving it.	N/A	No impact to consents, unless a new application is created on the developer portal, which would be considered a new registration with new credentials, as the consents and registration is tied to the client_id.	N/A	https://developer.barclays.com/
UK	BOI	To renew the certificates, you will need to upload the new certificates to the Open Banking Directory, and associate them to the currently used Software Statement ID. Once done, it is enough to change them in the Yapily Console UI, by editing the registration, assigning the new certificates, and saving it.	N/A	No impact to consents, unless a new Software Statement ID is used, which would be considered a new registration with new credentials, as the consents and registration is tied to the Software Statement ID.	N/A	N/A
UK	Capital One	To renew the certificates, you will need to upload the new certificates to the Open Banking Directory, and associate them to the currently used Software Statement ID. Once done, it is enough to change them in the Yapily Console UI, by editing the registration, assigning the new certificates, and saving it.	N/A	No impact to consents, unless a new Software Statement ID is used, which would be considered a new registration with new credentials, as the consents and registration is tied to the Software Statement ID.	N/A	N/A
UK	Cash Plus	To renew the certificates, you will need to upload the new certificates to the Open Banking Directory, and associate them to the currently used Software Statement ID. Once done, it is enough to change them in the Yapily Console UI, by editing the registration, assigning the new certificates, and saving it.	N/A	No impact to consents, unless a new Software Statement ID is used, which would be considered a new registration with new credentials, as the consents and registration is tied to the Software Statement ID.	N/A	N/A
UK	YBS	To renew the certificates, you will need to upload the new certificates to the Open Banking Directory, and associate them to the currently used Software Statement ID. Once done, it is enough to change them in the Yapily Console UI, by editing the registration, assigning the new certificates, and saving it.	N/A	No impact to consents, unless a new Software Statement ID is used, which would be considered a new registration with new credentials, as the consents and registration is tied to the Software Statement ID.	N/A	N/A
UK	Cumberland Building Society	To renew the certificates, you will need to upload the new certificates to the Open Banking Directory, and associate them to the currently used Software Statement ID. Once done, it is enough to change them in the Yapily Console UI, by editing the registration, assigning the new certificates, and saving it.	N/A	No impact to consents, unless a new Software Statement ID is used, which would be considered a new registration with new credentials, as the consents and registration is tied to the Software Statement ID.	N/A	N/A
UK	CYBG	To renew the certificates, you will need to upload the new certificates to the Open Banking Directory, and associate them to the currently used Software Statement ID. Once done, it is enough to change them in the Yapily Console UI, by editing the registration, assigning the new certificates, and saving it.	N/A	No impact to consents, unless a new Software Statement ID is used, which would be considered a new registration with new credentials, as the consents and registration is tied to the Software Statement ID.	N/A	N/A
UK	Danske Bank	To renew the certificates, you will need to upload the new certificates to the Open Banking Directory, and associate them to the currently used Software Statement ID. Once done, it is enough to change them in the Yapily Console UI, by editing the registration, assigning the new certificates, and saving it.	N/A	No impact to consents, unless a new Software Statement ID is used, which would be considered a new registration with new credentials, as the consents and registration is tied to the Software Statement ID.	N/A	N/A
UK	Handelsbanken	To renew the certificates, you will need to upload the new certificates to the Open Banking Directory, and associate them to the currently used Software Statement ID. Once done, it is enough to change them in the Yapily Console UI, by editing the registration, assigning the new certificates, and saving it.	N/A	No impact to consents, unless a new Software Statement ID is used, which would be considered a new registration with new credentials, as the consents and registration is tied to the Software Statement ID.	N/A	N/A
UK	Hoare	To renew the certificates, you will need to upload the new certificates to the Open Banking Directory, and associate them to the currently used Software Statement ID. Once done, it is enough to change them in the Yapily Console UI, by editing the registration, assigning the new certificates, and saving it.	N/A	No impact to consents, unless a new Software Statement ID is used, which would be considered a new registration with new credentials, as the consents and registration is tied to the Software Statement ID.	N/A	N/A
UK	HSBC	To renew the certificates, you will need to upload the new certificates to the Open Banking Directory, and associate them to the currently used Software Statement ID. Once done, it is enough to change them in the Yapily Console UI, by editing the registration, assigning the new certificates, and saving it.	N/A	No impact to consents, unless a new Software Statement ID is used, which would be considered a new registration with new credentials, as the consents and registration is tied to the Software Statement ID.	N/A	N/A
UK	Lloyds Banking Group	To renew the certificates, you will need to upload the new certificates to the Open Banking Directory, and associate them to the currently used Software Statement ID. Once done, it is enough to change them in the Yapily Console UI, by editing the registration, assigning the new certificates, and saving it.	N/A	No impact to consents, unless a new Software Statement ID is used, which would be considered a new registration with new credentials, as the consents and registration is tied to the Software Statement ID.	N/A	N/A
UK	Monzo	To renew the certificates, you will need to upload the new certificates to the Open Banking Directory, and associate them to the currently used Software Statement ID. Once done, it is enough to change them in the Yapily Console UI, by editing the registration, assigning the new certificates, and saving it.	N/A	No impact to consents, unless a new Software Statement ID is used, which would be considered a new registration with new credentials, as the consents and registration is tied to the Software Statement ID.	N/A	N/A
UK	Nationwide Building Society	To renew the certificates, you will need to upload the new certificates to the Open Banking Directory, and associate them to the currently used Software Statement ID. Once done, it is enough to change them in the Yapily Console UI, by editing the registration, assigning the new certificates, and saving it.	N/A	No impact to consents, unless a new Software Statement ID is used, which would be considered a new registration with new credentials, as the consents and registration is tied to the Software Statement ID.	N/A	N/A
UK	Payoneer	To renew the certificates, you will need to upload the new certificates to the Open Banking Directory, and associate them to the currently used Software Statement ID. Once done, it is enough to change them in the Yapily Console UI, by editing the registration, assigning the new certificates, and saving it.	N/A	No impact to consents, unless a new application is created on the developer portal, which would be considered a new registration with new credentials, as the consents and registration is tied to the client_id.	N/A	https://developer.payoneer.com/psd2/home
UK	PayPal	To renew the certificates, you will need to upload the new certificates to the Open Banking Directory, and associate them to the currently used Software Statement ID. Once done, it is enough to change them in the Yapily Console UI, by editing the registration, assigning the new certificates, and saving it.	N/A	No impact to consents, unless a new application is created on the developer portal, which would be considered a new registration with new credentials, as the consents and registration is tied to the client_id.	N/A	https://developer.paypal.com/home/
UK	RBSG	To renew the certificates, you will need to upload the new certificates to the Open Banking Directory, and associate them to the currently used Software Statement ID. Once done, it is enough to change them in the Yapily Console UI, by editing the registration, assigning the new certificates, and saving it.	N/A	No impact to consents, unless a new Software Statement ID is used, which would be considered a new registration with new credentials, as the consents and registration is tied to the Software Statement ID.	N/A	N/A
UK	Revolut	To renew the certificates, you will need to upload the new certificates to the Open Banking Directory, and associate them to the currently used Software Statement ID. Once done, it is enough to change them in the Yapily Console UI, by editing the registration, assigning the new certificates, and saving it.	N/A	No impact to consents, unless a new Software Statement ID is used, which would be considered a new registration with new credentials, as the consents and registration is tied to the Software Statement ID.	N/A	N/A
UK	Sainsbury’s Bank PLC	To renew the certificates, you will need to upload the new certificates to the Open Banking Directory, and associate them to the currently used Software Statement ID. Once done, it is enough to change them in the Yapily Console UI, by editing the registration, assigning the new certificates, and saving it.	N/A	No impact to consents, unless a new Software Statement ID is used, which would be considered a new registration with new credentials, as the consents and registration is tied to the Software Statement ID.	N/A	N/A
UK	Santander	To renew the certificates, you will need to upload the new certificates to the Open Banking Directory, and associate them to the currently used Software Statement ID. Once done, it is enough to change them in the Yapily Console UI, by editing the registration, assigning the new certificates, and saving it.	N/A	No impact to consents, unless a new application is created on the developer portal, which would be considered a new registration with new credentials, as the consents and registration is tied to the client_id.	N/A	https://developer.santander.co.uk/sanuk/external/
UK	Starling Bank	To renew the certificates, you will need to upload the new certificates to the Open Banking Directory, and associate them to the currently used Software Statement ID. Once done, it is enough to change them in the Yapily Console UI, by editing the registration, assigning the new certificates, and saving it.	N/A	No impact to consents, unless a new Software Statement ID is used, which would be considered a new registration with new credentials, as the consents and registration is tied to the Software Statement ID.	N/A	N/A
UK	Tesco bank	To renew the certificates, you will need to upload the new certificates to the Open Banking Directory, and associate them to the currently used Software Statement ID. Once done, it is enough to change them in the Yapily Console UI, by editing the registration, assigning the new certificates, and saving it.	N/A	No impact to consents, unless a new Software Statement ID is used, which would be considered a new registration with new credentials, as the consents and registration is tied to the Software Statement ID.	N/A	N/A
UK	Amex	To renew the certificates, you will need to upload the new certificates to the Open Banking Directory, and associate them to the currently used Software Statement ID. Once done, it is enough to change them in the Yapily Console UI, by editing the registration, assigning the new certificates, and saving it.	N/A	No impact to consents, unless a new application is created on the developer portal, which would be considered a new registration with new credentials, as the consents and registration is tied to the client_id.	N/A	https://developer.americanexpress.com/
UK	Think Money	To renew the certificates, you will need to upload the new certificates to the Open Banking Directory, and associate them to the currently used Software Statement ID. Once done, you’ll need to login to the developer portal and update the OBSEAL certificate there, the details will remain the same, so no need to change anything in the Yapily Console, but just as a double check, you can compare the details on the developer portal with the details in the Yapily Console to make sure that they are correct.	N/A	Consents are tied to the certificates, but are also validated separately, so there might be a slight chance of consent impact.	N/A	https://tmg.dashboard.token.io/
UK	Tide	To renew the certificates, you will need to upload the new certificates to the Open Banking Directory, and associate them to the currently used Software Statement ID. Once done, it is enough to change them in the Yapily Console UI, by editing the registration, assigning the new certificates, and saving it.	N/A	No impact to consents, unless a new Software Statement ID is used, which would be considered a new registration with new credentials, as the consents and registration is tied to the Software Statement ID.	N/A	N/A
UK	TSB Bank plc	To renew the certificates, you will need to upload the new certificates to the Open Banking Directory, and associate them to the currently used Software Statement ID. Once done, it is enough to change them in the Yapily Console UI, by editing the registration, assigning the new certificates, and saving it.	N/A	No impact to consents, unless a new Software Statement ID is used, which would be considered a new registration with new credentials, as the consents and registration is tied to the Software Statement ID.	N/A	N/A
UK	Unity Trust Bank	To renew the certificates, you will need to upload the new certificates to the Open Banking Directory, and associate them to the currently used Software Statement ID. Once done, you’ll need to login to the developer portal and update the OBSEAL certificate there, the details will remain the same, so no need to change anything in the Yapily Console, but just as a double check, you can compare the details on the developer portal with the details in the Yapily Console to make sure that they are correct.	N/A	Consents are tied to the certificates, but are also validated separately, so there might be a slight chance of consent impact.	N/A	https://unitytrust.dashboard.token.io/
UK	Vanquis Bank	To renew the certificates, you will need to upload the new certificates to the Open Banking Directory, and associate them to the currently used Software Statement ID. Once done, it is enough to change them in the Yapily Console UI, by editing the registration, assigning the new certificates, and saving it.	N/A	No impact to consents, unless a new Software Statement ID is used, which would be considered a new registration with new credentials, as the consents and registration is tied to the Software Statement ID.	N/A	N/A
UK	Wise	To renew the certificates, you will need to upload the new certificates to the Open Banking Directory, and associate them to the currently used Software Statement ID. Once done, it is enough to change them in the Yapily Console UI, by editing the registration, assigning the new certificates, and saving it.	N/A	No impact to consents, unless a new registration is created with new credentials, as the consents and registration is tied to the ClientID.	N/A	N/A
UK	cooperativebank	To renew the certificates, you will need to upload the new certificates to the Open Banking Directory, and associate them to the currently used Software Statement ID. Once done, you’ll need to login to the developer portal and update the OBSEAL certificate there, the details will remain the same, so no need to change anything in the Yapily Console, but just as a double check, you can compare the details on the developer portal with the details in the Yapily Console to make sure that they are correct.	N/A	Consents are tied to the certificates, but are also validated separately, so there might be a slight chance of consent impact.	N/A	https://coop.dashboard.token.io/signin
UK	Soldo	To renew the certificates, you will need to upload the new certificates to the Open Banking Directory, and associate them to the currently used Software Statement ID. Once done, you’ll need to login to the developer portal and update the OBSEAL certificate there, the details will remain the same, so no need to change anything in the Yapily Console, but just as a double check, you can compare the details on the developer portal with the details in the Yapily Console to make sure that they are correct.	N/A	Consents are tied to the certificates, but are also validated separately, so there might be a slight chance of consent impact.	N/A	https://soldo.dashboard.token.io/
UK	Mettle	To renew the certificates, you will need to upload the new certificates to the Open Banking Directory, and associate them to the currently used Software Statement ID. Once done, it is enough to change them in the Yapily Console UI, by editing the registration, assigning the new certificates, and saving it.	N/A	No impact to consents, unless a new Software Statement ID is used, which would be considered a new registration with new credentials, as the consents and registration is tied to the Software Statement ID.	N/A	N/A
UK	Chase UK	To renew the certificates, you will need to upload the new certificates to the Open Banking Directory, and associate them to the currently used Software Statement ID. Once done, it is enough to change them in the Yapily Console UI, by editing the registration, assigning the new certificates, and saving it.	N/A	No impact to consents, unless a new application is created on the developer portal, which would be considered a new registration with new credentials, as the consents and registration is tied to the client_id.	N/A	https://developer.openbanking-obie.chase.co.uk/

Learn

Build

Payments

Data

Hosted Pages

Resources

Registration Maintenance

Certificate Renewal and Updates

UK Certificates

EU Certificates

Getting Started

​Certificate Renewal and Updates

​UK Certificates

​EU Certificates

​Getting Started

Certificate Renewal and Updates

UK Certificates

EU Certificates

Getting Started