Online payments for
every market you serve.

Embedded Fields, powered by Global Payments PayFields, renders the payment fields directly in your own UI: the guest never leaves your domain, the session runs through payment with no redirect, you keep full control over CSS and layout, and card data is sent straight to the gateway vault. Hosted Checkout, powered by Stripe Checkout, redirects the guest to a mobile-optimized payment page managed by the provider — the lowest technical effort to deploy, pre-optimized for card autofill, no local validation logic to write, and new payment methods appear automatically as the provider adds them. Embedded Fields is the option recommended for enterprise, but both integration styles are supported and you choose per storefront.

Conditional routing based on transaction metadata. You can route by storefront so a given venue is pinned to a given gateway, including in test mode, and configure an automatic fallback so a secondary gateway takes over when the primary one fails. The Routing Configuration screen lists each market against its gateway with a live state — Active, Fallback Active, or Currency Unsupported — so a mismatched currency surfaces as a flagged configuration rather than a silent decline. Routing is designed to help reduce processing fees and improve authorization rates; the fees and rates you actually see remain a matter of your agreements with each gateway.

Not into your own systems, in either supported flow. With Embedded Fields the card details are tokenized and sent directly to the gateway vault, and with Hosted Checkout the payment page and everything captured on it are managed by the provider. The gateway supplies those as PCI-DSS compliant fields, which is designed to support your own PCI-DSS obligations and limit the card data your systems ever touch — it is not a certification of your business, and it is not a guarantee. Your compliance status remains a matter for you, your payment provider and your acquirer.

Gateway API keys and secrets are stored in hardware-level encrypted vaults with zero plaintext visibility, and sensitive callback secrets and merchant IDs are masked in both the UI and the logs, revealed only through a timed admin challenge. Every configuration change is written to an immutable log, giving payment operations a full forensic audit trail of who changed what and when. These controls are designed to limit exposure of gateway credentials and support your own security and audit requirements — they are safeguards rather than a guarantee, and they do not replace your internal access-control and key-rotation policies.

The Live Activity Monitor reports the real-time status of online payment callbacks and gateway responses, listing each job against its order number, provider, amount and status — Paid, Pending, or Callback Delayed — with logs you can refresh on demand. A gateway that is slow to call back shows up as its own state instead of an order that silently looks unpaid, so the team can chase the right transaction. What the monitor shows is the gateway's response to a transaction; funding, settlement and any dispute handling continue to run under the terms you hold with that provider and your acquirer.