Skip to main content

Hosted payment page

The hosted payment page is a Hubpay checkout reached by redirect. Hubpay handles the payment interface while your application controls the order, payer and return journey.

Use this model when you want a checkout integration without collecting payment details in your own interface.

How it works​

  1. Create or identify the payer
  2. Upload a supporting document if your account or payment method requires one
  3. Create a payment request with executionMode set to HOSTED_PAGE
  4. Redirect the customer to the returned paymentUrl
  5. Receive the customer at your success or cancellation URL
  6. Confirm the payment from a signed webhook or API lookup

Your backend must create the payment request. Do not expose Hubpay client credentials in browser code.

Redirects and payment state​

A redirect to successRedirectUrl means the customer completed the checkout journey. It does not always mean funds have been received or settled. For example, a bank-transfer customer may have received instructions but not yet sent the transfer.

Use payment lifecycle webhooks and fetch the payment request to determine the current status before taking a backend action.

Session security​

The hosted paymentUrl contains a signed sessionToken that is valid for one hour.

If the token expires while the payment request is still UNPAID or PART_PAID, call Refresh payment session. The response contains a new payment URL and one-hour session.

Branding​

Your Hubpay-hosted checkout can use the colours and logo configured for your account. See Payment page branding.

Next steps​