Customer Experience Guidelines

Change Log v4.0.1

This version is:

This is the latest version Published 2 weeks ago 18 Mar 2026

A summary of changes from V4.0 to V4.0.1

Other pages in this section

Customer Experience Guidelines Changes: V4.0 to V4.0.1

LinkSub section/LocationChangeReason for Change
TRI definitions and guidancePayment Purpose Codes (PPC)Added paragraph under PPC about new code CRYP for crypto

Deleted reference to crypto wallets in definition of EPAY

Added definition of CRYP

Added optional guidance relating to guidance under heading “Optional Use of PPC to Support Gambling Blocks”		Change Request
AIS Consent DashboardTable under Revocation Journey / Figure 8: Fourth requirement in tableDeleted redundant text about Version 4 and fixed link to API specificationsMinor correction during v4.0.1 discussions
Common Error ScenariosAwaiting Further Authorisation


Rejected – Consent / Payment
Updated description of U037 under Awaiting Further Authorisation. Previously it just said “Authorisation failed” but corrected to what it should be, namely “Authorisation failed by one (or more) of the authenticators”

Replaced U037 with U033 and removed a redundant scenario (formerly #13) under Rejected heading
Known Issue
AIS Access DashboardRevocation JourneyIn CEG Checklist Requirements & CX Considerations table under #5, aligned CEG text to the API Specification to make clear that ASPSP must update the status of the consent. Previously it said "should" update.

ASPSP should must update the status of the consent.		Minor correction during v4.0.1 discussions
Standing OrdersWireframesReplaced old wireframe which was for future dated payments with correct one for Standing OrdersKnown Issue
Information flow – Payment Status – Standing OrdersWireframesReplaced old wireframe which was for future dated payments with correct one for Standing Orders, moved the status reason code U0xx under example 8 to sit next to INFA rather than INCO, and made other minor typographical changesKnown Issue