> For the complete documentation index, see [llms.txt](https://apidocs.arionbanki.is/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://apidocs.arionbanki.is/psd2/more-information/working-with-corporate-accounts.md).

# Working With Corporate Accounts

## Overview

Arion Bank supports both personal accounts and corporate accounts in the PSD2 webservice. 

This applies for both account information service (AIS) consents and payment initiation service (PIS) consents. 

There are two header parameters used to identify the payment service user and the corporate entity that the user is acting for:

* `PSU-ID` - Kennitala of the payment user
* `PSU-Corporate-ID` - Kennitala of the corporate entity

When creating an account information service consent for personal accounts, the third party provider (TPP) should send in the `PSU-ID` of the payment user and omit the `PSU-Corporate-ID`. This will only return the payment accounts for the payment user and not corporate accounts it has access to. When creating an account information service consent for corporate accounts, the third party provider (TPP) should send in both the `PSU-ID` of the payment user and the `PSU-Corporate-ID` of the corporate entity the user is creating a consent for. This will only return the payment accounts that this user has access to for this specific corporate identity and will not return any personal accounts. Similarly, when initiating payments from a corporate account, the `PSU-Corporate-ID`for the owner of the account must be submitted in the payment initiation request.

### Sandbox

To assist in your integration of the corporate account flow, we have created static data for you to use. We have established a fake company with an associated fake kennitala in the sandbox which has two corporate accounts. Gervifyrirtæki ehf. has the kennitala 555555-5550. The two accounts it possesses have different capabilities. Both accounts are accessible via AIS consents, but only one of them is accessible for PIS consents. Below is a table detailing this:

| Account number | IBAN                       | Kennitala   | Available via AIS | Available via PIS | Accessible to |
| -------------- | -------------------------- | ----------- | ----------------- | ----------------- | ------------- |
| 030126007654   | IS740301260076545555555550 | 555555-5550 | Yes               | Yes               | Any PSU       |
| 030126007655   | IS120301260076555555555550 | 555555-5550 | Yes               | No                | Any PSU       |

### Examples

* An account information request (`GET /v1/accounts`), under a consent created with the corporate `PSU-Corporate-ID`, returns `200 OK` with both accounts.
* A payment from the entitled account (`030126007654`) returns `201 Created` and triggers the normal SCA flow.
* A payment from the blocked account (`030126007655`) returns `403 Forbidden` (`User is not entitled to this account`).
* An unknown corporate kennitala (for example `9999999999`) returns `403 Forbidden` (`Corporate ID not recognized`).