Worldpay eProtect
docs.worldpay.com
- Web
- iPhone and iPad
- Android
- API
What Worldpay eProtect is
Worldpay eProtect is a cloud service for card-not-present payments that reduces the amount of payment data handled by a merchant’s systems. It replaces card details with a low-value Registration ID, which Worldpay can exchange for an OmniToken during authorization, a sale or token registration. That token may support later card-on-file payments, returns and recurring billing. Merchants can integrate through a hosted iFrame, a JavaScript Customer Browser API or a Mobile API. The iFrame keeps card number, expiration and CVV2 fields in Worldpay’s PCI-compliant environment. With JavaScript, the account number is validated and encrypted before being sent to Worldpay, which returns a Registration ID. Worldpay says card data does not pass through the merchant’s web server and eProtect reduces applicable PCI controls. The guide covers Apple Pay, Apple Pay on the Web, Google Pay and Visa Checkout. The iFrame includes inline validation and configurable form behavior; version 4 improves screen-reader accessibility for expiration fields and error messages. Before production use, an organization must be enabled and certified for OmniTokens, obtain a PayPage ID and complete certification testing. eProtect does not validate CVV, AVS or expiration dates. Pricing is on request.
Who it suits
It suits merchants handling card-not-present payments who want token-based transactions and hosted payment fields. Organizations must meet the OmniToken enablement, PayPage ID and certification prerequisites before production use.
Good to know, and what to watch
- Offers iFrame, JavaScript and Mobile API integrations
- Card data does not pass through merchant web server
- Tokens can support recurring billing and returns
- Includes wallet payment integration guidance
- Lists 24/7 critical-issue technical support
- Does not validate CVV or AVS
- Does not validate expiration dates
- Certification is required before production use
- Pricing is on request
Getting started
- Open the eProtect integration guide
- Obtain enablement and certification to process OmniTokens
- Get a PayPage ID from the eProtect Implementation Consultant
- Choose the iFrame, JavaScript Customer Browser, or Mobile API integration
- Complete eProtect certification testing before production
Limits to check
The token exchange does not check CVV or AVS information and does not validate expiration dates. Production access is gated by OmniToken enablement, a PayPage ID, and successful certification testing.
The verdict
eProtect provides several integration paths and a token flow intended to reduce card-data exposure in merchant systems. Its validation limits and onboarding requirements should be addressed as part of payment integration planning.
Questions people ask
What does eProtect do?
It supports card-not-present payments while reducing the card data stored in merchant systems through tokenization.
Which integration methods are available?
The guide describes a hosted iFrame API, JavaScript Customer Browser API, and Mobile API.
Which wallets are covered?
The guide includes Apple Pay, Apple Pay on the Web, Google Pay, and Visa Checkout.
Can tokens support recurring billing?
Yes. An OmniToken may be used for card-on-file transactions, returns, and recurring billing.
What is required before production?
An organization must be enabled and certified to process OmniTokens, obtain a PayPage ID, and complete certification testing.
How is pricing handled?
Pricing is available on request.
What the maker publishes
- Accessibility
- The guide says iFrame version 4 improves screen-reader accessibility for expiration fields and error messages; version 3 lacks those upgrades. source
- Availability
- Worldpay says primary and secondary endpoint routing supports high availability for eProtect JavaScript API version 3 or higher. source
- Card data handling
- The guide states that card data is not transmitted through the merchant web server and that the token server stores the card number but not CVV or expiration date. source
- Certification
- The guide says successful eProtect certification testing is required before production use. source
- Checkout features
- The iFrame offers real-time inline field validation, configurable payment-form behaviors, and account-number auto-formatting based on card type. source
- Company headquarters
- Worldpay states that it is headquartered in Cincinnati, Ohio, United States. source
- Follow-on payments
- The guide says an OmniToken may be used for card-on-file transactions, returns, and recurring billing. source
- Hosted card fields
- With the iFrame API, payment card fields are hosted from Worldpay’s PCI-compliance environment instead of being embedded in the merchant checkout page. source
- iFrame fields
- The iFrame API hosts sensitive payment fields, including card number, expiration date, and CVV2, in Worldpay’s PCI-compliant environment. source
- Integration methods
- The guide describes iFrame API, JavaScript Customer Browser API, and Mobile API integrations. source
- Integration options
- The guide describes iFrame, JavaScript Customer Browser API, and Mobile API integration options. source
- JavaScript handling
- The JavaScript API validates and encrypts the account number before sending it to Worldpay and returns a Registration ID in its place. source
- Onboarding requirement
- Before using eProtect, an organization must be enabled and certified to process OmniTokens and obtain a PayPage ID from its eProtect Implementation Consultant. source
- Payment methods
- The guide includes integration instructions for Apple Pay on the Web, Google Pay, and Visa Checkout. source
- Payment types
- The eProtect PCI Non-Sensitive feature can tokenize private-label and Worldpay gift cards, subject to the Worldpay message interface specification. source
- Prerequisites
- Before using eProtect, an organization must be enabled and certified to process OmniTokens and obtain a PayPage ID from its eProtect Implementation Consultant. source
- Purpose
- eProtect is designed for card-not-present payments and reduces the amount of payment data in a merchant’s systems. source
- Security and PCI
- Worldpay says no card data is transmitted through the merchant’s web server and that eProtect reduces applicable PCI controls. source
- Support
- The guide lists 24/7 technical support for critical production issues and says technical support representatives respond to eCommerce technical issues within 15 minutes. source
- Token flow
- eProtect returns a low-value Registration ID, which Worldpay can exchange for an OmniToken during authorization, sale, or token registration. source
- Tokenization
- It exchanges card details for a low-value Registration ID, which is exchanged for a Worldpay token during a transaction. source
- Token use
- The guide says the resulting OmniToken can be used for follow-on transactions such as card-on-file, returns, and recurring billing. source
- Validation limit
- The guide states that eProtect’s token exchange does not check CVV or AVS information and does not validate expiration dates. source
- Wallets
- The guide includes eProtect support sections for Apple Pay, Apple Pay on the Web, Google Pay, and Visa Checkout. source
Checked against the maker's pages on 7 Oct 2026.