Card Fields: keep your checkout, drop the card-data burden

Card Fields let a merchant build its own branded checkout and drop in three secure Omno card fields: card number, expiry and CVV. The merchant styles them through the Omno SDK, so shoppers never see Omno. Card data goes straight to Omno and never touches the merchant's servers, and every payment runs through Omno's merchant-set routing rules, cascading and BIN-based routing.

Updated

Card Fields: your checkout and your Pay button; the dashed fields are the three Omno card fields, styled to match. Example values.

In 30 seconds

  • Your own checkout and Pay button, with three secure Omno fields styled to match: card number, expiry and CVV.
  • Card data never touches your servers, which can significantly reduce your PCI DSS scope; your assessor confirms your level.
  • Every payment runs through the full Omno card engine: your routing rules, cascading and BIN-based routing.
  • 2 min read
  • 7 features
  • 3 settings you control
Talk to us

What it does

Own the experience
Your layout, flow and Pay button. The fields are styled through the SDK, from font and colours to placeholders and error states.
Stay out of card data
Your website and servers never see or store card details. They go straight from the field to Omno.
Can significantly reduce your PCI DSS scope
Compared with a direct API integration that handles raw card data. Your own assessor confirms your PCI DSS level.
Shoppers stay on your checkout
Success, decline and error results show on your page. Some card payments still need a bank 3-D Secure check.
Real-time field validation
Errors are caught as the shopper types, before they press Pay.
Full Omno card engine
Your routing rules, BIN-based routing, all Omno card providers, and cascading to the next provider when one is unavailable or rejects the request. Same webhooks and reporting.
Fast to launch
The same Omno SDK and session flow as the hosted checkout. Existing Omno merchants keep their backend integration.
On this page4 sections

How do Card Fields work?

Card Fields are the card half of Omno Custom Checkout: your checkout, with no Omno payment page and no Omno branding. A payment takes five steps.

  1. Your backend creates a payment session with Omno.
  2. Three secure Omno card fields appear inside your checkout, styled to match it.
  3. The shopper enters their card details and presses your own Pay button.
  4. Omno receives the card data, then routes and processes the payment.
  5. The result shows on your page, and your backend receives the usual webhook.

Because the session flow and the SDK are the same as for the hosted checkout, an existing Omno merchant keeps its backend integration and changes only the front end.

What stays yours, and what does Omno run?

Everything the shopper sees is yours: the page, the layout, the order summary and the Pay button. The three fields take on your checkout’s look through the Omno SDK, with its set of options for font, colours, placeholders and error states. Errors are caught as the shopper types, so a mistyped card number is flagged before they press Pay.

Behind the fields, Omno runs the same card engine as every other Omno card payment. Your routing rules pick the provider by card BIN, country, currency, amount, browser information or customer segment. If a provider is unavailable or rejects the request, the payment moves to the next provider in the rule until one accepts. Final statuses arrive by webhook, and every attempt appears in the same transaction trail and reports.

How do Card Fields affect PCI DSS?

Card data goes from the fields straight to Omno, so your website and servers never see or store card details. Compared with a direct API integration, where your systems handle raw card data, that can significantly reduce your PCI DSS scope. Your own qualified security assessor decides your level and the questionnaire that applies to you. For the background, read our guides on PCI DSS for hosted checkout merchants and host-to-host card payments.

When should you choose Card Fields?

Choose Card Fields when your team wants full control of the checkout’s layout and conversion and will not send shoppers to a payment page that looks different from the rest of the store. Choose the hosted checkout when you would rather have Omno host the page and change it in the no-code builder, with every method in one place. For local methods and wallets on your own checkout, pair Card Fields with Direct Links.

Settings you control

Field styles
Font, colours, placeholders and error states for the three fields, from the set of options the SDK offers.
Routing rules
The same rules as any card payment, by card BIN, country, currency, amount, browser information or customer segment.
Webhook endpoint
Where Omno delivers the final status of each payment.
Developer guide

Frequently asked questions

What are Card Fields?

Three secure Omno fields for card number, expiry and CVV that sit inside your own checkout page. You build the page and the Pay button; Omno receives the card data from the fields, routes the payment and processes it.

Do Card Fields reduce my PCI DSS scope?

They can significantly reduce it compared with a direct API integration, because card data goes straight to Omno and never touches your servers. Your own qualified assessor decides your PCI DSS level and the questionnaire that applies to you.

What can I style?

The fields follow your checkout through the Omno SDK, including font, colours, placeholders and error states, from the set of options the SDK offers. Everything around the fields, including the layout and the Pay button, is yours.

Does 3-D Secure still apply?

Yes. Shoppers stay on your checkout and see the result on your page, but some card payments still need a check with the cardholder's bank through 3-D Secure.

Do I keep routing and cascading with Card Fields?

Yes. Card Fields payments run through the full Omno card engine. Your routing rules pick the provider, BIN-based routing works as usual, and if a provider is unavailable or rejects the request, the payment moves to the next provider in the rule until one accepts.

it will.

Tell us where your payments fail. We will show you how routing changes the outcome.

esc
↑↓ to move ↵ to open All results