When a permission is read beyond the service actually provided

A customer-facing service refers to the permission of a principal institution. The same brand also offers adjacent technology and commercial services through other entities. Public wording compresses these relationships into a general statement that the brand is regulated.

The issue is not necessarily that the permission is false. The issue is that readers cannot tell which legal entity provides the payment service, which activity the permission covers, whether an agent is involved or whether the same wording applies across territories and customer categories.

Start with the exact contracting and service-providing entities. Resolve official identifiers and source dates. Map the customer journey from brand or app to contract, legal entity, permission, agent or distributor and customer scope. Record restrictions and uncertainties without converting them into conclusions.

• —Exact legal name and identifier
• —Service-specific permission
• —Agent or distributor principal
• —Territorial and customer scope
• —Contract and funds flow
• —Source date and material changes

Permissions, group structures, agents and product terms can change. A screenshot or terms document may describe an earlier arrangement. The record should show what was known at each date and whether later evidence corrects or supersedes it.

A future PSCR record would preserve this history rather than overwrite it with one current label. Programme status would remain attached to the exact institution and scope.

The correct response is to narrow the statement until entity, permission and service perimeter align. If evidence does not resolve the relationship, the limitation remains visible. A group relationship or similar name does not create group-wide permission or status.

This note is not a conclusion about a real institution and does not determine regulatory or contractual rights.