Skip to content
Skip to main content
Payments & Banking Technical Explainer

What do bank login and device records contribute?

They connect account events to recorded sessions, endpoints and networks, helping distinguish customer ownership from use. They still do not identify a person without corroboration.

Access records narrow the route

Data may include login times, IP-related fields, device or application IDs, browser details, sessions, authentication and security changes. Aligned with beneficiary creation and payment instructions, it can reveal new endpoints, failures or unusual access.

A familiar endpoint can be remotely controlled or used through an existing session; a new one can reflect legitimate travel or replacement. IP data identifies connectivity, not automatically a person or precise place.

Correlate provider and endpoint evidence

Preserve exact times and session IDs and ask whether device identifiers persist, reset or apply only within an application. Compare the bank return with device examination, communications, location and normal account behaviour.

Report access from the recorded session or network unless the wider evidence supports human attribution.

The point to remember

Use login and device records to reconstruct account access and payment timing, then identify the person behind that route separately.

Reference: PAY-046Payments & Banking