Worldpay connected, tested and ready for volume
Worldpay hosted pages or direct integration on your store or custom platform, with 3-D Secure, tokenisation, refunds and settlement reports checked before go-live. For UK, EU and US merchants whose bank or acquirer requires it. From €890.
Stations are generic roles. With Worldpay, one company can act as both gateway and acquirer; the card scheme and the issuing bank are separate.
Your store sends the payment
Your checkout sends the amount, currency, order reference and the card details collected by the provider’s page or fields to the gateway.
what can fail here- Amount sent in the wrong minor units, such as 12.50 instead of 1250
- A double-click on Pay creating two orders
- API credentials expired after a key rotation
How I test it: Duplicate-submit and wrong-amount cases on staging, before any live key exists.
Response codes are the common ISO 8583 values; exact codes and texts vary by acquirer.
Check my payment setupFrom merchant agreement to first settlement
Worldpay projects go wrong at the edges: credentials for the wrong environment, a currency not enabled, a report nobody reconciles.
- 1
Requirements
Merchant agreement, enabled currencies and card types, and the integration type agreed with your account manager.
- 2
Test environment
Test credentials and the provider's test cards, every 3-D Secure outcome and decline path.
- 3
Tokens and refunds
Stored tokens for repeat purchases and refunds, partial refunds, voids before settlement.
- 4
Reconciliation
Settlement reports matched to orders line by line, with fees and refunds accounted for.
- 5
Go-live
Live credentials, one low-value payment and refund, and decline rates watched for the first week.
PCI scope in three plain steps
How you take the card decides how much card data touches your server, and so how much security paperwork lands on you. This is an explainer, not legal or compliance advice.
Dashed orange: card number and security code. Solid grey: token or payment result only.
Hosted fields
The card fields sit inside your checkout, but each field is a small frame served by the provider. Your page gets back a token.
- On your server
- A single-use token
- Your page's scripts
- Share the page with the fields, so they need watching
- Questionnaire
- Often SAQ A, with extra checks on payment-page scripts
Your acquirer decides which PCI DSS self-assessment applies to you. Check its guidance and your own obligations.
Your bank says Worldpay, your platform says nothing. I connect the two.
Get a Worldpay quoteWorldpay or Stripe, honestly
Both take card payments well. The difference is mostly how you sign up and who the contract suits.
| Question | Worldpay | Stripe |
|---|---|---|
| How you sign up | Usually a sales conversation and a merchant agreement, sometimes arranged through your bank | Online sign-up and identity checks |
| Who it tends to suit | Merchants with volume, an existing acquiring relationship or a bank requirement | New and growing stores that want to start quickly |
| Integration options | Hosted payment pages, hosted fields and direct APIs | Hosted Checkout, an embedded payment form and APIs |
| Pricing | Set in your contract | Published standard rates, with custom pricing possible |
General descriptions, not a fee comparison. Check each provider's current pages and your own contract offer.
When I would not recommend Worldpay: a new, small store with no bank or acquirer requirement will usually launch faster with a self-serve provider such as Stripe, or with Finnish payment methods for Finnish buyers. Selling into Britain? See web and ecommerce for UK businesses.
Questions about Worldpay
When is Worldpay a better fit than Stripe?
When your bank, acquirer or group already requires it, when your volumes justify negotiated pricing, or when an older platform has a Worldpay connector and nothing else. For a new store without those reasons, a self-serve provider is usually quicker to launch. I will tell you which fits after one look at your setup.
Can you integrate with a custom or older platform?
Usually, yes. Custom and older PHP stores are everyday work for me. I add a hosted payment page or hosted fields so card data stays off your server, and where the old code cannot be changed safely, I build a small separate payment service that the platform calls instead.
Who handles PCI requirements?
You do, as the merchant, and your acquirer decides which self-assessment applies. Worldpay looks after its own systems. I build so the least possible card data touches your server, usually through a hosted page or hosted fields, and document it for your questionnaire. Pikselipolku never holds card data or money and does not certify compliance.
Worldpay packages
Fixed prices, excl. VAT. Worldpay's own fees are set in your contract with Worldpay.
Hosted payment page
- Redirect and return handled
- 3-D Secure and decline paths tested
- Notifications update your orders
- Refunds from your admin
Hosted fields and tokens
- Card fields inside your own checkout
- Tokens for repeat purchases and refunds
- Settlement report reconciled to orders
- Payment-page script inventory
Direct or legacy platform
- Older or custom platforms
- Separate payment service where needed
- Magento and large-catalogue stores
If it does not work out: if the integration fails the test list we agree in writing, I keep working on it until it passes, at no extra cost.
Get a Worldpay quote
Tell me your platform, your markets and what your bank or acquirer has asked for. You get a written fixed price within one working day.
Pikselipolku does not process payments or hold card data. You sign the merchant agreement with the provider, and card data stays with the provider.
Pikselipolku is an independent studio and is not affiliated with Stripe, PayPal, Worldpay, Klarna, Paytrail or any other provider named here.
Or email [email protected]