Hosted Payment Page

The Hosted Payment Page is used when a payment flow requires customer interaction during checkout. It is not a standalone integration method. Merchants integrate with Dinape through the Payment API, and Dinape determines whether a hosted payment page is needed based on the payment request, channel configuration, payment method, and provider requirements.

When a hosted page is required, Dinape redirects the customer to a Dinape-hosted checkout page where they can select or confirm the payment method and complete any required payment steps.

How it works

A typical hosted payment page flow includes these steps:

1. The customer starts checkout in your shop.
2. Your backend creates a payment through the Payment API.
3. Dinape evaluates the request, channel configuration, selected payment method, and provider requirements.
4. If customer interaction is required, Dinape provides a hosted payment page flow.
5. The customer completes the required payment steps on the Hosted Payment Page.
6. Dinape redirects the customer back to your shop.
7. Dinape sends the payment result to your callback URL.
8. The transaction can be reviewed in Transactions.

Before you start

Before using the Hosted Payment Page, make sure you have:

• a configured channel
• at least one payment provider connected to the channel
• at least one payment method available for the channel
• API credentials for the channel
• payment URLs configured for success, failure, cancellation, and callbacks

For payment provider setup, see Integrations Overview.

Create the payment request

Your backend creates the payment through the Payment API.

The request identifies the channel that should process the payment and includes the payment details required for the transaction. The channel determines which provider configuration and payment methods are available.

If the request includes a specific payment method, Dinape uses that payment method where possible. If no payment method is provided, or if customer selection or confirmation is required, Dinape can route the customer through the Hosted Payment Page.

Redirect the customer

After the purchase is created, Dinape returns a link to the Hosted Payment Page.

Redirect the customer to this link so they can complete the payment. On the Hosted Payment Page, the customer reviews the payment amount and completes the payment with one of the available payment methods.

Handle the payment result

After the payment is completed, Dinape redirects the customer to one of the payment URLs configured for the channel or provided for the checkout session.

The redirect depends on the payment outcome:

• Return success URL: used after a successful payment
• Return failure URL: used after a failed payment
• Return cancel URL: used when the customer cancels the payment

Dinape also sends the payment result to the configured Callback URL. Use the callback to update the payment status in your shop or backend system.

WARNING

Do not rely only on the customer redirect to confirm the payment result. Use the callback notification to update the transaction status in your system.

Configure payment URLs

You can configure payment URLs on the selected entity in Configuration.

The available payment URLs include:

• Main URL
• Return success URL
• Return failure URL
• Return cancel URL
• Callback URL
• FAQ URL
• Terms conditions URL
• Privacy policy URL
• Imprint URL

For more information about entity configuration, see Configure Account.

Customize the payment page

The Hosted Payment Page can use your brand elements, such as logo, favicon, and primary color.

Branding settings are managed in Dinape configuration and white label settings. For more information, see White Label overview.

Next steps

Test the checkout flow

Use the Demo Online Shop to test how a hosted checkout flow works before using it in your own shop.

Continue to Demo Online Shop

Review transactions

Review created transactions and follow their status in Dinape.

Continue to Transaction Overview