Permission types#
On this page
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.
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
Payment#
A permission representing the approval of one or multiple payments satisfying PSD2 RTS Article 4 Authentication code and Article 5 Dynamic Linking.
See the schema specification for payment.v1
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
ApproveCard#
A permission representing the approval of adding a payment card.
See the schema specification for approveCard.v1
ApproveAccount#
A permission representing the approval of adding a bank account.
See the schema specification for approveAccount.v1
VerifiedConfirmation#
A permission representing the confirmation of a text message displayed to the user.
See the schema specification for verifiedConfirmation.v1
CustomerServiceCall#
A permission representing a Safe Conversation authentication scenario.
See the schema specification for customerServiceCall.v1
CustomerServiceChat#
A permission representing a customer service chat authentication scenario.
See the schema specification for customerServiceChat.v1
