Standalone payment page

The main goal of this project is to provide guests with a secure, user-friendly way to pay online via a dedicated payment link. The amount due is dynamically retrieved from the system to ensure accuracy at the time of payment. After completing the transaction, guests are redirected to a status page that confirms whether the payment was successful or not. This page also includes links to the user’s personal environment and to the general search page for further navigation.

Payment Page Setup (Web manager)

Create a new standalone payment page and attach it to the sitemap using a friendly URL such as /make-payment (or another appropriate slug).
This page should include:
1. the Bill
2. the payment widgets (instalments and payment methods), which can be copied from either the Bookflow payment step or the reservation details page in My Environment via template.
In addition, the page must have standard site elements—such as the header and footer—styled consistently with the brand’s design guidelines.
Optionally, title, intro text and reservation information, such as dates, travel party, accommodation name, location and image.

screencapture-lib-cms-test-maxxton-net-online-betalen-2025-07-18-16_41_31.png

If a reservation is expired, cancelled, or declined, the payment widgets are not displayed to the user. In such cases, it is recommended to show a fallback message with appropriate information. This can be implemented using conditional logic based on the reservation status.

Privacy Consideration

Please ensure that no widgets are added to the payment page that could reveal personal information, such as the guest’s name, travel party details, or other sensitive data.
Only include the information strictly necessary for completing the payment to minimize the risk of misuse.

Status page setup (Web manager)

Create a status page and attach it to the sitemap using a friendly URL such as /payment-result (or another appropriate slug).
Page should display payment status: successful or failed. It’s done with Payment status widget and bill.
You may also include:
- The Bill widget to summarize the transaction.
- Buttons linking to My Environment login and the Search page for continued navigation.
Additional content can be conditionally displayed based on the payment status using a conditional set. Below is an example of a result page for a successful payment:

And here is example of success page for failed payment with different text:

Link setup in Templates (Notification manager) and Testing

Guests receive a link to the standalone payment page via email. This link is configured within an email template and is valid only when sent through Maxxton mailing.

Maxxton provides clear instructions to clients on how to correctly insert this link into relevant templates—such as reservation confirmations, payment reminders, and other applicable messages.

Before deploying the payment page to the client, it is strongly recommended to set up a test email template and a test report to validate the full flow.
The simplest way to do this is to:

Duplicate an existing email template that contains the old payment link.
Replace the old link with the new standalone payment page URL.
Create a test report linked to the new test template to ensure the link works correctly and the page behaves as expected.

How to add payment link into Legacy/HTML code templates

Here is a test template where you can check how configuration was done: https://lsh.maxxton.net/notificationmanager/en-us/templates/template/2392004?showArchived=false

Set the variable for the URL at the top of the HTML document. URL should be different per language.

<!-- New paymentLink   -->
#set($newPaymentLink = "")
#set($tokenName = $messageTool.generateJwtToken())  
#set($newPaymentLink = "https://www.clienthostname.com/make-payment?reservationid=$reservation_id#universalAuthToken=$tokenName")

Add the link anywhere in the body of the template or replace old link using only href parameter

<a href="$newPaymentLink" style="" target="_blank">
    Pay                                                                                    
</a>

Note: Legacy templates require you to update the template for each translation. So you update 1 language and then do the same for another.

Examples: LSH, FCS

How to add payment link into new templates

Add link for each language to the visual button element:

Example: LIB

How to test payment link via Notification manager

For both old and new templates it can be done via Preview, if you select a reservation that has a due amount to pay.

FAQ’s

If widget configuration is correct, check if the payment link in a template is missing token responsible for display of this data.

If you can not send any report, check if you have permissions to send reports on this concern & environment.
Secret may be missing on this environment. Please ask MXTS developers to check.

List of clients using Standalone payment page

Can be found in this table: https://maxxton.atlassian.net/wiki/spaces/POL/pages/edit-v2/5013964