Skip to content
Last updated

Hosted Payment Fields

🧪 Beta. Hosted Payment Fields is in Beta and available on request. Ask your Omno integration team to enable it for your account.

New to HPF? Start with the concept guide: Hosted Payment Fields.

Hosted Payment Fields (HPF) let you build a fully custom, fully branded checkout page while Omno hosts only the sensitive card inputs. You embed four Omno-hosted iframe fields — card number, expiry, CVV and cardholder name — into your own layout.

Why use it

  • Lower PCI scope. Raw card data is entered inside cross-origin Omno iframes, so your page and server never touch the card number or CVV — keeping your PCI scope at SAQ A / A-EP instead of SAQ D.
  • Your UI. You own the whole page; Omno owns only the card fields.
  • No redirect. The payment completes against the existing session in-page.

Scope

  • Card pay-in only in this release.
  • No Cashier token — HPF field iframes load with the sessionId only. mountFields() takes no token.
  • Your checkout domain must be registered with Omno (frame-ancestors), or the browser blocks the field iframes.

How it works

Payment ProviderOmnoYour BackendYour Checkout PagePayment ProviderOmnoYour BackendYour Checkout PageCreate a card session (/v3/public/cashier/session, paymentTypes ["CARD"])sessionIdsessionIdmountFields({ sessionId, fields })submit() — card data stays in Omno iframesProcessResultPAYMENT_SUCCESS / FAILED / PENDING (UI only)Webhook (authoritative final status)
Payment ProviderOmnoYour BackendYour Checkout PagePayment ProviderOmnoYour BackendYour Checkout PageCreate a card session (/v3/public/cashier/session, paymentTypes ["CARD"])sessionIdsessionIdmountFields({ sessionId, fields })submit() — card data stays in Omno iframesProcessResultPAYMENT_SUCCESS / FAILED / PENDING (UI only)Webhook (authoritative final status)

Build it →