Skip to content

Payment Gateway

A payment gateway securely collects and transmits electronic payment information between a customer's checkout and the systems responsible for processing the transaction.

A payment gateway is the technology that securely collects and transmits payment information from a customer during an electronic transaction.

It acts as the communication layer between the checkout experience and the systems responsible for processing the payment.

Stripe distinguishes the gateway from the processor: the gateway securely transmits payment information, while the processor handles authorization and movement of funds. Stripe's explanation of payment gateways and processors

What It Does

During an online card payment, a gateway may:

  1. Collect payment details
  2. Encrypt or tokenize sensitive information
  3. Send the transaction into the payment-processing system
  4. Receive the authorization result
  5. Communicate the result back to Checkout

Modern payment providers often bundle gateway and processing functionality into one service.

Gateway vs. Processor

A Payment Gateway handles the secure communication of payment information.

A **Payment Processor** handles the systems required to authorize and settle the transaction between financial institutions.

In modern platforms, one provider may supply both, so merchants may never configure them as separate products.

Payment Security

Payment systems need to protect sensitive cardholder information.

The PCI Security Standards Council's PCI DSS documentation describes the industry security standard for organizations that store, process, or transmit payment-card data.

Using provider-hosted payment fields or checkout experiences can reduce how much sensitive payment information passes through the merchant's own systems.

The exact compliance responsibilities depend on the implementation.

Why It Matters

Payment collection is a high-risk system boundary.

A gateway needs to:

  • Work reliably
  • Communicate failures clearly
  • Protect payment information
  • Support required payment methods
  • Integrate correctly with the order system

A successful payment that fails to create an order can be just as problematic as a payment that fails outright.

Common Problems

Common problems include:

  • Gateway credentials expiring
  • Test credentials used in production
  • Duplicate payment requests
  • Checkout failing without useful feedback
  • Successful payments not reaching Order Management
  • Unsupported payment methods
  • Plugins becoming outdated
  • Several payment integrations conflicting

How to Improve

Prefer well-supported integrations from reputable payment providers.

Test:

  • Successful payments
  • Declines
  • Authentication flows
  • Retries
  • Refunds
  • Duplicate submission
  • Connection failures

and verify that payment state remains consistent with Order Management.