Hosted payment pages

Back to APIs

Paythru's hosted payment services take the headache out of payment. Not only do they save you development effort, but also reduce your PCI DSS compliance obligations. Choose from our standard pages, bespoke pages and a lot more besides.


Paythru's hosted payment pages have been designed specifically to render well and operate effectively on devices of all sizes and capabilities. Payment interfaces may be locked to one particular device channel (e.g. mobile) or may be configured to adapt according to the requesting device automatically. If necessary, the merchant may specify which layout to display in their request to their API. Responsive web design layouts may also be used for a 'one size fits all' solution.

Paythru's Hosted Payment Pages may also be used to accept payments within mobile applications. Please refer to our 'Accepting Payments in Mobile Applications' datasheet for more information.

'Off the peg' or 'tailor made'

The payment interface may be delivered in one of Paythru's standard templates, or if necessary, in a bespoke template. Bespoke templates are often used to replicate the look and feel of the referring website so the customer is often unaware that they have been redirected elsewhere.

Our standard pages have a modern look and feel, and allow some customisation. A number of colours and a logo may be included to ensure a payment journey consistent with your company's branding.

Multiple payment types

All payment types available from Paythru are available in our hosted interfaces. The merchant simply nominates the required payment type in their request to Paythru's Enterprise API.

Multi language

The interface may be delivered in a choice of languages. For international merchants or merchant in multilingual territories, the merchant may nominate in which language they would like the interface presented to the customer.

Payment Form configuration

It is often necessary to capture more information from the customer than the card details alone. For example, the address of the card holder is often required by the bank for address verification purposes. The shipping address may also be required by the merchant. The payment form may be configured to capture as little or as much data from the customer as required. The form may also be divided into stages, so the customer completes one section before moving on to the next. A variety of predefined fields may be chosen or custom fields used where a precise field is unavailable. Address lookups are available to UK based merchants, making it simpler for the customer to complete address fields.

Redirection after payment

Merchants may choose whether the customer is redirected back to the merchant's website immediately after payment, or if the result of the payment is delivered by Paythru. Please note that 'auto-redirect' is not available for merchants using Paythru authenticated card storage.

Card storage

Paythru's Hosted Payment Pages may be configured to allow customers to store their payment cards for a faster checkout experience when they return. The pages can be set up to request a username and password from the customer immediately after payment that may be used to retrieve their card details when they return, or if the customer has already authenticated with the merchant before checkout, the stored card may be presented with no further authentication. In a addition to the payment card, other details of the user such as their address may also be stored if necessary. For more information of card storage with Paythru, please refer to our Card Storage an Tokenisation datasheet.

Enterprise API

Integrating with Paythru's hosted Payment Interfaces will usually require integration with our Enterprise API. The API is a simple web service that you send the checkout information to, and the URL of the payment interface is returned. Merchants may also choose to integrate with our callback notifications that provide you with full details of your transactions in real time.

Prefer to host the interface yourself?

Merchants wishing to host the entire payment experience may be prefer to use either our Gateway or Express APIs. For more information, please refer to our Application Programming Interfaces (APIs) datasheet.