Payment Page Templates
Hyp Enterprise supports two main payment page templates that define the overall layout, user experience, and behavior of the payment page:
Hyp Basic: The current default template, providing the existing payment page look and behavior. Most UI examples and instructions in this documentation use this template.
Hyp Standard: A new template option that provides a different layout. Unlike Hyp Basic, which navigates to a separate full-screen view when a payment method (e.g., Google Pay) is selected, Hyp Standard keeps the payment method selector visible at the top of the page. This template currently does not support Pay By Link or PCP.
Configuring templates
You can configure which template to use by setting a default template in the Hyp Console or by choosing a template on a per-request basis.
Configuring the default in the Hyp Console
To set a default template that will be used on all payment pages unless overridden per request:
Open your Hyp Console.
In the sidebar, click Merchant details.
Expand the Merchant settings section.
Click Gateway management settings.

Navigating the Hyp Console Under Gateway management settings, open the Payment Account Payment Management (MID) tab.
Click the name of a merchant ID (MID) in the table. The default template is configured per MID, so you may need to repeat this and the following steps for each MID that you have.
In the MPI account information form, use the Default PPS template dropdown to set a default template:

Selecting a default template Optionally, you can set different default templates for:
Pay By Link: Use the PPS template - Payment link J206 dropdown.
Payment requests: Use the PPS template - Payment link J306 dropdown.
Currently, the default template for all new terminals is Hyp Basic.
Choosing a template per request
You can specify the template for a specific transaction by including the template property inside the uiCustomData object within ppsJSONConfig:
The template specified in ppsJSONConfig overrides the default template selected for the MID that your request uses.
Customization and ppsJSONConfig
Most customization options available via ppsJSONConfig (such as custom logos, styles, and text) are expected to apply to both Hyp Basic and Hyp Standard templates.
Last updated
Was this helpful?