Keep Drupal Commerce. Upgrade your payment processing.
Keep your Drupal Commerce storefront as it is. Our integrations team helps your developer connect Finix through Cybersource.
What you get with Finix
Credit and debit cards
Accepted through the commerce_cybersource module, using Secure Acceptance Hosted Checkout or Flex Microform v2.
3D Secure (Strong Customer Authentication)
Supported via Cybersource’s Secure Acceptance Hosted Checkout and Flex Microform v2 integration methods, per the module’s own documentation.
Interchange-plus pricing
Interchange-plus pricing based on actual card network interchange, rather than a blended flat rate.
Dispute handling
Finix’s dispute and chargeback tools, available at the account level regardless of ecommerce platform.
Finix vs. Stripe and PayPal modules
Finix | Stripe & PayPal modules | |
|---|---|---|
Pricing model | Interchange-plus pricing through the Cybersource gateway integration. | Stripe: 2.9% + $0.30 domestic, plus 1.5% for international cards and 1% currency conversion. PayPal: roughly 2.99% + $0.30 to 3.49% + $0.49 domestic, plus 1.5% for international transactions. |
Payout timing | Set during onboarding with your Finix team. | Stripe: first payout in 7–10 business days, then a rolling 2- or 7-day schedule. PayPal: 1–3 business days free, or instant for a 1.75% fee (capped at $25). |
Account holds and disputes | Dedicated support throughout disputes and account reviews. | Payouts may be delayed during risk reviews, depending on each provider's risk policies. |
Payment methods | Cards via the commerce_cybersource module (Secure Acceptance Hosted Checkout or Flex Microform v2). Apple Pay, Google Pay, and ACH: confirm with your Finix integrations team. | Stripe: cards, Apple Pay, and bank transfers. PayPal: PayPal Checkout and Payflow Pro. |
Merchant account | Individual merchant account (Direct Merchant). | Merchant account structure depends on the payment provider and module you choose. |
Support model | Dedicated integrations support from the Finix team. | Community-maintained modules supported through drupal.org issue queues. Production support typically requires a separate contract with a Drupal agency or Centarro. |
Quick recap of Finix vs. Stripe and PayPal modules
Drupal Commerce doesn't include a single default payment processor, so merchants typically choose between community-maintained Stripe and PayPal modules, each with its own pricing and support model. Finix consolidates payment processing into one interchange-plus relationship through Cybersource.
How it works
Switch your payment processor without switching your ecommerce platform. Finix is built so you can move from application to processing without a drawn-out integration.
Talk to our integrations team.
Your developer installs the module.
Go live with support from Finix.
What this integration requires
Finix connects to Drupal Commerce through the commerce_cybersource module, installed via Composer, not a native Finix-branded plugin, so setup involves your developer working in Composer and the Drupal admin.
Payment gateway
Routed through the commerce_cybersource module, added as a payment gateway under Commerce → Configuration → Payment gateways.
Code changes
Payment gateway configuration in the Drupal admin. No custom code beyond standard module setup and cache clearing.
Command-line or Composer install
Yes. Installed via composer require 'drupal/commerce_cybersource:^1.8', then enabled under Extend.
Developer needed
Yes. The Composer install and cache-clear steps are standard Drupal developer tasks, not merchant-facing, no-code steps.
Why merchants switch to Finix
Pain point | Finix solution |
|---|---|
Drupal Commerce doesn't include a default payment processor, so merchants typically choose between community-maintained Stripe and PayPal modules, each with its own setup, pricing, and support model. | Finix brings payment processing together under one interchange-plus relationship through the Cybersource-based commerce_cybersource module. |
Both commerce_stripe and commerce_paypal are community-maintained, open-source contrib modules, supported through drupal.org issue queues rather than a vendor support line. Paid production support requires an added contract with Centarro or a Drupal agency. | Support on Finix’s Drupal Commerce integration comes from a dedicated integrations team that helps plan the setup with your developer, not a community issue queue. |
Payment reviews and disputes can interrupt cash flow if merchants don't know what's happening. | Dedicated support helps merchants understand and manage disputes and account reviews. |
Everything you need to accept and manage payments
Online, in person, recurring, or on demand. Finix gives you every tool in one place.
Frequently asked questions
Yes. Finix connects to Drupal Commerce through the commerce_cybersource module, so your site’s content, catalog, and checkout flow stay the same. You’re changing how payments are processed, not your platform.
Setting up Finix means configuring Cybersource as your active payment gateway and disabling your existing Stripe or PayPal gateway. You can't run them side by side. Your site, catalog, and customer data stay unchanged.
Yes. Installing the commerce_cybersource module requires running a Composer command, enabling the module, and configuring the payment gateway in the Drupal admin: standard developer tasks. Finix’s integrations team can guide your developer through the setup.
Nothing changes. Order history, catalog, and customer data live in Drupal Commerce regardless of which payment gateway is active. Switching to Finix only changes how new transactions are processed.
Drupal 10.3 or later, with Composer installed. Confirm your site meets both requirements before starting setup.
Setup time depends on your developer’s availability and how quickly your Finix and Cybersource accounts are approved. Finix does not publish a fixed timeline for this integration; talk to our integrations team for a project estimate.