Should a checkout redirect customers to a separate payment page?

It is better to keep the customer in the merchant's environment than to send them to an unfamiliar page. A hosted page can still do that when its look matches the merchant's site. On NORBr, the Smart Checkout hosted page runs behind a CSS layer the merchant controls, so colors, fonts and buttons stay consistent from cart to confirmation.

What the customer feels

A redirect to a page that looks different from the shop, with another domain in the address bar, breaks trust at the moment the customer is about to type a card number. Research on checkout abandonment consistently lists lack of trust and unfamiliar pages among the top reasons shoppers leave. Embedding the payment in the merchant's environment avoids that break.

Hosted does not have to mean foreign

• A hosted payment page can be styled to match the merchant's site: colors, fonts, buttons, logo.
• It can be served on a domain the customer recognizes.
• It keeps the PCI DSS scope with the provider, which is the reason to host it in the first place.

How it works on NORBr

The Smart Checkout hosted page runs behind a CSS layer the merchant controls. The merchant sets the visual identity once, and every page from cart to confirmation looks like its own. The operator gets the compliance and maintenance benefits of a hosted page, and the merchant gets the conversion benefits of an embedded one. Operators can also offer embedded fields for merchants that want full control of the layout, with the same tokenization underneath.