Other pages in this section Account selection at PISP Account Selection at PISP – Supplementary Info Account Selection at ASPSP Scheduled Payments – Future Dated Standing Orders International Payments Bulk / Batch Payments Multi-authorisation Payments Confirmation of Funds for PISP – Y/N Response Payment Refunds VRP Payments with an SCA exemption VRP Payments under Sweeping Access VRP Payments with delegated SCA VRP Consent Dashboard & Revocation VRP – Access Dashboard & Revocation
This content is best viewed on a desktop browser. 1 CX Considerations 1ASPSPs must display the TPPs’ trading name/brand name (i.e. the Client Name in the software statement) to the PSU during authentication screens and on any Access Dashboards. They do not need to display the registered company name of the TPP even if it is different. If there is an Agent acting on behalf of the TPP, ASPSPs must also, display the Agent company name (as captured in the ‘On behalf of’ field of the software statement) to the PSU. (Please note that ASPSPs can only show the Agency/On Behalf field in cases where this information has been provided by PISPs). For examples of what names should be displayed, please refer to below table Examples. You may also refer to FAQs on Which name must TPPs display to the PSU. 2 CX Considerations 2ASPSPs should offer a functionality ( e.g. search, sort, filter) to enable a PSU to search for the relevant access. This will be of particular benefit as the number of consents given by a PSU to TPPs increases. 3 CEG Checklist Requirements 3ASPSPs must present all the consent parameters and allow the PSU to expand the level of details. The Access Dashboard should also describe: The status of the variable recurring payment access e.g. Active/Inactive. The date the variable recurring payment was granted. When the PISP’s variable recurring payment access to the account(s) will expire, if available. ASPSPs must make available on all digital channels a variable recurring payment access dashboard which allows PSUs to view access which has been previously granted and it must be easy and intuitive for PSUs to find and use. 4 CX Considerations 4ASPSPs should make the status of TPP variable recurring payment access clear by the use of emboldened words. The ASPSP should also make it clear, which party provided the PISP variable recurring payment access, in the case of joint/ multiple account holders. 5 CX Considerations 6ASPSPs should present the PSU with Payment History and allow the PSU to expand the level of details. 6 CEG Checklist Requirements 7The access dashboard must allow a PSU to view or cancel the variable recurring payment access they have given consent to. These functions %22cancel access%22 and %22back%22 should be given equal prominence when offered to the PSU. ASPSPs must advise PSUs that they should contact the associated PISP to inform them of the cancellation of variable recurring payment access and/or understand the consequences of doing so. 7 CEG Checklist Requirements 5ASPSPs must present all the consent parameters and allow the PSU to expand the level of details. Payee Account Name. Payee Account Identification details (e.g. account number and sort code or additionally roll number or full IBAN). Payment Reference – This is optional but it is good practice to be populated for a payment. Maximum amount per payment and Currency (GBP for UK implementations). Maximum amount per month. 8 CEG Checklist Requirements 7ASPSPs must advise PSUs that they should contact the associated AISP to inform them of the cancellation of access and/or understand the consequences of doing so. 9 TPP Trading NameA trading name is a name (or names) used by a person, partnership or company for carrying out business, which is not the same as their own name or official registered name. The trading name is the customer-facing entity name of the company or the name of a brand or product owned by the company and should be registered with the FCA. 10 TPP Registered Company NameA company name is the registered legal entity name of the business. This is also referred to as the Organisation Name or Business Name and is usually the name that will appear on the relevant NCA register, as well as, the eIDAS certificate. 11 TPP Agent Company NameAn agent means a person or entity who acts on behalf of an authorised payment institution or a small payment institution in the provision of payment service. Agents are registered with the FCA under their principal’s entry. Select to scroll left Select to scroll right
CEG Checklist Requirements & CX Considerations 1 ASPSPs must display the TPPs’ trading name/brand name (i.e. the Client Name in the software statement) to the PSU during authentication screens and on any Access Dashboards. They do not need to display the registered company name of the TPP even if it is different. If there is an Agent acting on behalf of the TPP, ASPSPs must also, display the Agent company name (as captured in the ‘On behalf of’ field of the software statement) to the PSU. (Please note that ASPSPs can only show the Agency/On Behalf field in cases where this information has been provided by PISPs). For examples of what names should be displayed, please refer to below table Examples. You may also refer to FAQs on Which name must TPPs display to the PSU. 2 ASPSPs should offer a functionality ( e.g. search, sort, filter) to enable a PSU to search for the relevant access. This will be of particular benefit as the number of consents given by a PSU to TPPs increases. 3 ASPSPs must present all the VRP consent parameter(s) and allow the PSU to expand the level of details. The Access Dashboard should also describe: The status of the variable recurring payment access e.g. Active/Inactive. The date the variable recurring payment access was granted. When the PISP’s variable recurring payment access to the account(s) will expire, if available. ASPSPs must make available on all digital channels a variable recurring payment access dashboard which allows PSUs to view access which has been previously granted and it must be easy and intuitive for PSUs to find and use. 10a 4 ASPSPs should make the status of variable recurring payment access clear by the use of emboldened words. The ASPSP should also make it clear, which party provided the PISP variable recurring payment access, in the case of joint/ multiple account holders. 5 ASPSPs must present all the VRP consent parameter(s) and allow the PSU to expand the level of details. Payee Account Name. Payee Account Identification details (e.g. account number and sort code or additionally roll number or full IBAN). Payment Reference – This is optional but it is good practice to be populated for a payment. Maximum amount per payment and Currency (GBP for UK implementations). Maximum amount per month. 19c 6 ASPSPs should present the PSU with Payment History and allow the PSU to expand the level of details. 7 The access dashboard must allow a PSU to view or cancel the variable recurring payment access they have given consent to. These functions “cancel access” and “back” should be given equal prominence when offered to the PSU. ASPSP must update the status of Variable Recurring Payment consent setup to ‘Revoked’ immediately and make the status visible to the PSU on the access dashboard. ASPSP must also make the status available to the PISP immediately. ASPSPs must advise PSUs that they should contact the associated PISP to inform them of the cancellation of variable recurring payment access and/or understand the consequences of doing so. 10c
VRP Consent Dashboard & Revocation Previous Related articles Please select API specifications Access Revocation Card Based Payment Instrument Issuers (CBPIIs) Next