Contact us
About us
Payneteasy is a leading payment platform provider. Our state-of-the-art technologies and multiple layers of flexibility boost the fastest and most efficient integration and customization.
Business type
Our clients have advantage with the full-fledged FinTech tools. Payneteasy offers technological processing solutions for different payment industry players and large-scale online businesses.
Events

Meet us at conferences around the world

SBC Summit Lisbon

SBC Summit Lisbon

29 Sep-1 Oct, 2026 Lisbon, Portugal
SiGMA Europe

SiGMA Europe

2–5 Nov, 2026 Rome, Italy
View all Upcoming Events

Hosted Fields for Branded Payment Checkouts

Your checkout. Our secure card fields.

Keep payers on your own branded checkout while card details go directly to Payneteasy.

Hosted Fields places secure card-number, expiry-date and CVV fields inside your existing checkout. Card details go directly to Payneteasy, while your server receives a token instead of the card number.

Branded checkout with card number, expiry date and CVV fields hosted by Payneteasy
How it works

How Hosted Fields Works

01

The Payer Enters Their Card Details

Card number, expiry date and CVV appear as secure fields inside your existing checkout page.

The payer enters their card details without being redirected to a separate hosted payment page.

02

Card Details Go Directly to Payneteasy

The secure card fields send the card details directly from the payer's browser to Payneteasy.

The raw card number, expiry date and CVV do not pass through your page code or backend.

03

Your Server Completes
the Payment With a Token

Payneteasy exchanges the card details for a hostedFieldsToken, which your checkout sends to your backend.

Your server then initiates the payment through the Payneteasy payment API using the token instead of the raw card parameters.

Information

Tokenization itself does not initiate the transaction.

Why it matters

Why Use Hosted Fields?

Branded checkout window with a verified badge

Keep Your Checkout and Your Design

Hosted Fields sits inside your existing checkout instead of sending the payer to a separate hosted payment page.

You control the surrounding layout, labels, non-card fields, checkout logic and Pay button.

Payment card protected by a shield

Keep Raw Card Data Out of Your Systems

Card details go directly to Payneteasy through the secure card fields.

Your page and backend work with a token instead of the raw card number, expiry date and CVV.

Code brackets for the payment API

Use the Payment API You Already Know

Hosted Fields changes how card details are collected, not how your server initiates the transaction.

The standard server-to-server payment request remains in place, with hostedFieldsToken used instead of the card parameters.

Checkout experience

Make Hosted Fields
Fit Your Interface

The surrounding checkout remains
under your control.

You decide where the card fields appear and how they fit into the rest of the form. The field containers are styled through your own CSS, while supported styles for the content inside the secure fields are configured through the Hosted Fields SDK.

This lets the card-entry step sit naturally inside your checkout without giving your page access to the card values.

Checkout where the field container is styled with your CSS and the field content with Hosted Fields SDK styles
Technical architecture

Built to Isolate
Sensitive Card Data

  • Checkmark

    Each sensitive field — card number, expiry date and CVV — is loaded inside its own Payneteasy-hosted cross-origin iframe.

  • Checkmark

    Because the field contents belong to the Payneteasy origin, your page DOM and third-party scripts running on your page cannot read the raw card values.

  • Checkmark

    The resulting hostedFieldsToken is short-lived and single-use. The original card details cannot be reconstructed from it.

  • Checkmark

    Server-side signing credentials remain on your server. The browser receives only the ephemeralTicket required for tokenization.

Checkout where the card fields load from the Payneteasy origin in cross-origin iframes
Developer integration

Add Hosted Fields to Your
Existing Payment Flow

Hosted Fields uses the Payneteasy JavaScript SDK in the browser and the standard Payneteasy payment API on your server.

View Code Examples Opens in a new tab
Server

Request an ephemeralTicket

Your server requests an ephemeralTicket for the Endpoint used for the payment.

The ticket is valid for 15 minutes and is consumed by one tokenization. Server-side signing credentials remain on your server.

01

Browser

Keep Raw Card Data
Out of Your Systems

Load the Payneteasy Hosted Fields SDK and define the containers for card number, expiry date and CVV.

The SDK creates a separate Payneteasy-hosted iframe for each card field and reports when the fields are ready.

02

Browser

Tokenize the Card Details

Payneteasy returns a hostedFieldsToken. The token is short-lived, single-use and valid for 5 minutes.

03

Server

Initiate the Payment
From Your Server

Send the token from your checkout to your backend.

Your server uses hostedFieldsToken instead of the raw card parameters in a supported Payneteasy payment request.

The payment request — not the tokenization step — initiates the transaction. Transaction status continues through the standard Payneteasy callback or status-request flow.

04

3-D Secure support

Use Hosted Fields
With 3-D Secure

Hosted Fields can be used with Payneteasy payment flows that require 3-D Secure authentication.

Hosted Fields handles card-data collection and tokenization. It does not replace transaction authentication or payment-status handling.

When authentication is required by the bank, the payer completes the required verification with their bank and then returns to the checkout.

Payment card entered in Hosted Fields
Hosted Fields

Keep Your Checkout
and Your Design

Card-data collection and tokenization inside your checkout.

Next step
Payment card with a 3-D Secure shield
If required by the bank

3-D Secure Verification

The payer completes the required verification with their bank.

Next step
Payment card returning to the checkout
Your checkout

Return to the Checkout

The payer returns to your checkout after verification.

Who it's for

Who Hosted Fields Is For

Hosted Fields handles card-data collection and tokenization. It does not replace transaction authentication or payment-status handling.

Shopping cart for e-commerce teams

E-Commerce
and Product Teams

Keep the checkout inside your own product and brand instead of redirecting payers to a separate card-entry page.

Code file for developers

Developers

Use the Payneteasy Hosted Fields SDK for card collection while continuing to work with the standard payment API on the server.

Security shield with a checkmark

Security and Compliance Teams

Keep card numbers, expiry dates and CVV out of your page code and backend while the payment flow works with a token.

Information

Payneteasy is a technology platform, not a bank or payment facilitator.

Keep Your Checkout. Leave the Card Details to Payneteasy.

Add secure card fields to your existing checkout and continue processing payments through the Payneteasy payment API.

Contact Sales Read the Docs Opens in a new tab

Hosted Fields FAQ

What are Hosted Fields?

Hosted Fields are secure card fields provided by Payneteasy and embedded inside your own checkout page. They let payers enter card details inside your checkout while those details go directly to Payneteasy.

Do payers leave our site?

Not to enter their card details. The card fields appear inside your own checkout page rather than on a separate hosted payment page. If 3-D Secure authentication is required later in the payment flow, the payer completes the required verification with their bank.

Does our system receive the card number?

No. The card details go directly from the Payneteasy-hosted fields to Payneteasy. Your checkout receives a token instead, which is then sent to your backend for the payment request.

Can Hosted Fields match our design?

Yes, within supported styling options. You control the surrounding checkout layout and field containers with your own CSS, while supported styles for the content inside the secure card fields are configured through the Hosted Fields SDK.

Does Hosted Fields support 3-D Secure?

Yes. When the bank requires 3-D Secure authentication, the payer completes the required verification with their bank and returns to the checkout.

Does tokenization complete the payment?

No. Tokenization exchanges the card details for a token. Your server still needs to initiate a supported Payneteasy payment request using that token.

How long is the Hosted Fields token valid?

The hostedFieldsToken is valid for 5 minutes and is single-use. A new payment attempt requires a new tokenization flow.

How do developers get started?

Start with the Hosted Fields documentation for SDK setup, ephemeralTicket creation, tokenization and supported payment requests. Payneteasy also provides reference integrations and code examples for multiple server stacks.