> ## Documentation Index
> Fetch the complete documentation index at: https://docs.yapily.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Handelsbanken UK

## Links

* [Developer Portal](https://developer.handelsbanken.com)

## Platform V1

### Scopes

* Account Information 🔒

### Live Environment

**Precondition**: To connect to live Open Banking entities, whether you are accessing account information or initiating payments, your business must have the right regulatory permissions as per the [Open Banking Guide](/tools-and-services/open-banking/enrolment-guide).

1. Upload your QWAC/OBWAC and QSEAL/OBSEAL certificates (PEMs), along with the keys into Yapily's [certificate vault](https://console.yapily.com/certificates).

2. Add **Handelsbank UK** from the **Live** tab to your Dashboard application and add your `Client Uri` and `Terms of Service Uri`.

3. Select your QWAC/OBWAC and QSEAL/OBSEAL certificates from the relevant drop-downs lists then click *Next*.

4. On the next Page, Click the 'Register' button to Register your certificates to Handlesbank UK. If successful it will generate *`Client ID`* along with whole registration response. Click 'Save' to save the response.

## Platform V2

#### For our platform V2 offering there are a few differences:

* The institutions now include PIS.
* There is a new sandbox that can be integrated with.
* The AIS includes credit card accounts.

### Scopes

* Account Information 🔒

### Supported ASPSPs

| ASPSP                     | Link                                                                       | Supported | Institution ID             |
| ------------------------- | -------------------------------------------------------------------------- | --------- | -------------------------- |
| Handelsbanken UK          | [https://developer.handelsbanken.com](https://developer.handelsbanken.com) | Yes       | `handelsbanken_uk`         |
| Handelsbanken Business UK | [https://developer.handelsbanken.com](https://developer.handelsbanken.com) | Yes       | `handelsbankenbusiness_uk` |
| Handelsbanken UK Sandbox  | [https://developer.handelsbanken.com](https://developer.handelsbanken.com) | Yes       | `handelsbanken-sandbox_uk` |

### Accounts Currently Supported - Payments Soon to Come

#### Accounts

* Accounts
* Transactions

### Onboarding ASPSP's to Yapily Application

**Precondition**: To connect to Handelsbanken institutions with eIDAS/OB certs a dynamic registration is needed.

Even if you have pre-existing credentials that are being used for V1, please re-register as the V2 integration requires additional subscriptions (e.g. for payments and card-acounts).

**Pre-requisites for DCR:**

* Valid QWAC / QSEAL certificates.

1. Upload the signing (OBSEAL/QSEAL) and transport (OBWAC/QWAC) certificates into V2 services
   1. For the transport certificate upload with the following request. If it already uploaded, then note down its UUID which can be retrieved from the [`GET 'https://api.yapily.com/certificates/keys/'`](https://api.yapily.com/certificates/keys/) endpoint.

      **Request**

      ```shell theme={null}
      curl --location --request POST 'https://api.yapily.com/certificates/keys/' \
      --header 'Authorization: Basic YOUR_APPLICATION_CREDENTIALS_AS_BASIC_AUTH' \
      --header 'Content-Type: application/json' \
      --data-raw '[{
         "pem": "$YOUR_PUBLIC_KEY_AS_PEM",
         "key": "$YOUR_PRIVATE_KEY",
         "kid" : "$CERT_KID",
         "name" : "$CERTIFICATE_NAME"
      }]'
      ```

      **Response**

      ```json theme={null}
      {
      "id": "d16f87d3-4222-4173-b8b9-44aeccacae7d",
      ....
      }
      ```

      Save the id and remember for which kind of key it corresponds:
      e.g. `TRANSPORT_KEY_UUID = d16f87d3-4222-4173-b8b9-44aeccacae7d`

2. Call the registration endpoint with the certificate UUIDs:

   **Request**

   ```shell theme={null}
   curl --location --request POST 'https://api.yapily.com/institutions/handelsbanken_uk/register' \
        --header 'Content-Type: application/json' \
        --header 'Authorization: Bearer YOUR_APPLICATION_CREDENTIALS_AS_BASIC_AUTH' \
        --data-raw '{
              "signingKeyID": "$SIGNING_KEY_UUID",
              "transportKeyID": "$TRANSPORT_KEY_UUID"
         }'
   ```

   **Response**

   ```json theme={null}
   {
      "id": "a0460a91-4b4c-422a-bbe6-bebe0b92e308"
   }
   ```

   Note above ID, this will be the clientId which can be further used to Get, Modify, Delete registrations with Yapily.

## Sandbox institution

**Precondition**: To connect to Handelsbanken sandbox institution with eIDAS certs a manual registration is needed.

**Pre-requisites for Manual Reg:**

* We must create an app with on the developer portal to obtain the client ID. Make sure we have added the following subscriptions for the app:

<img src="https://mintcdn.com/yapily/DOGnmkCLngHjnTOu/images/knowledge/handelsbanken/handelsbanken-subs.png?fit=max&auto=format&n=DOGnmkCLngHjnTOu&q=85&s=31245d9eb04bb18b862acdf05d7021e7" alt="handelsbanken_subscriptions" width="910" height="314" data-path="images/knowledge/handelsbanken/handelsbanken-subs.png" />

1. Call the manual registration endpoint with the certificate UUIDs and the client ID:

   **Request**

   ```shell theme={null}
   curl --location --request POST 'https://api.yapily.com/institutions/handelsbanken-sandbox_uk/manual/register' \
        --header 'Content-Type: application/json' \
        --header 'Authorization: Bearer YOUR_APPLICATION_CREDENTIALS_AS_BASIC_AUTH' \
        --data-raw '{
              "signingKeyID": "$SIGNING_KEY_UUID",
              "transportKeyID": "$TRANSPORT_KEY_UUID",
              "clientId" : "$CLIENT_ID"
         }'
   ```

   **Response**

   ```json theme={null}
   {
      "id": "a0460a91-4b4c-422a-bbe6-bebe0b92e308"
   }
   ```

## Support

If you require technical support with certificate management, please contact [Support](/resources/support).