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

What evidence may corroborate payment authorisation?

Corroboration should reconstruct how an instruction was created, authenticated and approved and connect those stages to an account, endpoint and user. Completion alone does not prove informed consent.

Authorisation is a sequence

Relevant provider fields include instruction time, beneficiary creation, limit or whitelist changes, one-time-code delivery, biometric or PIN result, endpoint, session, IP-related data and confirmation. Initiation and approval may occur on different devices; codes can be intercepted and remote access can influence the user.

Add endpoint and communication context

Device artefacts, notifications, copied details, messages, CCTV and location can explain who acted and what they believed. Preserve every timestamp and establish its system meaning.

Report completion, technical authentication, personal action and informed consent separately, especially where deception or direction is alleged.

The point to remember

Corroborate authorisation through the complete instruction, authentication, endpoint and communication sequence - not one success event.

Reference: PAY-213Payments & Banking