[Skip to main content](#vessel-content)

[View on the marketplace →](/marketplace/display/product/289-worldline-direct-cawl) ☰ Documentation

#  Worldline Direct payment plugin

Details    Written by: Administrator    Category: [Payment plugins](/support/documentation/hikashop/payment-plugins)     Published: 10 November 2026     Hits: 6

## Installation

- 1) Have an account with your provider (Worldline Direct, PAYONE Global Online Pay, CAWL or ANZ Worldline). PAYONE opens a free test account at signup.preprod.payone.com; with Worldline, CAWL or ANZ, ask your provider for one. The live account comes with your contract and has its own keys.
- 2) Log in to your merchant portal (for PAYONE, portal.preprod.payone.com for the test account and portal.payone.com for the live one) and note your PSPID, shown at the top of the portal.
- 3) Open Developer, Payment API, and generate an API key: copy the API Key ID and the Secret API Key. The secret is shown only once.
- 4) Install this plugin on your website: the Joomla extension manager, or HikaShop's plugin installer on WordPress. The plugin needs PHP 8.3 or higher.
- 5) In HikaShop, go to System &gt; Payment methods, click "New" and choose Worldline Direct. Fill in the PSPID and the two keys, choose the environment (Pre-Production for a test account, Production for a live one) and the endpoint of your provider (PAYONE for a PAYONE account), set "Published" to Yes and save.
- 6) In your portal, turn on the payment methods you want to offer. No webhook has to be set up: the plugin gives its notification address with each payment.
- 7) If your website uses Akeeba Admin Tools' .htaccess Maker, or any other server hardening that restricts which PHP files can be reached at the root of the website (often called entry point filtering or allowed front-end files), allow worldlinedirect\_\*.php in the list of allowed files and regenerate your .htaccess. When the payment method is saved, the plugin writes a small return file named worldlinedirect\_ followed by the payment method number, at the root of your website, so that the return address stays short enough for the payment page. If your hardening blocks it, customers see a "403 Forbidden" page when they come back although they paid, and the order waits for the notification. When the root of the website is not writable, the plugin uses a longer return address through index.php instead, which is not affected.

## Configuration

![The Worldline Direct settings in the HikaShop payment method](/images/doc/plugins/worldlinedirect/plg_hikashoppayment_worldlinedirect_settings.png)

- **PSPID**: the PSPID of your merchant account (step 2). A test account and a live account have different PSPIDs. Left empty, the payment cannot start.
- **API Key ID** and **Secret API Key**: the keys of step 3, from the same account and environment as the PSPID. Left empty, the payment cannot start.
- **Environment**: Pre-Production (test) takes no real payment and uses the keys of your test account; Production takes real payments with the keys of your live account.
- **Endpoint**: your provider: Worldline Direct, CAWL (Credit Agricole), PAYONE (Global Online Pay), ANZ Worldline Solutions (Australia), GlobalCollect or WL Online Payment Acceptance. Choose the one your contract is with; the payment page then carries its name and look.
- **Variant name**: the template of the payment page made in your portal (Branding), to show your colours and logo. Empty, the default page is shown.
- **3D Secure Challenge Indicator (for credit card payments)**: whether you want the bank of the customer to ask them to authenticate on card payments: no preference (default), prefer not to challenge, prefer to challenge, or require the challenge. Keep the default unless your provider tells you otherwise.
- **Debug**: No by default. Yes writes the requests and answers of your provider to the payment log file of the HikaShop configuration page, to look into a problem.
- **Return url**: not used, the plugin makes the return address itself. Leave it empty.
- **Invalid status**: not used by this version: a payment cancelled on the payment page cancels the order.
- **Verified status**: the status of an order once its payment is accepted, usually "confirmed". Choose the status that sends your customer the confirmation email.
- The other settings of the page (name, description, images, price, zone, currency, restrictions) are the same as for every HikaShop payment method.

## Troubleshooting

- Turn Debug on and open the payment log (System &gt; Configuration, Files, "See the report" next to "Payment log file"): the answers of your provider are written there.
- **"You have to configure a PSPID"**, **"the API Key"** or **"the Secret API Key"**: one of these settings is empty.
- **MISSING\_OR\_INVALID\_AUTHORIZATION** in the payment log: the keys do not belong to the PSPID, or the keys of a test account are used in Production (or the reverse).
- **"The endpoint Ogone (EU)" (or "TechProcess (India)") "of this payment method no longer exists"**: those servers were shut down and payments now go to Worldline Direct. Choose the endpoint of your contract and save the payment method.
- **"Worldline Direct payment error"** or "Error during the Worldline Direct payment request" (log): the payment page could not be opened; the end of the message is your provider's reason.
- The customer sees "403 Forbidden" on coming back from the payment page: see step 7 of the installation.
- **INVALID\_VALUE** on returnUrl in the payment log: the return address is too long. Check that the return file of step 7 can be written at the root of your website, and save the payment method again.
- "Unable to retrieve the order ID from the hostedCheckoutId" (shown and logged): the shop received a return or a notification without an order reference. Check the order and the payment in your portal.
