GoPay

What a gateway handles

Without a payment gateway a shop would need its own contracts with the card schemes, would have to meet the security requirements for handling card data, and would connect to each bank separately. The gateway wraps all of that into one interface: the shop passes an amount and an order identifier and receives a payment result.

The second layer is the payment page. At the moment of payment the customer is redirected into the gateway's environment or it is embedded into the page, so sensitive card data never touches the shop's own server. That materially reduces the security obligations the merchant would otherwise carry alone.

What to expect in this region

On the Czech and Slovak markets cards alone are not enough. Customers expect bank buttons — an immediate redirect into their own bank's online banking — and mobile wallets. A gateway is worth what its coverage of the specific banks your customers actually use is worth.

• Cards, including cardholder verification and saving a card for next time.
• Bank buttons for Czech and Slovak banks, depending on the target market.
• Mobile wallets, now a substantial share of payments made on a phone.
• Recurring payments if you sell subscriptions.
• Refunds issued from the shop's own admin, not by emailing support.

How to compare gateways

Price is one variable and not always the decisive one. Just as important: how fast money reaches the account, whether refunds can be issued from the shop's admin, how the customer-facing page behaves on a phone, and whether payment data flows back onto the order.

In practice it pays to design the integration so the gateway can be swapped. If payment logic sits in one layer rather than scattered through the codebase, changing provider becomes configuration. That is how a custom e-shop is built — ComGate or GoPay then becomes a commercial decision rather than a rebuild.