Customize Checkout

The EGW Hosted Checkout Page offers a secure, responsive, and brand-customizable payment interface hosted by the Gateway, simplifying the merchant’s integration while maintaining full governance and compliance under the Bank’s control.

It enables a seamless user experience across devices, reduces PCI DSS scope for merchants, and allows for flexible branding — all within the parameters defined by the Gateway owner.

Merchant-Level Customization

Managed via the Merchant Portal

Merchants can tailor the Hosted Checkout Page to reflect their brand identity while maintaining the security and compliance benefits of a centrally hosted solution.

Available Customization Options:

• Logo Integration – Display the merchant’s logo prominently on the payment page.

• Color Scheme Configuration – Customize primary and secondary colors (e.g., buttons, headers, links) to match brand aesthetics.

• Font Selection – Select from supported fonts to ensure visual consistency with merchant design guidelines.

• Language Preference – Set a default language or enable auto-detection based on customer locale.

• Payment Method Visibility – Show or hide specific payment options (e.g., Card, A2A, Wallet) to match merchant business needs.

• Optional Field Display – Enable or disable input fields such as billing/shipping address or phone number.

• Legal and Terms Links – Add links to merchant-specific privacy policies, terms of service, or refund policy.

• Mobile-Optimized Layout – Fully responsive checkout experience designed for smooth usability across smartphones, tablets, and desktops.

• Accessibility Compliance – Designed in alignment with WCAG 2.1 accessibility guidelines to support inclusive user experiences.

• Custom Domain Support (Optional) – Merchants may configure a custom DNS (e.g., pay.merchant.com) to white-label the checkout URL, enhancing brand trust and continuity.

Payment Method Selection Logic

The EGW Hosted Checkout Page offers dynamic and flexible control over which payment methods are displayed to the end-user and how they are ordered. The selection logic can be influenced by merchant configurations, end-user preferences, and bank-level definitions.

Supported Configuration Models

1. Merchant-Defined Defaults - Merchants can explicitly select which payment methods are available and define the default or preferred method shown first (e.g., always show Card before A2A).

2. Bank-Level Configuration - The Gateway owner (Bank or PSP) can override or predefine method availability per merchant segment or geography — ensuring regulatory compliance or strategic promotion of specific payment methods (e.g., promoting A2A in specific countries).

3. Cookie-Based / User Preference - EGW supports storing user-selected payment methods using browser cookies or session data, allowing the checkout to pre-select the previously used method for a faster experience on return visits.

4. Context-Aware Display (Optional Enhancements) - Payment methods can be dynamically prioritized based on:

   • Device type (e.g., display wallet methods first on mobile)

   • Transaction amount (e.g., A2A for higher-value payments)

   • User geolocation (e.g., show regional methods first)

   • Time of day / transaction load balancing

Additional Controls

• Method Sorting – Merchants and bank admins can define the default sort order of available methods.

• Method Grouping – Optionally display methods grouped (e.g., “Bank Payments”, “Cards”, “Wallets”).

• Fallback Scenarios – If the preferred method is unavailable (e.g., A2A bank offline), EGW can automatically fallback to other enabled methods.

End-User Experience

• The checkout UI clearly displays all enabled payment options, with visual icons and labels for better UX.

• First-time users are shown the default method (merchant or bank-defined).

• Returning users are offered a familiar and fast flow via cookie-based method recall.

• Hidden methods (e.g., temporarily disabled by bank) are excluded dynamically.

Bank-Level Control

Managed via the Administration Portal

The Bank (or Gateway owner) maintains full administrative control over the Hosted Checkout Page to ensure compliance, consistency, security, and alignment with corporate branding and strategic objectives across all merchants.

Available Administrative Controls:

• Global and Merchant-Specific Themes - Define and enforce default UI templates, color schemes, and layouts that apply across all merchants or selectively override individual merchant configurations.

• Brand Governance Rules - Enforce specific branding policies by restricting which customization options are editable by merchants (e.g., locking corporate fonts, disabling unsupported color variations, or hiding non-compliant layout options).

• Default Settings and Fallbacks - Set platform-wide fallback settings for:

  • Language (e.g., default to English if merchant locale is not defined)

  • Color and font defaults

  • Layout behaviors

• Security & Behavioral Configuration - Maintain centralized control of:

  • Session timeout durations

  • Redirect URL whitelists

  • Cross-site scripting protection

  • Input validation policies

• Payment Method Configuration & Strategy - Centrally manage:

  • Which payment methods are available per merchant or segment

  • Method prioritization and sorting logic

  • Pre-selection strategy (e.g., promote A2A over cards)

  • Fallback rules if a preferred method is unavailable

• Domain & DNS Control - Authorize or restrict the use of custom domains (e.g., pay.merchant.com), ensuring they meet SSL/TLS and DNS requirements.

• Accessibility & Compliance Standards - Enforce global compliance settings (e.g., WCAG 2.1 level AA), ensuring checkout pages meet accessibility, data privacy, and regulatory standards.

Key Benefits for Gateway Owners

• Enforces regulatory and brand consistency across all merchants

• Reduces support overhead through predefined templates and defaults

• Ensures PCI DSS and accessibility compliance

• Enables centralized governance over security, UX, and method visibility