Hosted Payment PageExtend your integrationSave a customer's payment details

Load the Hosted Payment Page

View as Markdown

An AI skill is available for this guide, get it on the Skills Marketplace (GitHub).

When your customer wants to save their payment details, load the Hosted Payment Page. To do this, add a button to your checkout page that sends a POST request to our gateway. When we receive the POST request, the Hosted Payment Page loads and the customer can submit their payment details.

Note: The Hosted Payment Page doesn’t return a transaction type in the transaction response. Because you can run sales, run pre-authorizations, and save a customer’s payment details, we recommend that you record the transaction type in your system.

You can also use this page to update a customer’s payment details. When you load the Hosted Payment Page, provide the MERCHANTREF to indicate the customer’s secure token that you want to update and send a value for the ACTION parameter of update instead of register.

Send a POST request to load the Hosted Payment Page

To load the page, send a POST request to the Secure Card Page URL.

Request parameters

To create the body of your request, use the following parameters:

ParameterTypeSizeDescription
ACTIONEnumIndicates if the customer is saving new payment details or if they are updating existing payment details. The value is one of the following:
- register - Customer is saving new payment details.
- update - Customer is updating existing payment details.
TERMINALIDString1-50 charactersUnique identifier that we assigned to the terminal.
MERCHANTREFString1-200 charactersUnique identifier that the merchant assigns to the secure token.

Note: We recommend that you store this value.
DATETIMEStringDate and time that you send the request. Send this value in DD-MM-YYYY:HH:MM:SS:SSS format, for example, 06-02-2026:12:23:23:719.
HASHString1-128 charactersSHA-512 hash value that you generate with values from the request parameters and the terminal secret. For more information about how to create your hash, go to [Authenticate your requests].
STOREDCREDENTIALUSEEnumIndicates how the merchant can use the card details, as agreed by the customer:
- UNSCHEDULED - Transactions for a fixed or variable amount that are run at a certain predefined event.
- RECURRING - Transactions for a fixed amount that are run at regular intervals, for example, monthly. Recurring transactions don’t have a fixed duration and run until the customer cancels the agreement.
- INSTALLMENT - Transactions for a fixed amount that are run at regular intervals, for example, monthly. Installment transactions have a fixed duration.

Note: Send a value for this parameter if the customer is saving card details.

Next steps