# Permission types

Here you'll find a list of some supported permission types along with images showcasing the user experience when authenticating with the respective permission type.

> **Terms and conditions**
>
> The integration options available to you depend on the terms of your agreement. If you are unsure about your rights or permissions, please review the details in your agreement or contact us or your vendor for further guidance.

## Using permission types

See the example of permission usage in the [step 5 of OpenID Connect Authorization Code flow for upfront permissions](https://docs.stoe.no/bankid-with-biometrics/flows/code-flow-for-payments.md#5-register-the-permission) using permission type [payment](https://docs.stoe.no/bankid-with-biometrics/permission-types.md#payment).

> **Info**
>
> Using a permission type other than `authentication.v1` requires registering permissions upfront, unless you use [Rich Authorization Requests (RAR)](https://docs.stoe.no/bankid-oidc-provider/advanced-topics/authorization-details.md#authorization-details) to include them directly in a Pushed Authorization Request (PAR).
> See the [Authorization Code with upfront permissions](https://docs.stoe.no/bankid-with-biometrics/getting-started.md#authorization-code-flow-with-upfront-permissions) or [Client Initiated Backchannel Authentication](https://docs.stoe.no/bankid-with-biometrics/getting-started.md#client-initiated-backchannel-authentication) flows for more details, or the [RAR section](https://docs.stoe.no/bankid-with-biometrics/flows/code-flow-for-payments.md#alternative-rich-authorization-requests) for the alternative approach.
>
> All permission types require the `permissions/client` scope. Some permission types require additional scopes as noted in their descriptions below.

## Available permission types

There are various permission types, each with specific context data available. These permission types range from standard logins where the name of the merchant is presented, to fully-fledged PSD2 SCA compliant payment approvals.
Note that not every permission type will be listed here. If you have use cases not covered by the permission types below, please get in touch.

### Authentication

A permission representing a standard login.

[See the schema specification for authentication.v1](https://docs.stoe.no/bankid-with-biometrics/apis/permissions-api.md#model-PermissionType-authentication.v1)

![Authentication](https://docs.stoe.no/bankid-with-biometrics/img/permission-authentication.png)

### Payment

A permission representing the approval of one or multiple payments satisfying PSD2 RTS Article 4 Authentication code and Article 5 Dynamic Linking.

> **Tip**
>
> Instead of charging a nominal amount (e.g., 0 or 1 kr) to confirm cards and then refunding it, use [approveCard](https://docs.stoe.no/bankid-with-biometrics/permission-types.md#approvecard) for a smoother card approval flow.

[See the schema specification for payment.v1](https://docs.stoe.no/bankid-with-biometrics/apis/permissions-api.md#model-PermissionType-payment.v1)

![Payment](https://docs.stoe.no/bankid-with-biometrics/img/permission-payment.png)

### CardPayment

A permission representing the approval of a card payment satisfying PSD2 RTS Article 4 Authentication code and Article 5 Dynamic Linking. This is identical to the payment permission type, but we use this permission type for 3-D Secure payments.

[See the schema specification for cardPayment.v1](https://docs.stoe.no/bankid-with-biometrics/apis/permissions-api.md#model-PermissionType-cardPayment.v1)

![Payment](https://docs.stoe.no/bankid-with-biometrics/img/permission-payment.png)

![Basket payment](https://docs.stoe.no/bankid-with-biometrics/img/permission-basket-payment.png)

### ApproveCard

A permission representing the approval of adding a payment card.

> **Note**
>
> This permission type additionally requires the `permissions/approve_card` scope to be enabled for your client, and included as a `scope` when retrieving your access token. Get in touch to enable the scope for your client.

[See the schema specification for approveCard.v1](https://docs.stoe.no/bankid-with-biometrics/apis/permissions-api.md#model-PermissionType-approveCard.v1)

![ApproveCard](https://docs.stoe.no/bankid-with-biometrics/img/permission-approve-card.png)

### ApproveAccount

A permission representing the approval of adding a bank account.

> **Note**
>
> This permission type additionally requires the `permissions/approve_account` scope to be enabled for your client, and included as a `scope` when retrieving your access token. Get in touch to enable the scope for your client.

[See the schema specification for approveAccount.v1](https://docs.stoe.no/bankid-with-biometrics/apis/permissions-api.md#model-PermissionType-approveAccount.v1)

![ApproveAccount](https://docs.stoe.no/bankid-with-biometrics/img/permission-approve-account.png)

### VerifiedConfirmation

A permission representing the confirmation of a text message displayed to the user.

> **Warning**
>
> This permission type must not be used for payment confirmations. Instead, use [payment](https://docs.stoe.no/bankid-with-biometrics/permission-types.md#payment).

> **This product has specific pricing rules**
>
> Please go to our webpage for details.

[See the schema specification for verifiedConfirmation.v1](https://docs.stoe.no/bankid-with-biometrics/apis/permissions-api.md#model-PermissionType-verifiedConfirmation.v1)

![VerifiedConfirmation](https://docs.stoe.no/bankid-with-biometrics/img/permission-verified-confirmation.png)

### CustomerServiceCall

A permission representing a Safe Conversation authentication scenario.

> **Note**
>
> This permission type additionally requires the `permissions/ciba` scope to be enabled for your client, and included as a `scope` when retrieving your access token. Get in touch to enable the scope for your client.

[See the schema specification for customerServiceCall.v1](https://docs.stoe.no/bankid-with-biometrics/apis/permissions-api.md#model-PermissionType-customerServiceCall.v1)

![CustomerServiceCall](https://docs.stoe.no/bankid-with-biometrics/img/permission-customer-service-call.png)

### CustomerServiceChat

A permission representing a customer service chat authentication scenario.

> **Note**
>
> This permission type additionally requires the `permissions/ciba` scope to be enabled for your client, and included as a `scope` when retrieving your access token. Get in touch to enable the scope for your client.

[See the schema specification for customerServiceChat.v1](https://docs.stoe.no/bankid-with-biometrics/apis/permissions-api.md#model-PermissionType-customerServiceChat.v1)

![CustomerServiceChat](https://docs.stoe.no/bankid-with-biometrics/img/permission-customer-service-chat.png)