Spreedly vs Worldpay eProtect
Spreedly
spreedly.comWorldpay eProtect
docs.worldpay.comSide by side
| Figure | Spreedly | Worldpay eProtect |
|---|---|---|
| Price from | $750/mo | — |
| Free plan | — | — |
| Free trial | — | — |
| Open source | — | — |
| Web | Yes | Yes |
| iOS | — | Yes |
| Android | — | Yes |
| API | Yes | Yes |
| Plans published | 2 | 0 |
| Spec score · Payment Tokenization Software | 7.1 (#12) | 7.1 (#13) |
| Purpose | Spreedly connects businesses to payment services through a single API and supports payment orchestration. | eProtect is designed for card-not-present payments and reduces the amount of payment data in a merchant’s systems. |
| Support | Spreedly links to a Support Portal and developer guides and documentation from its official site. | The guide lists 24/7 technical support for critical production issues and says technical support representatives respond to eCommerce technical issues within 15 minutes. |
| Tokenization | Spreedly stores tokenized payment methods in its vault so merchants can use them with multiple gateways and endpoints. | It exchanges card details for a low-value Registration ID, which is exchanged for a Worldpay token during a transaction. |
Plans
In their own words
Worldpay eProtect
Worldpay eProtect handles card-not-present payments by replacing card details with a low-value Registration ID, which Worldpay can exchange for an OmniToken during authorization, a sale, or token registration. The cloud service is available through an iFrame, the JavaScript Customer Browser API, or a Mobile API, with platforms listed as Android, iOS, web, and API. Worldpay says card data does not pass through the merchant’s web server and that eProtect reduces applicable PCI controls. The iFrame hosts card number, expiration, and CVV2 fields in Worldpay’s PCI-compliant environment; JavaScript validates and encrypts the account number before sending it to Worldpay. The resulting token may support card-on-file payments, returns, and recurring billing. The guide covers Apple Pay, Apple Pay on the Web, Google Pay, and Visa Checkout. Before production use, an organization must be enabled and certified to process OmniTokens, obtain a PayPage ID, and complete certification testing. The token exchange does not check CVV or AVS and does not validate expiration dates. Pricing is on request.