Exact identity before market claims

A familiar brand can make a service appear singular when its legal and operational structure is not. The website may be operated by one group company, the contract issued by another, payments received by a specialist provider and a regulatory permission held by a fourth entity. None of those facts is inherently unusual. The evidence problem begins when they are compressed into one unqualified claim about ‘the firm’. A responsible record starts by identifying which legal person performs which function.

Exact identity is more than copying a company name from a footer. A useful record connects the legal name to an official identifier, place of incorporation, trading names and the source from which each fact was taken. It then tests whether the customer-facing journey points to that same entity: the terms presented at onboarding, the account agreement, transaction information, complaint notice and payment instructions. Differences require explanation, not assumption.

Jurisdiction changes the analysis. A group may direct customers in different countries to different contracting entities, and the same web address may present different terms by location. A permission held in one jurisdiction does not automatically describe services provided elsewhere. The evidence record therefore needs a territorial statement and a date, because routing, permissions and customer terms can change.

Brand, website and domain evidence remain useful, but only for what they prove. They can show how a service is represented publicly, which names are used and where customers are directed. They do not, without supporting records, establish the contracting party, licence holder or entity responsible for a complaint. RMCA’s developing methodology keeps representational evidence separate from official and contractual evidence.

The same discipline applies to payment flows. The name on a bank transfer, card descriptor or payment page may identify a payment provider, collection agent or affiliate rather than the entity responsible for the underlying financial service. Recording that difference is not an allegation. It is a way to prevent a payment function from being mistaken for a wider regulatory or conduct conclusion.

An identity record should also preserve uncertainty. If public sources conflict, a record can state the conflict, show the sources and define what could not be resolved. Silence is preferable to filling a gap with group-level inference. Where appropriate, a right-of-reply process may help clarify the record, but any response should remain attributed and should not erase the underlying public-source history.

For FDRC, exact identity supports questions about the trading service, complaint owner and potential redress route. For PSCR, it supports questions about the payment institution, service perimeter and safeguarding responsibility. The common RCEF identity layer connects those records without merging their conclusions. One entity may have records in both contexts; each remains bounded by its programme scope.

This is why identity comes before status. Until the responsible entity and service perimeter are established, a positive or adverse label risks being attached to the wrong person or activity. The Observatory uses public-source examples and methodology notes to show the anatomy of that problem. It does not convert research visibility into programme participation or endorsement.