CyberSource Gateway for Magento 2

Key Features

Global card processing through the CyberSource / Visa Acceptance REST API (SOAP/SCMP supported where your account mandates it), built as a native Magento\Payment gateway command module

Decision Manager fraud screening: device fingerprint injection, decision call on authorization, and admin-mapped ACCEPT / REVIEW / REJECT outcomes onto Magento order states

PCI-friendly card capture via CyberSource Flex Microform or Unified Checkout — PANs are tokenized client-side and never reach your Magento server

Network tokenization with stored payment instruments saved against the customer for one-click reorder and subscription rebilling

3D Secure 2 / Payer Authentication for SCA and PSD2 compliance, with frictionless and challenge flow handling in checkout

Recurring billing via a cron-driven rebill command that charges stored tokens on your subscription schedule

Separate authorize, capture, void, partial and full refund commands wired through di.xml virtual types and the gateway request/handler/validator pattern

Admin configuration under Stores > Configuration > Payment Methods with ACL-gated access, sandbox/production toggle, and encrypted credential storage

Multi-store and multi-website scope support so different store views can run distinct CyberSource merchant IDs and rule sets

Order-grid and order-view surfacing of Decision Manager scores, AVS/CVV results and transaction IDs for your support and fraud team

Optional GraphQL and REST coverage so headless / PWA Studio storefronts and external systems can drive the same payment flow

Webhook / notification handling to reconcile asynchronous capture, review-release and chargeback events back into Magento

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Magento 2.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

CyberSource — Visa's enterprise acceptance platform (now Visa Acceptance Solutions) — gives you global card processing married to Decision Manager, one of the most configurable fraud-screening engines in payments. Magento 2 ships with no native CyberSource integration, so most merchants either patch together a generic redirect or pay for a one-size-fits-all Marketplace extension that ignores their checkout, ERP and fraud-rule realities. ECOSIRE builds this module to your exact processing setup instead.

We deliver a proper Magento 2 payment module under app/code/Ecosire/CyberSource, wired through the official Magento\Payment gateway command framework — di.xml virtual types for authorize, capture, void and refund commands, request/handler/validator classes, and a Gateway client that talks to the CyberSource REST API (or SOAP/SCMP where your account requires it). Card data is captured with CyberSource Flex Microform / Unified Checkout so PANs never touch your server, then exchanged for a network token stored against the customer for one-click reorders and subscriptions.

Decision Manager is integrated as a first-class flow: device fingerprint injection, decision call on authorization, and an admin-configurable mapping of ACCEPT / REVIEW / REJECT outcomes onto Magento order states and emails. 3D Secure 2 runs through the Payer Authentication services for SCA / PSD2 compliance. Recurring billing hooks into your subscription logic via stored tokens and a cron-driven rebill command.

You buy a scoped build. ECOSIRE gathers your CyberSource merchant ID, environment and rule set, develops on Open Source or Adobe Commerce, installs it on your staging and production, and supports it afterwards. No fabricated Marketplace link, no instant download — a working, tested integration delivered on an agreed timeline.

What you get

Custom Magento 2 module under app/code/Ecosire/CyberSource (composer-installable), compatible with your Magento Open Source or Adobe Commerce version and PHP runtime

CyberSource REST (or SOAP/SCMP) gateway integration with authorize, capture, void and refund commands and full error/exception mapping

Decision Manager fraud flow with device fingerprinting and configurable order-state outcome mapping

3D Secure 2 Payer Authentication and tokenized recurring-billing implementation with the supporting cron job

Installation and configuration on your staging and production environments, including sandbox-to-live credential cutover

Documentation (admin configuration guide + handover notes) plus a defined post-launch support and warranty period

Who this is for

Enterprise checkout owner

Runs a high-volume Adobe Commerce store and needs CyberSource specifically because their acquirer and existing Decision Manager rules already live there — they want that exact stack reflected in Magento, not a generic gateway.

Risk / fraud manager

Owns chargeback and fraud KPIs and needs Decision Manager scores, REVIEW queues and ACCEPT/REJECT mapping to actually control how Magento creates, holds and emails orders.

Subscription / recurring-revenue merchant

Bills customers on a schedule and needs network-tokenized cards plus a reliable cron rebill so renewals run with stored credentials and SCA-compliant exemptions.

How CyberSource Gateway for Magento 2 Compares

Criterion	ECOSIRE	Custom Build	Competitor
Native CyberSource + Decision Manager integration in Magento 2	Included	Included	Partial support
Built to your exact checkout, ERP and fraud-rule setup	Included	Included	Not included
3D Secure 2 / Payer Authentication for SCA compliance	Included	Partial support	Partial support
Tokenized recurring billing with cron rebill	Included	Partial support	Partial support
Installed and configured on your environments by the vendor	Included	Not included	Not included
Defined post-launch support and upgrade maintenance	Included	Partial support	Partial support
You own the source under app/code (no lock-in)	Included	Included	Partial support
Predictable one-time cost, no per-build engineering overhead	Included	Not included	Included

Frequently Asked Questions about CyberSource Gateway for Magento 2

How long does delivery take, since this isn't an instant download?

This is a build-to-order extension, not a Marketplace one-click install. After purchase we hold a short scoping call to collect your CyberSource merchant ID, environment, processor and Decision Manager rules, then develop, test in sandbox and install on your staging and production. A standard CyberSource + Decision Manager + 3DS2 build typically lands in roughly 2 to 4 weeks depending on recurring-billing and headless requirements; we confirm the exact timeline in writing before work starts.

What ongoing support and updates do I get after launch?

The price includes a defined post-launch warranty period covering bug fixes and configuration help. After that we offer ongoing support and compatibility maintenance — keeping the module working across Magento / Adobe Commerce upgrades and CyberSource API changes — on a retainer or per-request basis. Because you own the source under app/code/Ecosire/CyberSource, you are never locked to us for future changes.

Does this work on both Magento Open Source and Adobe Commerce?

Yes. The module is built on the standard Magento\Payment gateway framework, which is identical across both editions, so it runs on Open Source and Adobe Commerce. On Adobe Commerce we can additionally align with B2B, shared catalog and the native order-management workflows where you use them. We build against your specific version and PHP runtime.

Is card data PCI-compliant and does it touch my server?

No raw PAN touches your Magento server. We capture cards with CyberSource Flex Microform or Unified Checkout, so the card data is tokenized in the browser directly with CyberSource and your storefront only ever handles a token. This keeps you in the lighter SAQ A / A-EP scope rather than handling full cardholder data, and tokens are stored encrypted for reuse.

Can it run in a headless / PWA Studio storefront?

Yes. Alongside the standard Luma/checkout integration we can expose the payment flow over GraphQL and REST so a PWA Studio, custom React/Next.js, or external headless storefront can initialize payment, run 3DS2 and submit the order. Headless coverage is scoped as part of the build since it affects the client-side tokenization and Payer Authentication handoff.