What is a payment gateway?¶
A payment gateway receives checkout payment information and passes it into processing. It is neither necessarily the merchant nor the bank or final recipient.
Gateway data describes submission¶
It may transmit card or token, amount, merchant and authentication information and apply encryption, fraud checks or routing. Records can include gateway transaction and session IDs, times, merchant, endpoint, browser, IP-related, token and response fields.
A successful gateway response may mean accepted for processing, not authorised or settled.
Link checkout to final status¶
Preserve gateway, merchant and session IDs and mapped processor references. Ask how the event connects to order and later payment state.
Distinguish checkout, gateway transmission, authorisation and settlement, and identify the person behind the session from account and endpoint evidence.
The point to remember
Use gateway records for checkout submission and routing, then link them to processor, bank and merchant data for outcome and attribution.