What is a card-payment processor?¶

A card-payment processor handles transaction messages and data between merchants, acquiring institutions, card networks and issuing banks.

Avoid this assumption: The merchant and processor are the same organisation.

A merchant may use a processor to route authorisation requests, record transaction status, manage refunds, support settlement and provide fraud controls.

The processor may create its own transaction IDs, merchant references, risk scores and timestamps.

These records can be valuable where the merchant statement, issuer record and customer account show different identifiers.

A processor may also support many merchants, marketplaces or payment facilitators.

The processor’s name may appear in a descriptor, receipt, website code or provider response even where the customer has never heard of it.

Relevant records may include merchant ID, terminal or gateway ID, authorisation request, response code, IP address, device or browser data, token information, settlement status and linked refunds or chargebacks.

The processor may not hold all customer-order or delivery records. Those may remain with the merchant.

Likewise, it may not identify the person who used the card or operated the merchant account.

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

Where several providers are involved, use the processor’s identifiers to reconcile the payment chain.

Do not assume that a processor’s timestamp is the customer-action time without confirmation.

When reporting, identify the processor’s role and avoid describing it as the merchant unless the evidence supports that.

Operational takeaway¶

Use processor records and identifiers to connect the card-payment stages, while obtaining separate merchant and user evidence for attribution and purpose.