less than a minute read • Updated 2 hours ago
Worldline Hosted
Connect Foxy to Worldline Hosted for secure payments.
- Countries
Austria, Belgium, Bulgaria, Croatia, Czech Republic, Denmark, Finland, France, Germany...Show more
- Features
- Auth Only & Delayed Capture
- Multi-Currency
Worldline Hosted connects Foxy to Worldline Direct using Worldline's Hosted Checkout Page. Worldline Direct is the current generation of the platform previously sold as Ingenico Direct and, before that, Ogone — if your account documentation refers to a PSPID, you are on this platform. The gateway is used primarily across Europe, and it supports multiple currencies.
Countries listed for this gateway: Austria, Belgium, Bulgaria, Czechia, Denmark, Finland, France, Germany, Croatia, Hungary, Italy, Luxembourg, Netherlands, Norway, Poland, Romania, Slovakia, Slovenia, Spain, Sweden.
Because this is a hosted gateway, the customer is handed off to a payment page hosted by Worldline to enter their card details, and returned to your Foxy receipt when the payment completes.
Setting up Worldline Hosted
You will need a Worldline Direct account before you start. You will be moving between two browser tabs — the Foxy admin and the Worldline Merchant Portal — so it is easiest to open both first.
The panel is split into a Live setup block and a Test setup block carrying the same field list. Fill in the credentials above under Live setup. (The Live heading reads "Live setup (inactive)" while the payment method set has Use live credentials switched off — that reflects the current state of the set, not a different set of fields.)
Template Variant
Worldline lets you brand the hosted payment page with custom template variants. The Template Variant (optional) field in the Foxy panel selects which hosted-checkout-page template Worldline renders for the transaction — if you have a variant configured and want Foxy to use it, this is where you tell it.
In the Worldline administration, go to Developer > Branding, copy the Variant name, and paste it into the Template Variant (optional) field in your Worldline Hosted settings in the Foxy admin. Leave the field empty to use your Worldline account's default page.
There is a separate Template Variant field in the Test setup block, so you can point test transactions at a different variant while you are trying a design out.
Testing
Foxy provides shared test credentials for Worldline Hosted, so you can run test transactions without setting up your own sandbox account. Leave the Test setup fields as they are — including the pre-filled Test Webhook Secret.
Those shared credentials only exercise the integration itself. If you need to test against your own account configuration — your own branding variants, your own enabled payment products, your own webhook delivery — get a sandbox account from Worldline and fill in the Test setup fields with its credentials.
Obtaining a test account
You can create your own Worldline Hosted test account at https://signup.direct.preprod.worldline-solutions.com. Once created, follow the same setup steps above, but enter the values into the Test setup fields rather than the Live ones.
Test card numbers
Worldline does not publish test card numbers through Foxy. Contact Worldline, or check the test card list in the Worldline Direct developer documentation at https://docs.direct.worldline-solutions.com/en/index, for the cards that apply to your preprod account.
Advanced features
Authorize only. Worldline Hosted supports authorization-only transactions, so you can authorize at checkout and capture later.
Multiple currencies. The gateway supports multi-currency processing, subject to the currencies enabled on your Worldline account.
3D Secure. Strong customer authentication is handled by Worldline on the hosted payment page according to your Worldline account configuration. There is no separate 3D Secure configuration to set on the Foxy side for this gateway.
Important notes and caveats
The API secret and the webhook secret are each shown only once in the Worldline portal. Copy them into Foxy at the moment they are displayed. If you miss either one, generate a new one rather than hunting for the old value.
The webhook endpoint must point at your store's own domain. Getting this wrong is the most common reason transactions complete at Worldline but never finalize in Foxy.
Card details are entered on Worldline's page, not on your Foxy checkout, so the checkout flow includes a redirect away from your site and back.
Troubleshooting
If a transaction is declined or returns a response code you do not recognise, contact Worldline — they own the response code definitions for this platform and can see the transaction detail that Foxy cannot.
If payments succeed at Worldline but the order never appears in Foxy, re-check the webhook endpoint URL (step 13) and confirm the Webhook Secret in Foxy matches the one currently active in Developer > Webhooks.