Worldline is one of Europe largest payment processors, and the group behind Bambora and Ingenico following a series of acquisitions. For merchants selling into Europe, that scale matters mainly for one reason: coverage of the local payment methods that shoppers in each market actually expect to see.
This guide covers connecting WorldLine to Contact Form 7 on WordPress.
Why local payment methods matter
Card penetration varies widely across Europe. A Dutch shopper looks for iDEAL, a German one may expect direct debit or an invoice option, and a Belgian buyer looks for Bancontact. Offering only Visa and Mastercard in those markets does not simply reduce convenience, it removes the option a large share of buyers would have used.
Before configuring anything, list the countries you actually sell to and the methods buyers there expect. That list determines what you enable at a Contact Form 7 payment form, and it is worth deciding deliberately rather than switching on everything available.
What you need
- A WorldLine merchant account with gateway credentials issued.
- WordPress running Contact Form 7, kept current.
- HTTPS across the whole site, not only the payment page.
- The WorldLine gateway plugin for Contact Form 7.
Installing and connecting
Upload the plugin ZIP under Plugins → Add New → Upload Plugin and activate it. A WorldLine section appears in your Contact Form 7 payment settings. Paste in the credentials from your merchant account, keeping test and live values clearly separated.
Strong Customer Authentication
Under PSD2, most consumer card payments in the European Economic Area require Strong Customer Authentication. In practice that means the shopper confirms the payment through their bank, usually in an app, before it is approved.
Two things follow. First, your checkout must handle the authentication step returning control to your site cleanly, which is exactly what testing should confirm. Second, expect a small proportion of payments to fail authentication for reasons entirely outside your control, such as a customer not having their banking app to hand. A clear retry message recovers a good share of those.
Exemptions exist for low-value and low-risk transactions, but they are applied by the acquirer and issuer rather than configured by you. Treat authentication as the normal path, not the exception.
Currencies and settlement
Decide whether to price in a single currency or in each local currency. Local pricing generally converts better, because shoppers see a familiar figure rather than doing mental arithmetic. It also means dealing with conversion and settlement in more than one currency, so confirm which currencies your account settles in before you advertise prices in them.
Testing
Run a Contact Form 7 payment form in test mode and confirm each of these:
- A successful card payment, including the authentication step, returns to your site and records correctly.
- A payment abandoned during authentication does not leave an order marked as paid.
- Each local payment method you enabled completes end to end.
- Amounts and currency match exactly at every stage.
- Receipts reach both the customer and you.
The abandoned-authentication case is the one most often missed, and it is the one that produces phantom orders and confused customers.
Going live
Replace the test credentials, disable test mode, and process one small real payment yourself before refunding it. Repeat that for at least one non-card local method if you enabled any, because those follow a different flow from a card payment and can fail independently.
Troubleshooting
The method is missing at checkout. Local payment methods are usually restricted by country and currency. If the order does not match those rules, the option is hidden by design.
Customers stall at the bank authentication screen. Check the return URL configuration. If the bank cannot hand control back to your site, the payment may succeed while the order never completes.
Payments taken but orders unpaid. The gateway callback is not reaching WordPress. Check host firewalls and security plugins that filter incoming requests.
Getting the plugin
The WorldLine Payment Gateway for Contact Form 7 is available from wpayo with updates and support. Background on the provider is in our overview of what Worldline payment is and how it relates to the former Bambora service.
Disputes and chargebacks in Europe
Strong Customer Authentication changes who carries the loss on a disputed payment. Where a transaction was authenticated by the cardholder bank, liability for fraudulent-use claims generally shifts away from the merchant. That is a meaningful protection, and a reason not to seek exemptions from authentication too eagerly.
It does not cover every dispute. A claim that goods never arrived, or did not match the description, remains yours to answer regardless of authentication. Keep delivery evidence, the order record and the authorization response together, because a dispute window is short and evidence assembled after the fact is rarely convincing.
Practical points for selling across borders
- Show prices inclusive of VAT where you sell to consumers in the EU. A total that changes at the final step is a well-documented cause of abandonment.
- Use a billing descriptor customers will recognize on a statement. Unrecognized descriptors generate disputes from buyers who simply do not remember the purchase.
- State delivery times and refund terms in plain language. Cross-border buyers are more cautious, and vagueness reads as risk.
- Offer at least one familiar local method per major market. It is usually the single highest-return change you can make to a checkout.
Frequently asked questions
Do I need SCA if I sell outside Europe?
The requirement applies to transactions where both the cardholder bank and the acquirer are in the European Economic Area. Selling to customers elsewhere generally falls outside it, though card networks apply their own authentication rules regardless.
Will authentication reduce my conversion rate?
It adds a step, so some drop-off is expected. The offsetting gains are lower fraud and the liability shift on authenticated payments. The larger practical factor is how clearly your checkout handles a failed authentication and invites a retry.
Can I take recurring payments under SCA?
Yes. The first payment is normally authenticated, and subsequent merchant-initiated charges run against the mandate established then. Whether Contact Form 7 supports this depends on the subscription extension you use, so confirm before advertising a subscription.
What if a local payment method fails but the card works?
Each method is a separate integration with its own rules and failure modes. Test them individually rather than assuming a working card path means the rest are fine.
Leave a Reply