Commerce Worldline GoPay provides a comprehensive payment gateway integration between Drupal Commerce 3 and the Worldline Online Payments (GoPay) platform. It enables merchants to accept credit card payments and local payment methods on Drupal-based eCommerce sites through a secure, PCI-compliant architecture.

Integration Methods
The module offers three integration approaches:

  • Hosted Checkout Page — Customers are redirected to Worldline's PCI-compliant hosted payment environment, where all enabled payment methods are presented. Upon completion, customers are returned to the merchant site with payment status resolved via asynchronous polling.
  • Hosted Tokenization Page — Worldline's tokenization interface is embedded within the checkout flow, enabling customers to submit card payments and store payment credentials without sensitive card data being transmitted through or stored on the merchant's server.
  • Pay-by-Link — Store administrators may generate payment links from the order administration interface. These links, with configurable expiration periods of up to six months, can be distributed to customers for deferred payment completion.

Supported Payment Methods
The module accommodates over 25 payment methods, including major card networks (Visa, Mastercard, American Express, Diners Club, Discover, JCB, UnionPay), digital wallets (Apple Pay, Google Pay, WeChat Pay), and regional payment methods (iDEAL, Bancontact, SEPA Direct Debit, Przelewy24, Bizum, PayPal, Klarna, Bank Transfer). Available payment methods are configurable on a per-store basis through the administrative interface.

Payment Lifecycle Management
The module implements complete payment lifecycle operations:

  • Authorization & Capture — Supports both immediate capture and deferred authorization with subsequent full or partial capture.
  • Refunds — Provides full and partial refund capabilities, including support for orders with multiple associated payments.
  • Void/Cancel — Enables cancellation of authorized payments, including partial void operations.
  • Stored Payment Methods — Implements tokenization-based card storage with full remote token lifecycle management (creation, utilization, and deletion).

Security Architecture
The module adheres to established security practices throughout its implementation:

  • PCI DSS compliance support — All card data handling is delegated to Worldline's hosted pages; no sensitive payment information is stored or processed on the merchant's server.
  • Encryption at rest — All sensitive credentials, including API keys, API secrets, webhook signing keys, and payment tokens, are encrypted via the Drupal Encryption module prior to database storage.
  • Webhook signature verification — All inbound webhook notifications from Worldline undergo cryptographic signature validation before processing.
  • Post-payment order integrity — Orders completed through this gateway are protected against subsequent modification; order items, coupons, billing and shipping profiles, and price adjustments are locked after payment.

Multi-Store Architecture & Configuration
The module fully supports Drupal Commerce's multi-store architecture. Each store maintains independent API credentials, connection modes (test and production), payment method configurations, and operational settings. Configuration options encompass payment action selection (authorize versus authorize and capture), surcharge application, order status mapping, payment attempt limits, and session timeout parameters.

Differentiation
Commerce Worldline GoPay is the official Worldline-maintained integration for Drupal Commerce 3. It is distinguished from other payment integrations by the following:

  • A purpose-built administrative dashboard that mirrors the structure and capabilities of Worldline's Merchant Portal, encompassing connection management, payment configuration, and transaction monitoring.
  • Comprehensive coverage of the Worldline Online Payments API surface, including the Checkout, Order, Admin, and Webhook APIs.
  • A dedicated Pay-by-Link payment gateway plugin, providing administrator-initiated payment workflows as a first-class feature.

Project link

https://www.drupal.org/project/commerceworldlinegopay

Comments

goran.stamenkovski created an issue. See original summary.

vishal.kadam’s picture

vishal.kadam
Location Mumbai
commented
Issue summary: View changes
avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

Thank you for applying!

Before giving links helpful to understand how the review process works, what to expect from a review, and what to do to avoid a review takes more time than needed, I would like to thank all the reviewers for the work they do.
These applications are volunters-driven, which also means it is not possible to predict when an application will be marked fixed and the applicant will get the permission to opt projects into security advisory policy. While we aim to make an application as quick as possible, it is also important for us that more people review the project used for an application. In this way, we make sure applications do not miss some important points that should be instead reported.
Applications are not meant to be complete debugging sessions that eliminate every existing bug, though. I apologize if sometimes applications seem to go into too-detailed reviews.

Please read Review process for security advisory coverage: What to expect for more details and Security advisory coverage application checklist to understand what reviewers look for. Tips for ensuring a smooth review gives some hints for a smoother review.

The important notes are the following.

  • If you have not done it yet, you should enable GitLab CI for the project and fix the PHP_CodeSniffer errors/warnings it reports.
  • For the time this application is open, only your commits are allowed.
  • The purpose of this application is giving you a new drupal.org role that allows you to opt projects into security advisory coverage, either projects you already created, or projects you will create. The project status will not be changed by this application; once this application is closed, you will be able to change the project status from Not covered to Opt into security advisory coverage. This is possible only 14 days after the project is created.

    Keep in mind that once the project is opted into security advisory coverage, only Security Team members may change coverage.
  • Only the person who created the application will get the permission to opt projects into security advisory coverage. No other person will get the same permission from the same application; that applies also to co-maintainers/maintainers of the project used for the application.
  • We only accept an application per user. If you change your mind about the project to use for this application, or it is necessary to use a different project for the application, please update the issue summary with the link to the correct project and the issue title with the project name and the branch to review.

To the reviewers

Please read How to review security advisory coverage applications, Application workflow, What to cover in an application review, and Tools to use for reviews.

The important notes are the following.

  • It is preferable to wait for a project moderator before posting the first comment on newly created applications. Project moderators will do some preliminary checks that are necessary before any change on the project files is suggested.
  • Reviewers should show the output of a CLI tool only once per application.
  • It may be best to have the applicant fix things before further review.

For new reviewers, I would also suggest to first read In which way the issue queue for coverage applications is different from other project queues.

vishal.kadam’s picture

vishal.kadam
Location Mumbai
commented
Status: Needs review » Needs work

1. FILE: commerce_worldlineop.module

For a new module that aims to be compatible with Drupal 10 and Drupal 11, I would rather implement hooks as class methods as described in Support for object oriented hook implementations using autowired services.
It would require increasing the minimum Drupal 10 version supported, but Drupal 10.1 is no longer supported.

/**
 * @file
 * Module file.
 */

The usual description for a .module file is “Hook implementations for the [module name] module”, where [module name] is the module name given in the .info.yml file.

2. FILE: templates/commerce-worldlineop-config.html.twig

Twig code needs to be correctly indented. Drupal uses two spaces for indentation, not four spaces or tabs.

Move all JavaScript code into a library and attach them. See the process here.

3. New modules, which are compatible with Drupal 10 and higher versions are expected to include type declarations in property definitions, and use constructor property promotion.

vishal.kadam’s picture

vishal.kadam
Location Mumbai
commented
Priority: Normal » Minor

I am changing priority as per Issue priorities.