03.02 Hosted Payment Page

Status: draft for discussion

1. Goal

Hosted Payment Page is the main payment flow page shown to the customer.

Customer opens the link that merchant received when creating the deposit.

2. Scenario

1. Customer opens Hosted Payment URL.
2. The page shows loading while the system prepares the payment flow.
3. If the selected execution path requires additional customer fields, the page shows a form.
4. Data already provided by merchant must be prefilled and available only for viewing, without editing.
5. After the form is completed, the system continues transaction execution.
6. If provider returns a redirect URL, customer is redirected further. The system must also support cases where a payment provider does not return a URL and the payment needs a different handling approach, for example showing an Apple Pay button on our Hosted Payment Page.
7. If payment cannot continue, customer sees a clear error message.

3. Required Page States

Hosted Payment Page must support these business states:

• loading while transaction and routing result are prepared;
• additional customer fields form;
• payment action, for example redirect or wallet button;
• waiting state when payment is in progress;
• clear error state;
• expired session state.

Customer should not need to understand transaction status names.

The page should guide the customer to the next action.

4. Additional Fields

Sometimes a provider requires additional customer attributes.

Customer must see clear field names, not names from provider integration.

The MVP page language is English. The solution should still allow localization later.

5. Redirect Behavior

For the MVP, redirect is the preferred option when supported.

This helps avoid issues where provider redirects happen inside an iframe.

If the development team proposes a safe iframe approach for specific providers, it can be reviewed separately.

6. Brand Context

Hosted Payment Page receives brand context.

Full visual brand customization is not included in the MVP, but the system must understand which brand the payment belongs to.

7. End User Experience

The page must be fast and clear because the customer is an end user trying to complete a deposit.

The page should avoid unnecessary explanations and should not expose internal platform logic.

If payment cannot continue, the message should be short, understandable, and safe to show to the customer.