How to create OBWAC & OBSEAL certificates

Previous step of the certificates onboarding process

Please make sure you complete the first step of the process: Create an Open Banking Software Statement.

Before you start

To create the OBWAC & OBSEAL certificates you need the following prerequisites:

• Access to the "Directory" tile in Open Banking Directory (You will need permission from Open Banking to access this tile)
• Credit Kudos CLI tool cloned to your local machine
• Go 1.11 or higher installed on your local machine

Steps for you to follow

1. Information required to create certificates

Before you can create the certificates you will require information about your organisation from your Software Statement.

You will require the following information:

Field	Description
Country code	This is the code of the country you operate in
Organisation Name	This is the name of your organisation as listed on your Software Statement
Organisation ID	This is your Registration ID To find this field you will need to go to the "Organisation Details" tab in your Software Statement Under the "Component Authority Claims" section you will then see your "Registration ID" You must append this value to the following: PSDGB-FCA- The final value should look like this : PSDGB-FCA-xxxxxx
Common Name	This is the Organisation ID To find this field you will need to go to the "Organisation Details" tab in your Software Statement Under the "Business Information" section you will then see your "Organisation ID"
PSD2 Roles	PSP_PI - Payments PSP_AI - Data

2. Create the OBWAC certificate

To create your OBWAC certificate you will need to first navigate to where you have cloned the Credit Kudos CLI tool. and then run the following command:

 go run github.com/creditkudos/eidas/cmd/cli \

  -country-code Country code \

  -organization-name "Organization Name" \

  -organization-id Organization ID \

  -common-name Common Name \

  -roles PSD2 Roles \

  -type QWAC \

  -csr obwac.csr \

  -key obwac.key

In this Eidas folder this will generate 2 files an obwac.csr and obwac.key

You will then need to upload this OBWAC certificate to your Software Statement.

3. Upload the OBWAC certificate

Select the "Certificates" tab  and then click the "Add new Organisation Certificate" button:

You must then select the following values and upload the obwac.csr file:

4. Create the OBSEAL certificate

To create your OBSEAL certificate you will need to first navigate to where you have cloned the Credit Kudos CLI tool. and then run the following command:

 go run github.com/creditkudos/eidas/cmd/cli \

  -country-code Country code \

  -organization-name "Organization Name" \

  -organization-id Organization ID \

  -common-name Common Name \

  -roles PSD2 Roles \

  -type QSEAL \

  -csr obseal.csr \

  -key obseal.key

In this Eidas folder this will generate 2 files an obseal.csr and obseal.key

5. Upload the OBSEAL certificate

Select the "Certificates" tab  and then click the "Add new Organisation Certificate" button:

You must then select the following values and upload the obseal.csr file:

6. Associate certificates with their Software Statement

In the "Organisation Details" tab in your Software Statement, you must go to the "Keys/Certificates" section to see your created certificates.

You must click the "Associated" checkbox in order to associate the certificates with your Software Statement:

7. Obtain certificate PEM 

In the "Organisation Details" tab in your Software Statement, you must go to the "Organisation level certificates" section to see your created certificates.

For each certificate you must click the "Get PEM" button. This will download the PEM file for the certificate.

This file will be downloaded and named by the key ID we advise that you append obseal/obwac to the file name to make it easier to identify the PEMs.

Outcome

You should now have 6 files:

1. obwac.csr
2. obwac.key
3. obwac-KEY_ID.pem
4. obseal.csr
5. obseal.key
6. obseal-KEY_ID.pem

Next step of certificates onboarding process

The next step would be to manually register with ASPSPs.