Revoking the Consents

After a certain period, some bank customers (also known as Payment Service Users (PSUs)), may prefer to revoke the consents they gave Third-Party Providers (TPPs) to access account data. In WSO2 Open Banking, you can revoke these consents as follows:

Let's learn more about these two methods! 

Revoking the consents by Payment Service Users

The WSO2 Open Banking Consent Manager portal, also known as the Self-care portal, enables Payment Service Users (PSUs) to review and revoke the consents they provided to access account details. 

Let's take a look at how a PSU can revoke consent.

1. Go to the Consent Manager portal at https://<WSO2_OB_KM_HOST>:9446/consentmgt.

   

2. Enter the username and password provided by the bank. Click SIGN IN.

3. In the Consent Manager portal's home page, you can view a list of the consents you granted to Accounts and Payments. Click on an account consent to see its details, as shown below:
   

   Consent status is displayed to the right of the selected consent. Available consent statuses are rejected, awaiting authorisation, authorised, and revoked. You can find more information in Account access consent status.

   Below is the list of permissions that a PSU can grant to Account consents:

   Permission type	Description	Permission variation
   ReadAccountsDetail	Reads account information	Basic Detail - ability to identify account using information in the payload
   ReadBalances	Reads all balance information	-
   ReadBeneficiariesDetail	Reads beneficiary information	Basic Detail - ability to identify an account for the beneficiary using information in the payload
   ReadDirectDebits	Reads all beneficiary information	-
   ReadProducts	Reads all product information related to an account	-
   ReadStandingOrderDetail	Reads standing order information	Basic Detail - ability to identify an account for the beneficiary of  the standing order using information in the payload
   ReadTransactionsCredits	Reads credit transaction information	Basic Detail - Reads transaction data elements which may hold silent party details
   ReadTransactionsDebits	Reads debit transaction information	Basic Detail - Reads transaction data elements which may hold silent party details
   ReadOffers	Reads offer information	-
   ReadPAN	Reads Permanent Access Number (PAN) in the clear	-
   ReadParty	Reads party information of the account owner	-
   ReadPartyPSU	Reads party information of the PSU logged in	-
   ReadStatementDetail	Reads statement details	Basic Detail - Reads identification details accessing certain elements in the payload
   ReadScheduledPaymentDetail

4. After reviewing the consent, click revoke. 

   Optionally, you can enter a reason for the revocation.

   Revocation reasons help you to find more information later. It is not mandatory to provide a reason for revocation.

   

5. Click Revoke to confirm the revocation. 

6. The status of the consent is now changed to Revoked. You can still find the history of consents remaining in the list.
   

Revoking the consents by customer care representatives

The WSO2 Open Banking Customer Care portal enables the Customer Care Representatives to revoke the consents on behalf of the PSUs. You need a user whose role is defined as a customer care officer. To create and user and role, refer Configuring users and roles.

Now, let's take a look at how a customer care representative can revoke consent.

1. Sign in to the Customer Care Portal (https://<WSO2_OB_KM_HOST>:9446/ccportal) using the username and password of the Customer Care user.

   

2.  You can filter the search results using the following parameters:

   • User ID: The user ID created for the PSU in the online banking application. This is the same user that is used for generating the consent IDs.

   • The consent type is selected as Accounts by default. You can select between Accounts or Payments.

   • TPP Application: The TPP applications authorised for the ASPSP are listed here. You can select the TPP application the PSU has given consent to.

   • Status: Select the consent status. Possible values are: Rejected, Awaiting Authorisation, Authorised, and Revoked. 

   • Set Date Range: The date range in which the PSU’s consent is valid.

     You can use one or more filter options and proceed searching.

   

   WSO2 Open Baking is a solution developed with compliance to the PSD2. It is stated in the PSD2 as "A PSU cannot revoke a payment-order consent once it has been authorized".

3. Click Search.

4. A list of search results is displayed, as shown below. You can view the Account and Payment consent information by clicking the consent.

   

5. Click the consent you want to revoke and view the consent details. 
   
   One consent ID can be granted to many accounts that belong to the same PSU. Therefore, there are two methods to revoke account consent.
   1. 1. 1. Revoke consent ID -
            When a PSU has asked a customer care representative to revoke consent, customer care representative revokes all account consents with that consent ID.
         2. Revoke an account consent -
            An individual account consent can be revoked. It revokes only that account consent. 
            
            The above mentioned two options are as follows:
            
            

6. Click Revoke. Optionally, you are asked to enter a reason for the revocation.

   Revocation reasons will help you to find more information later. It is not mandatory to provide a reason for revocation.

   
   Confirmation windows appear for the two methods separately:

   1. 1. Confirmation to revoke an account
         

      2. Confirmation to revoke consent ID.
         
7. Click Revoke to confirm the revocation.