Category: Uncategorized

CyberSource Unified Checkout WooCommerce is the fastest way to add Google Pay, Apple Pay, Paze, and Click to Pay to your store — one SDK, one set of REST credentials, no separate gateway account per wallet. Your checkout has about three seconds to match a shopper’s preferred payment method before they leave, and this integration lets you offer all major wallets at once through the RyanPlugins CyberSource Payment Gateway.

This guide covers how UCO works, which wallets it supports, and the exact steps to enable it in WooCommerce.

---

What Is CyberSource Unified Checkout?

Unified Checkout is Visa/CyberSource’s hosted payment SDK. It renders a single, PCI-compliant payment UI directly on your WooCommerce checkout page — one interface that handles credit card entry, Google Pay, Apple Pay, Paze, and Click to Pay, all controlled by a single set of CyberSource credentials.

You load one SDK and configure which payment types to expose. CyberSource manages the relationship with each wallet network on the back end. Your store never sees raw card data — only a short-lived transient token that the plugin forwards server-side to complete the charge.

With CyberSource Unified Checkout WooCommerce, all five payment types share the same session request, the same SDK load, and the same authorization path — enabling three wallets takes the same effort as enabling one.

How the payment flow works

1. Session request — on checkout page load, the plugin calls CyberSource’s REST API via AJAX to create a UCO session and retrieves a session JWT.
2. SDK mount — the UCO SDK loads and renders the wallet buttons and/or card entry iframe within the WooCommerce payment form.
3. Customer approval — the shopper taps Google Pay or Apple Pay and authenticates on their device. For Click to Pay or Paze, they complete the wallet flow in an iframe.
4. Transient token returned — the SDK passes a single-use JWT back to your store. No raw card number, no PAN.
5. Server-side authorization — the plugin posts that token to CyberSource to authorize the charge and updates the WooCommerce order status.

Because sensitive credentials never leave the CyberSource / wallet ecosystem, this flow keeps your PCI scope as narrow as possible.

---

Supported Payment Methods

Enable any combination of the five UCO payment types from a single plugin settings section. Each is toggled independently — roll out one method at a time or switch them all on at once.

Payment method	What it covers	Plugin setting
Google Pay	One-tap checkout on Android and Chrome desktop using cards saved to the customer’s Google account	GOOGLEPAY
Apple Pay	Touch ID / Face ID checkout on Safari — iPhone, iPad, and Mac	APPLEPAY
Paze	Bank-backed US digital wallet from major card issuers — tokenised checkout, no separate app required	PAZE
Click to Pay	EMV Secure Remote Commerce — returning customers pay in one click using network-stored tokenised credentials	CLICKTOPAY
PAN Entry	Standard card number entry rendered inside the same UCO hosted iframe — consistent UI across all methods	PANENTRY

---

Works With Classic Checkout and WooCommerce Blocks

Both WooCommerce checkout experiences are fully supported — no need to stay on the legacy shortcode checkout or roll back from Blocks.

Classic checkout (shortcode)

The plugin enqueues wc-cybersource-uco.js, which fetches the session JWT via AJAX, loads the UCO SDK, mounts the payment UI, and handles errors — all inline on the checkout page. No template overrides required.

WooCommerce Blocks checkout

A dedicated UCOContent React component integrates directly with the Blocks payment API. It captures the wallet token and submits the order automatically — no page reload, no redirect to a hosted payment page.

---

What You Need Before Enabling UCO

Important: UCO uses CyberSource’s REST API — not the older Secure Acceptance or SOAP path. Your existing Hosted Checkout or SOP credentials are not used here. You’ll need a separate REST API Key ID and Shared Secret.

CyberSource Business Center

• REST API Key ID + Shared Secret — generated under Payment Configuration → API Keys. If you’ve already set up REST credentials for another plugin feature, you can reuse them.
• Unified Checkout enabled for your Merchant ID — navigate to Payment Configuration → Unified Checkout and activate each wallet. Step-by-step: Enabling Unified Checkout in the CyberSource Business Center.
• Apple Pay domain verification — the Business Center generates a verification file you upload to your store’s root. Walkthrough: Apple Pay Enrollment and Testing Guide.
• Google Pay merchant registration — enroll your site via the Business Center. Walkthrough: Enrolling in Google Pay on CyberSource Unified Checkout.
• Click to Pay + 3D Secure (optional) — see Enabling Click to Pay & Setting Up 3D Secure.

WooCommerce requirements

• PHP 7.4 – 8.3
• RyanPlugins CyberSource plugin v2.2.0 or later
• WooCommerce 6.x or later (WC 7–9 fully tested)

---

How to Enable CyberSource Unified Checkout WooCommerce

Once the Business Center is configured, the plugin side takes under five minutes. Full reference: CyberSource Unified Checkout Plugin Settings Documentation.

1. Go to WooCommerce → Settings → Payments → CyberSource.
2. Scroll to Unified Checkout — Digital Wallets and tick Enable Unified Checkout.
3. Under Allowed Payment Types, select your wallets: GOOGLEPAY, APPLEPAY, PAZE, CLICKTOPAY, and/or PANENTRY.
4. If using Click to Pay, set Auto-Enroll on or off — when on, eligible customers are enrolled automatically after their first purchase.
5. Save. The plugin requests a UCO session on every checkout page load and mounts the wallet UI automatically.

The SDK URL, Content Security Policy headers for all wallet domains, and the AJAX session endpoint (cybsawm_get_uco_session) are all managed by the plugin internally. Nothing to add to wp-config.php or .htaccess.

After setup, run through a test transaction using the CyberSource Unified Checkout Test Payment Guide.

---

UCO vs. Standalone Click to Pay — What’s the Difference?

The plugin has offered a standalone Click to Pay mode since an earlier release. Here’s how the two compare:

	Standalone Click to Pay	Unified Checkout (UCO)
SDK	Earlier CyberSource Click to Pay SDK	CyberSource UCO SDK (current)
Wallets	Click to Pay only	Google Pay, Apple Pay, Paze, Click to Pay, PAN Entry
Credentials	Secure Acceptance / SOAP	REST API (Key ID + Shared Secret)
Recommended for	Existing deployments	All new wallet deployments

If you’re starting fresh, UCO is the right path. If your existing Click to Pay setup is working, there’s no rush to migrate — but UCO gives you broader coverage with the same credentials.

---

Security and PCI Scope

The UCO SDK is hosted and served entirely by CyberSource. Raw card numbers and wallet credentials never pass through your WooCommerce server.

The only value your server handles is the transient JWT returned after the customer approves payment — a single-use, short-lived token that the plugin immediately forwards to CyberSource’s authorization API. Card numbers, tokens, API keys, and personal data are also redacted automatically in all debug logs before anything is written to the WooCommerce log file.

---

Try the Live Demo

Test the full UCO checkout — all wallet types, against CyberSource’s sandbox — on the RyanPlugins demo store:

For test card numbers and step-by-step wallet testing, see the Test Payment Guide.

---

---

Further Reading

All setup guides are in the Unified Checkout docs section:

• How to Install the CyberSource Unified Checkout Plugin
• Plugin Settings Documentation
• Enabling Unified Checkout in the CyberSource Business Center
• Apple Pay Enrollment and Testing Guide
• Enrolling in Google Pay on CyberSource Unified Checkout
• Enabling Click to Pay & Setting Up 3D Secure
• Test Payment Guide