Worldpay integrates into an online store either through its own hosted payment page, where a customer is sent to a Worldpay-controlled screen to enter card details, or through a direct API or iframe integration that keeps the payment form on your own site. Both methods confirm the result back to your store through a response URL you configure. We build what fires off that confirmation: order fulfillment, inventory updates, and the records a successful or failed checkout should leave behind.
A hosted payment page redirects the shopper to a Worldpay-controlled screen for the card entry itself, then sends them back to your site once it's done, along with a result, through an installation ID and a payment response URL you configure in the Worldpay merchant dashboard. It's the lower-effort option because Worldpay, not your server, handles the sensitive card data.
An iframe or direct integration keeps the payment form visually on your own checkout page while still routing the actual card data through Worldpay, which looks cleaner to a shopper but puts more integration work, and more PCI scope, on your side.
Platforms like Shopify that support Worldpay as a payment option generally wrap one of these two paths behind a simpler setup screen, which is faster to turn on but gives you less control over exactly how the response gets handled.
Getting a payment-successful response back is the easy half of an ecommerce integration. The harder half is what a store does with it: does the order actually get created, does inventory get decremented, does a confirmation email go out, and does any of that happen the same way whether the payment came through the hosted page or the direct integration.
A declined or abandoned Worldpay checkout is its own gap. A shopper who starts checkout and never completes it rarely gets followed up on, unless something is specifically built to notice an incomplete response and flag it.
A confirmed Worldpay payment can trigger order creation, inventory updates, and a confirmation email in one pass, instead of someone reconciling the payment dashboard against the order list at the end of the day.
A shopper who starts a Worldpay checkout and never finishes it can trigger a follow-up email or a flag for the team, instead of disappearing from view the moment they close the tab.
Tell us how you're currently confirming a checkout actually turned into an order, and we'll look at whether the response Worldpay already sends can drive that instead.
The checkout itself is the part most ecommerce integrations get right. What happens to that confirmation once it lands, inventory, fulfillment, following up on the ones that don't finish, is usually the part nobody built. That gap shows up on every payment processor, not just Worldpay. n-frames builds the piece that's missing, wherever it's missing.
Let's talk →Through Worldpay's hosted payment page, which redirects a shopper to a Worldpay-controlled screen for card entry, or through a direct API or iframe integration that keeps the payment form on your own site. Some ecommerce platforms, including Shopify, offer a simplified setup for one of these paths; a fully custom storefront usually needs the integration built directly.
It's the URL you configure in your Worldpay merchant dashboard that Worldpay sends the result of a hosted-page checkout back to, confirming whether the payment succeeded, failed, or was cancelled, so your site knows what happened without you having to ask.
Worldpay can be connected to a Shopify store as a payment option, typically through Shopify's third-party gateway setup rather than Shopify Payments itself. The integration still runs through one of Worldpay's standard checkout methods behind that setup screen.
Nothing, by default. If a shopper starts the checkout and never completes it, Worldpay simply never sends a successful response. Nothing follows up with that shopper unless the store has specifically built logic to notice an incomplete checkout and act on it.