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.

Using permission types

See the example of permission usage in the step 5 of OpenID Connect Authorization Code flow for upfront permissions using permission type payment.

Info

Using a permission type other than authentication.v1 requires registering permissions upfront. See the Authorization Code with upfront permissions or Client Initiated Backchannel Authentication flows for more details.

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

Text

A permission representing the approval of a text string, for example a terms and conditions text.

Warning

This permission type must not be used for payment confirmations. Instead, use payment.

Note

This permission type requires the permissions/text 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 text.v1

Payment

A permission representing the approval of a payment 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, consider using approveCard for a smoother card approval flow.

See the schema specification for payment.v1

ApproveCard

A permission representing the approval of adding a payment card.

Note

This permission type 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

ApproveAccount

A permission representing the approval of adding a bank account.

Note

This permission type 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