What is a payment gateway?¶

A payment gateway is the service that receives payment information from a merchant checkout and passes it into the payment-processing chain.

Avoid this assumption: The gateway is the merchant, bank or final recipient of the money.

The gateway may collect or transmit card details, tokens, transaction amounts, merchant identifiers and authentication information.

It may also apply security checks, encryption, fraud screening or routing rules.

Relevant records can include gateway transaction IDs, checkout-session IDs, timestamps, merchant account details, IP addresses, device or browser data, token information and response codes.

The gateway may sit between the website or application and the payment processor.

A merchant can use one gateway and a separate processor or acquiring institution. The gateway may also serve many merchants under different commercial arrangements.

The gateway’s records can help show what information was submitted, when and from which session.

But they may not show final settlement or receipt of goods.

They also do not automatically identify the person using the device.

Preserve the gateway reference, merchant ID, session ID, amount, date, time and any linked processor reference.

Ask the merchant or gateway provider how the records connect to the order and final payment status.

Do not assume that a successful gateway response means the payment completed. It may only mean the request was accepted for processing.

When reporting, distinguish the checkout event, gateway transmission, authorisation and settlement.

Operational takeaway¶

Use gateway records to reconstruct the checkout and payment-submission stage, then link them to processor, merchant and bank records for final status and attribution.