What records might a payment processor hold?¶

A payment processor may hold the connecting records between the payer, merchant, acquiring institution and card issuer.

Avoid this assumption: The processor merely passes the payment through and keeps nothing useful.

Processor records may include merchant ID, gateway ID, transaction ID, authorisation request, response code, amount, currency, timestamps, risk checks, settlement status, refunds and chargebacks.

For online payments, the processor may also record IP address, device or browser information, checkout-session data, token details and authentication outcomes.

The processor may hold the reference needed to match the merchant’s order with the issuer’s card record.

It may also identify whether the payment was card-present, card-not-present, recurring, tokenised or merchant-initiated.

But processor records do not necessarily identify the actual purchaser or merchant operator.

Customer-order, delivery, staff and account records may remain with the merchant.

Preserve every processor reference and ask how it links to merchant, acquiring and issuer records.

Where several processors or payment facilitators are involved, identify which one handled each stage.

Do not assume that a processor timestamp is the customer-action time. It may represent message receipt, authorisation, settlement or another system event.

Ask the processor to define unfamiliar fields and explain any status changes.

Processor records can be especially important where the merchant descriptor is unclear, the merchant account is part of a marketplace or the payment was later refunded or disputed.

When reporting, identify the processor’s role and keep system routing separate from personal attribution.

Operational takeaway¶

Use processor records to reconcile the payment chain and identify merchant, token, gateway and status information, while obtaining separate evidence about the actual user and purchase.