WooCommerce CyberSource Payment Gateway

Secure, Fast and Reliable CyberSource Checkout

Accept payments in WooCommerce using CyberSource Hosted Checkout and Checkout API integrations with enterprise-grade security, tokenization, and subscription support.

Hosted Checkout Demo: https://cybersource.ryanplugins.net/hosted-checkout/

Checkout API Demo: https://cybersource.ryanplugins.net/checkout-api/

Click to Pay Demo: https://cybersource.ryanplugins.net/cybersource-click-to-pay/

Key Features

Secure Payment Processing

• Secure, fast, and reliable CyberSource checkout process
• PCI-compliant payment processing
• CyberSource Secure Acceptance Silent Order POST (SOP)
• CyberSource Secure Acceptance Web/Mobile API
• CyberSource Checkout API integration
• CyberSource Hosted Checkout integration
• CyberSource Simple Order API (SOAP)
• Click to Pay via Unified Checkout SDK
• Unified Checkout — Digital Wallets

Digital Wallet Support via Unified Checkout (UCO)

Seamlessly accept modern payment methods including:

• Google Pay
• Apple Pay
• Paze
• Click to Pay (EMV Secure Remote Commerce)

Security & Fraud Protection

• CyberSource Payer Authentication supported
• CyberSource 3D Secure integration
• CyberSource Device Fingerprint ID Profiler
• CyberSource Merchant Notifications
• Secure API logging with automatic card number masking
• Supported integrations: Hosted Checkout & Checkout API
• P12 Certificate authentication support for both SOAP (Simple Order API) and REST API.

Subscriptions & Tokenization

• WooCommerce Subscriptions support (new in v2.0)
• Automatic subscription renewals via CyberSource Recurring Billing (SOAP)
• Save card tokenization support (Checkout API / SOP integration)
• Customers can add a payment method from My Account → Payment Methods page
• Saved card UI for both Classic and Blocks checkout

Webhooks & Real-Time Updates

• CyberSource Webhooks for real-time payment notifications
• HTTP POST requests sent when payments are authorized, captured, refunded, or disputed
• Ensures WooCommerce order statuses stay in sync automatically
• Eliminates the need to poll the CyberSource API

Advanced Payment Features

• CyberSource Refunds supported directly from WooCommerce orders
• CyberSource Purchase Level 3 (Visa/MasterCard) support
• Custom Merchant Defined Data (MDD) fields supported via WordPress filters
• Full support for automatic tokenized payments and subscriptions

WooCommerce Compatibility

• WooCommerce Checkout Blocks supported
• Compatible with High-Performance Order Storage (HPOS)
• Compatible with WooCommerce Subscriptions plugin

Easy Configuration

• Simple and manageable plugin settings
• One-click “Set Defaults” buttons to auto-populate Signed Field Names
• Built-in debug logging for easy troubleshooting

Summary

This plugin is perfect for merchants who want enterprise-grade CyberSource payment processing in WooCommerce, with subscriptions, tokenization, webhooks, advanced security, and full WooCommerce compatibility.

Video Help

1.Demo Checkout for WooCommerce CyberSource Payment Gateway. watch here
2.WooCommerce CyberSource Payment Gateway Setup Tutorial. watch here
3.How to Install Cybersource Payment Gateway Plugin Tutorial. watch here

Online Documentation

1. How to Setup WooCommerce CyberSource Payment Gateway
2. How to Create Cybersource Secure Acceptance Profile
3. How to get your Cybersource Secure Acceptance Profile Id
4. How to get your Cybersource Profile Access Key and Secret Key

Reviews

Frequently Asked Questions (FAQ)

1. Which CyberSource integration methods are supported?

This plugin supports two CyberSource integrations:

• CyberSource Hosted Checkout (Secure Acceptance Hosted Checkout)
• CyberSource Checkout API (Secure Order Page / Silent Order POST)

You can select your preferred integration method from the plugin settings.

2. Does the plugin support WooCommerce Subscriptions?

Yes. The plugin includes built-in support for WooCommerce Subscriptions, allowing you to accept recurring payments using CyberSource.

• Subscription checkout
• Saved payment methods
• Automatic subscription renewals via CyberSource Recurring Billing (SOAP)

Note: The WooCommerce Subscriptions plugin must be installed and activated.

3. Can customers save their cards for future payments?

Yes. Customers can securely save their cards using CyberSource tokenization. Saved payment methods can be used for:

• Faster checkout
• Future purchases
• Automatic subscription renewals

Customers can also add a new payment method from the My Account → Payment Methods page.

4. Does the plugin support CyberSource Webhooks?

Yes. The plugin supports CyberSource Webhooks for real-time payment event notifications.

• HTTP POST requests sent when payments are authorized, captured, refunded, or disputed
• Ensures WooCommerce order statuses stay in sync automatically
• Eliminates the need to poll the CyberSource API

5. Is the plugin PCI compliant?

Yes. The plugin uses CyberSource Hosted Checkout or Secure Acceptance APIs, meaning sensitive card information is processed securely by CyberSource, helping merchants maintain PCI compliance.

6. Does the plugin support WooCommerce Blocks checkout?

Yes. The plugin supports WooCommerce Blocks Checkout for CyberSource Hosted Checkout.

7. Can I issue refunds from WooCommerce?

Yes. You can process refunds directly from the WooCommerce order page, and the plugin will automatically send the refund request to CyberSource.

8. Does the plugin support 3D Secure or Payer Authentication?

Yes. The plugin supports:

• CyberSource Payer Authentication
• CyberSource 3D Secure

Supported integrations: Hosted Checkout & Checkout API

9. Does the plugin support High-Performance Order Storage (HPOS)?

Yes. The plugin is fully compatible with WooCommerce High-Performance Order Storage (HPOS).

10. What server requirements are needed?

Your server must support:

• PHP 7.4 – PHP 8.3
• PHP SOAP (SoapClient) extension enabled
• WordPress and WooCommerce installed

11. Do I need to enable anything in the CyberSource Business Center?

Yes. To use subscriptions and saved payment methods, you must enable:

• Recurring Billing in your CyberSource merchant account
• Transaction Key configured in the plugin settings

12. Can developers customize the integration?

Yes. Developers can customize the plugin using:

• WordPress filters
• CyberSource Merchant Defined Data (MDD) fields

This allows advanced customization of transaction metadata.

Changelog

 = 2.6.16 - 2026-09-29 =  Improved - Unified Checkout and Click to Pay session requests now include detailed debug logging for the amount, billing address, billing type, 3-D Secure and Decision Manager settings, and CyberSource capture context. Personal details are masked. Improved - CyberSource session rejection reasons are now recorded in the debug log instead of only the HTTP status. Improved - All Unified Checkout 3-D Secure payment results are now logged, including status, commerce indicator, ECI, amount and reference. Fix - P12 (JWT) authentication no longer writes entries to the server PHP error log on every request. Authentication details are now written only to the WooCommerce log when Debug Log is enabled.  = 2.6.15 - 2026-09-29 =  Fix - WooCommerce Blocks checkout no longer displays a critical website error when a payment is refused. Customers now see the actual payment refusal message. Fix - Unified Checkout payment results such as AUTHENTICATION_SUCCESSFUL are no longer incorrectly recorded as declined payments when CyberSource has not reported an approved payment. Improved - Non-standard Unified Checkout payment results are now recorded in the debug log in full with sensitive information masked. Security - 3-D Secure cryptograms, Payer Authentication tokens and transient JWTs are now fully redacted from debug logs.  = 2.6.14 - 2026-09-22 =  Fix - Resolved a PHP 8.5 fatal error caused by the SOAP client method signature. Improved - The SOAP toolkit is now loaded only when a SOAP operation is required. Fix - Missing PHP SOAP support now reports a clear error instead of causing an unrelated failure.  = 2.6.13 - 2026-09-22 =  Security - Unified Checkout payments are now refused when 3-D Secure is enabled but the payment reaches the server without successful authentication. Fix - Prevented unauthenticated fallback payments from being processed as regular unauthenticated transactions when 3-D Secure is required. Improved - The payment type and cardholder authentication status are now logged before each authorization. Improved - 3-D Secure fallback refusals are recorded in the order and debug log with the applicable wallet payment type.  = 2.6.12 - 2026-09-22 =  Improved - Unsupported CyberSource webhook events now record their full payload in the debug log for troubleshooting. Security - Debug log masking now recognizes camelCase billing fields used by the REST and Unified Checkout APIs.  = 2.6.11 - 2026-09-22 =  Fix - Unified Checkout webhook events can now correctly locate WooCommerce orders using the checkout session reference and transaction ID, in addition to the order number. Fix - Refund, dispute and fraud review webhook notifications now correctly reach Unified Checkout orders. Fix - Added support for the CyberSource webhook Endpoint Health Check. Improved - Updated webhook setup instructions and added warnings for insecure webhook authentication settings.  = 2.6.10 - 2026-09-21 =  New - Added Unified Checkout settings to control which customer information is requested during wallet checkout. New - Billing address fields can now be configured as full address, postal code and country only, or no billing fields. New - Added options to disable email address, phone number and confirmation requests. Changed - Unified Checkout no longer requests a shipping address by default because WooCommerce already collects the shipping address. Improved - Reduced duplicate customer information requests during checkout.  = 2.6.9 - 2026-09-16 = * Fix - Unified Checkout could not take a payment on the Pay for order page. The capture context was priced from the cart, which that page does not have, so CyberSource was asked to authorise 0.00 and rejected the payment with INVALID_REQUEST. * Fix - A customer paying for an order while items remained in their cart was quoted the cart total rather than the order total. The amount, currency and billing address now come from the order being paid, which is trusted only once its order key matches. * Fix - Click to Pay reported "missing configuration" on the Pay for order page. Two enqueue paths registered the same script handle, and the one that ran there attached its settings under a name the script does not read. * Fix - A capture context worth 0.00 is refused with a readable message and a log entry instead of failing inside CyberSource at the end of the flow. * Dev - Ten tests covering the order key binding on the Pay for order page. Suite is now 114 tests.  = 2.6.8 - 2026-09-16 = * Tweak - The block checkout hides its Place Order button while Unified Checkout or Click to Pay is the selected payment method, matching the classic checkout. Both take the payment in their own window and the plugin submits the order once CyberSource answers. * Fix - If the order cannot be submitted for the customer after a wallet payment, the Place Order button is handed back and the message asks them to click it, so a missed auto-submit can no longer strand a customer who has already paid. * Fix - The Place Order button also returns whenever the wallet fails to load, since nothing will submit the order in that case.  = 2.6.7 - 2026-09-14 = * Add - Unified Checkout settings now have their own settings tab, between Payment and Advanced, leaving the General tab for core settings. Field names are unchanged, so existing configurations carry over and nothing needs re-saving. * Tweak - The classic checkout hides its Place order button while Unified Checkout or Click to Pay is the selected payment method. * Fix - A Unified Checkout payment is no longer refused when the JWT signing key cannot be fetched. Keys are cached for a week per key ID, and a fetch failure confirms the transaction with CyberSource instead of failing the order. * Fix - The transaction-lookup fallback reads the payment status from applicationInformation, which it previously ignored, so every lookup-confirmed payment was reported as a decline. * Fix - The replay guard claims the payment reference and transaction ID before checking them, closing a race between two simultaneous submissions. * Fix - Standalone Click to Pay is read from POST only and runs only when Click to Pay is enabled, the same treatment the Unified Checkout path already had. * Fix - A payment that cannot be matched to its checkout session is recorded on the order as _cybsawm_unmatched_transaction_id so the transaction can be traced. * Fix - The admin Capture action and the REST capture endpoint read the merchant ID from a protected property, which is a fatal error in PHP. Both now use an accessor. * Fix - A SOAP capture stored an empty request ID on the order because the line reading it from the response had been commented out. * Fix - The "days since last purchase" merchant-defined data field subtracted two date strings, which is a TypeError in PHP 8 rather than a day count. * Fix - The Checkout API sent an empty ship-from postal code in its level 2/3 data. * Fix - Add payment method returned nothing instead of a failure result when the card was declined. * Fix - Assorted undefined variables, incorrect argument counts and an unreachable parent method call in the Simple Order, Checkout API and Merchant Defined Data paths. * Dev - PHPStan added to the development tooling. composer check runs the test suite and the static analysis together, and both are clean.  = 2.6.4 — September 14, 2026 =  == Fixed ==  * 3-D Secure Regression Fix: Fixed an issue where the `exp` claim was incorrectly required during 3DS result verification. Live 3DS results do not include this claim, which caused valid 3DS payments to fail.  = 2.6.3 =  == Security ==  * 3DS result binding: Added validation of the transaction reference, merchant, amount, and single-use requirements to prevent replay attacks and cross-merchant acceptance.  = 2.6.2 =  == Fixed ==  * Transaction status validation: Captures, voids, reversals, and refunds now verify the actual transaction status instead of relying only on the HTTP response code.  = 2.6.1 =  == Fixed ==  * ECI value: Fixed an issue where the commerce indicator (`spa`/`vbv`) was incorrectly stored as the ECI value.  = 2.6.0 =  == Added ==  * 3-D Secure for Unified Checkout:Added complete 3DS support for Unified Checkout using the required authentication flow. * 3DS settings: Added two new 3DS settings, disabled by default. * Server-side verification: Added server-side verification of 3DS authentication results.  == Fixed ==  * Decision Manager rejection: Fixed an issue where HTTP `201` responses were incorrectly treated as successful payments. Decision Manager rejections are no longer marked as paid or captured. * Risk-declined authorisations: Risk-declined authorisations are now automatically reversed.  = 2.5.1 — September 1, 2026 =  == Security ==  * Improved webhook security: Webhook requests are now rejected with a `401 Unauthorized` response when the Webhook Security Key is not configured. * Restricted webhook order lookup: Webhooks now require a valid numeric client reference and an order that was originally paid using this payment gateway. *Improved transaction response security: HMAC verification is now performed before any order metadata is written. Failed verification no longer changes the order status to `failed`. * Improved Secure Acceptance secret validation: An empty Secure Acceptance Secret Key is now treated as a verification failure. * Prevented order status downgrade: Signed but replayed or delayed `DECLINE`, `ERROR`, or `CANCEL` notifications can no longer change an already-paid order to an unsuccessful status. * Improved saved card security: Saved cards are now resolved only through WooCommerce payment-token ownership checks, ensuring that logged-in customers can only use their own saved payment methods. * Protected payment tokens: Raw CyberSource tokens are no longer exposed to the browser or accepted directly from checkout requests. Checkout now uses the WooCommerce payment token ID.  == Fixed ==  * Unified Checkout: Fixed an issue where Unified Checkout sessions did not correctly respect the configured REST API Authentication Mode. * Click to Pay: Fixed an issue where Click to Pay sessions always attempted to use HTTP Signature authentication, even when P12 authentication was configured. * REST API Authentication: Unified Checkout and Click to Pay now correctly support both HTTP Signature and P12 authentication modes in Live and Sandbox environments. * P12 authentication: Fixed the `REST API credentials not configured` error that could occur for merchants using P12 authentication.  == Developer ==  * Added PHPUnit test coverage. * Added the `build-release.sh` release build script. * Added `.distignore` configuration. * Locked down the `tests/` directory for release builds.  = 2.5.1 — September 1, 2026 =  == Security ==  * **Improved webhook security:** Webhook requests are now rejected with a `401 Unauthorized` response when the Webhook Security Key is not configured. * **Restricted webhook order lookup:** Webhooks now require a valid numeric client reference and an order that was originally paid using this payment gateway. * **Improved transaction response security:** HMAC verification is now performed before any order metadata is written. Failed verification no longer changes the order status to `failed`. * **Improved Secure Acceptance secret validation:** An empty Secure Acceptance Secret Key is now treated as a verification failure. * **Prevented order status downgrade:** Signed but replayed or delayed `DECLINE`, `ERROR`, or `CANCEL` notifications can no longer change an already-paid order to an unsuccessful status. * **Improved saved card security:** Saved cards are now resolved only through WooCommerce payment-token ownership checks, ensuring that logged-in customers can only use their own saved payment methods. * **Protected payment tokens:** Raw CyberSource tokens are no longer exposed to the browser or accepted directly from checkout requests. Checkout now uses the WooCommerce payment token ID.  == Fixed ==  * **Unified Checkout:** Fixed an issue where Unified Checkout sessions did not correctly respect the configured REST API Authentication Mode. * **Click to Pay:** Fixed an issue where Click to Pay sessions always attempted to use HTTP Signature authentication, even when P12 authentication was configured. * **REST API Authentication:** Unified Checkout and Click to Pay now correctly support both HTTP Signature and P12 authentication modes in Live and Sandbox environments. * **P12 authentication:** Fixed the `REST API credentials not configured` error that could occur for merchants using P12 authentication.  == Developer ==  * Added a comprehensive PHPUnit test suite with **49 tests** covering payment-token ownership, webhook signature verification, REST authentication mode selection, JWT construction, and log masking. * Added automated release packaging using `build-release.sh` and `.distignore`. * Release builds now prevent development files such as `tests/`, `vendor/`, `composer.*`, and `phpunit.xml` from being included in the customer ZIP. * Hardened the `tests/` directory against accidental deployment using Apache access restrictions, silence files, and CLI-only execution guards.  = 2.5.0 =  — 10 May 2026  - New Features:    * Added P12 Certificate authentication support for both SOAP (Simple Order API) and REST API.    * Supports CyberSource’s new security requirements using WS-Security X.509 and JWT authentication.    * Added separate Live/Test P12 settings fields and passphrase options for SOAP and REST APIs.    * Added “Test P12 Connection” buttons for SOAP and REST authentication validation.    * Added certificate validation, expiry checking, and admin warning notices.    * Added Simple Order API (SOAP) as a selectable Integration Type.    * Added SOAP + WooCommerce Subscriptions support.    * Added WooCommerce Blocks checkout support for SOAP integration.    * Added automatic renewal billing support for WooCommerce Subscriptions using SOAP API.    * Added support for saved payment tokens and payment method updates.    * Added detailed WooCommerce logging for SOAP and REST P12 operations.  - Fixes:    * Fixed PHP warnings for inherited class properties.    * Fixed SOAP script loading for subscription integrations.    * Fixed WooCommerce Blocks payment processing compatibility.    * Fixed saved token handling and card validation in Blocks checkout.    * Fixed billing email fatal error in WooCommerce Blocks context.    * Fixed SOAP subscription renewals when using P12 authentication mode.    * Fixed PHP 8.1+ deprecation warnings for SoapClient::__doRequest().  - Improvements:   * Refactored CybsClient.php for improved SOAP request handling and P12 authentication support.   * Improved REST API JWT authentication handling using RS256 signing.   * Improved logging and debugging tools with direct log access links.   * Improved compatibility for both Classic Checkout and WooCommerce Blocks checkout.  = 2.2.0 = - 25 April 2026 * NEW: Unified Checkout (UCO) integration with support for Google Pay, Apple Pay, Paze, Click to Pay, and card entry (PAN). * NEW: Added get_unified_session_uco() method to create UCO sessions with configurable allowedPaymentTypes and paymentConfigurations. * NEW: Added process_uco_payment() for server-side authorization using transient token (JWT) from UCO wallet payments. * NEW: AJAX endpoint (cybsawm_get_uco_session / cybsawm_ajax_get_uco_session) to securely fetch UCO session JWT. * NEW: Added wc-cybersource-uco.js script for Classic WooCommerce checkout UCO integration (session fetch, SDK load, mount, error handling). * NEW: Added UCOContent React component for WooCommerce Blocks checkout with automatic order submission on token capture. * NEW: Block checkout data now includes UCO config (enable flag, AJAX URL, nonce, SDK URL, payment types). * NEW: Added “Unified Checkout — Digital Wallets” settings section:        - Enable Unified Checkout        - Allowed Payment Types (GOOGLEPAY, APPLEPAY, PAZE, CLICKTOPAY, PANENTRY)        - Click to Pay Auto-Enroll option * NEW: Added enqueue_uco_script() to properly load UCO assets and pass required parameters to frontend. * FIXED: Updated Content Security Policy (CSP) to support Google Pay, Apple Pay, and Paze domains. * FIXED: Added wildcard support for CyberSource SDK domains to allow UCO asset loading. * NOTE: Requires CyberSource REST API credentials (Key ID and Shared Secret). Existing credentials can be reused.  = 2.1.1 - 13 April 2026 = * SECURITY: Strengthened HMAC-SHA256 signature verification using hash_equals() to prevent timing attacks. * SECURITY: Signature verification is now always enforced (admin toggle removed). * SECURITY: Sanitized device_fingerprint_id input before SOAP requests. * SECURITY: Removed logging of CVV and sensitive card data (PCI compliance). * SECURITY: Masked sensitive fields in logs (card numbers, CVV, tokens, API keys, personal data). * SECURITY: Fixed IP spoofing issue by using WooCommerce IP detection. * SECURITY: Escaped inline JavaScript outputs to prevent XSS. * SECURITY: Replaced wp_redirect() with wp_safe_redirect(). * SECURITY: Removed HMAC signature values from logs. * SECURITY: Blocked direct access to sensitive library/config files.  * FIX: Resolved signature verification failure on HPOS-enabled sites. * FIX: Corrected signature mismatch caused by escaped POST data (wp_unslash applied). * FIX: Updated all order meta access for full HPOS compatibility.  * NEW: Added centralized log masker to automatically sanitize all debug logs.  * DEV: Removed leftover debug outputs (print_r, var_dump, etc.).  * NOTE: Ensure CyberSource Secret Key is configured before upgrading, as signature verification is now mandatory.  Version 2.0.0 – Major Release  New Features: - WooCommerce Subscriptions integration     * Automatic recurring payments via CyberSource Recurring Billing (SOAP) - Add Payment Method support from My Account page (SOAP tokenization) - Saved card UI for Classic and WooCommerce Blocks checkout - One-click "Set Defaults" buttons for Signed Field Names (Hosted Checkout & Checkout API) - Webhooks support     * Real-time payment notifications (authorization, capture, refund, disputes)     * Ensures WooCommerce order statuses stay in sync automatically - Improved secure REST logging with card numbers masked - PHP 7.4 – 8.3 compatibility  Improvements: - Improved subscription renewal workflow - Better saved token handling - Enhanced checkout UX for subscription products  = 1.54.49 =  - 29 June 2025 - FIXED: MDD Fields 4 sanitized html.  = 1.54.48 =  - 17 June 2025 - FIXED: MDD Fields char length, and custom removed fields.  = 1.54.47 =  13 June 2025 FIXED: Remove phone number with extra space (Hosted Checkout and Checkout API)  = 1.54.46 =  - 31 January 2025 - UPDATE: Purchase Level 3 Checkout API Integration  = 1.53.46 =  - 04 November 2024 - UPDATE: YITH WooCommerce Multi-step Checkout Plugin supported ( Hosted Checkout only)  = 1.52.46 =  - 30 October 2024 - UPDATE: Purchase Level 3 signed fields settings  = 1.51.46 =  - 29 October 2024 - FIXED: Purchase Level 3 settings - FIXED: allowed cybersource reason code  = 1.51.45 =  - 28 October 2024 - UPDATE: Purchase Level 3 integration in Cybersource Hosted checkout shipping address update  = 1.50.45 =  - 26 September 2024 - UPDATE: Purchase Level 3 integration in Cybersource Hosted checkout  = 1.49.45 =  - 8 Aug 2024 - FIXED: decline error in footer  = 1.49.44 =  - 29 July 2024 - UPDATE: Billing Address and Shipping Address Auto Split Cybersource max length  = 1.48.44 =  - 20 July 2024 - UPDATE: Additional Security Validation in Post Back Response  = 1.47.44 =  - 15 July 2024 - FIXED: JQuery undefined in WooCommerce receipt page  = 1.47.43 =  - 12 July 2024 - UPDATE: WooCommerce Checkout Blocks Cybersource Payment Integration - UPDATE: Cybersource Hosted Checkout Supported by Checkout Block  = 1.46.43 =  - 28 June 2024 - FIXED: Hosted(WM) and Checkout API(SOP) Bug Billing and Shipping Address length validator  = 1.46.42 =  - 18 May 2024 - FIXED: Bugs MDD fields has previous order  = 1.46.41 =  - 1 May 2024 - FIXED: Bugs Mobile number prefix (+) Hosted Checkout and Checkout API  = 1.46.40 =  - 28 Feb 2024 - UPDATE: Update Mobile Phone number for Payer Authentication Enrollment - FIXED: Missing Transaction UUID  = 1.45.39 =  - 22 Jan 2024 - UPDATE: plugin text and description  = 1.44.39 =  - 19 Jan 2024 - UPDATE: Cybersource mandatory update in Feb2024, Payer Authentication Enrollment   New Fields customer_browser_screen_height,customer_browser_screen_width,payer_authentication_mobile_phone - FIXED: Secure Acceptance Hosted Checkout API Void,Capture, Reverse using SOAPToolkit  = 1.43.38 =  - 24 Nov 2023 - UPDATE: Update Code WM & SOP for High-Performance Order Storage (HPOS)  = 1.42.38 =  - 21 Nov 2023 - UPDATE: add code to support High-Performance Order Storage (HPOS) - UPDATE: Remove SOAP Toolkit in the Dropdown list menu integration - FIXED: fixed php8 deprecated code  = 1.41.38 =  - 22 August 2023 - FIXED: Soap Toolkit Integration  = 1.41.37 =  - 14 April 2023 - FIXED: add order id reference in mdd19 - FIXED: default address length to 60 characters for all cybersource integration  = 1.41.36 =  - 23 Feb 2023 - FIXED: default address length to 60 characters for all cybersource processor  = 1.41.35 =   - 20 Nov 2022 - FIXED: Settings Warnings. - FIXED: MDD3 & MDD4 strip tags  = 1.41.34 =  - 19 Oct 2022 - UPDATE: SOP and SO add card backend validation. - UPDATE: SO API end points  = 1.41.33 =  - 25 Sep 2022 - UPDATE: WPML Supported.  = 1.40.33 =  - 15 Aug 2022 - FIXED: fix the mdd function already exist.  = 1.40.32 =  - 30 July 2022 - UPDATE: Secure Acceptance Hosted and Checkout API MDD fields Integration. - UPDATE: Secure Acceptance Hosted and Checkout API Shipping fields override.  = 1.39.32 = - 15 June 2022 - FIXED: duplicate or validator and error message  = 1.39.31 = - 12 June 2022 - FIXED: Add duplicate order number validator  = 1.39.30 = * 25 March 2022 * UPDATE: Order ID validator  = 1.38.30 = * 30 January 2022 * UPDATE: Cybersource signature verification plugin settings   = 1.37.30 = * 29 December 2021 * FIXED: Card expiry input  = 1.37.29 = * 19 December 2021 * UPDATE: Hosted Checkout refund(void and capture) * UPDATE: Checkout API refund(void, reversal and capture) * UPDATE: Soap Toolkit API refund (void, reversal and capture)  = 1.36.29 = * 08 December 2021 * Fixed: unsigned fields for Hosted checkout and Checkout API * UPDATE: add the customer payment method  = 1.35.28 = * 26 August 2021 * Fixed: special chars in customer information  = 1.35.27 = * 30 April 2021 * Fixed: Cybersource Deprecated and error notices  = 1.35.26 = * 22 April 2021 * UPDATE: Cybersource Secure Acceptance Default Order status  = 1.34.26 = * 17 January 2021 * FIXED: Cybersource Secure Acceptance redirect wc_add_notice in checkout page  = 1.34.25 = * 15 January 2021 * UPDATE: Custom page setting redirect * UPDATE: WM and SOP Order status * UPDATE: Remove payment fields filter()  = 1.33.25 = 15 December 2020 UPDATE: SOAP add a payment method UPDATE: SOAP add payment tokenization UPDATE: SA change redirect page to cart page if the decision is an error/canceled  = 1.32.25 = * 27 November 2020 * FIXED:  Cannot redeclare tgmpa()  = 1.32.24 = * 15 November 2020 * UPDATE: Cybersource Secure Acceptance Signed Field Names Signature Verification * FIXED:  Cybersource Secure Acceptance Saved Customer Token  = 1.31.23 = * 22 September 2020 * UPDATE: Envato Market WordPress Plugin integration for remote plugin updates  = 1.30.23 = * 17 September 2020 * FIXED: WC order and Cybersource status bugs * TESTED: WC 4.4.1 * TESTED: WP 5.5.1  = 1.30.22 = * 30 June 2020 * UPDATE: Mask Card code settings * UPDATE: SO/SOAP Void Transaction * UPDATE: SO/SOAP error message with reason code * UPDATE: WM/SOP error message with reason code  = 1.29.22 = * 22 April 2020 * UPDATE: purchase level payment card allowed * UPDATE: Custom Cardholder Message  = 1.28.22 = * 01 April 2020 * UPDATE: Secure Acceptance WC/Cybersource status sync  = 1.27.22 = * 27 March 2020 * FIXED: SO capture bug  number format * FIXED: SO capture button bug multi language  = 1.27.21 = * 23 March 2020 * UPDATE: SO additional level 3 paramaters - 'purchaseTotals_dutyAmount' - 'purchaseTotals_freightAmount' - 'purchaseTotals_discountAmount' * UPDATE: SO Auto-capture * FIXED: SO Fixed multiple Items * FIXED: SO Fixed Unit Price  = 1.26.20 = * 07 February 2020 * UPDATE: SO Purchasing Level 2 & Level 3 Processing * UPDATE: SO Purchasing Level Units of Measurement * UPDATE: SO Purchasing Level Item Commodity Code * FIXED: pcode bug extra unused params  = 1.25.19 = * 19 January 2020 * UPDATE: SO add void button for SOAP * UPDATE: SO add void capture for SOAP * UPDATE: SO add void reversal for SOAP * UPDATE: Removed REST API module because it confusing to the customer. I will create a separate plugin for this module.  = 1.24.19 = * 8 January 2020 * UPDATE: REST API Device Fingerprinting Implementation * FIXED: REST API BUG response code 00   = 1.23.18 = * 31 December 2019 * UPDATE: update default signed field names * FIXED: remove rest API capture button in the sop and wm  * UPDATE: MMD REST API implemented  = 1.22.17 = * 19 October 2019 * UPDATE: REST API Integration * FIXED: SOAP MDD Fields  * TWEAK: Adjustable Customer Address length settings  = 1.21.16 = * 8 September 2019 * UPDATE: Silent Order Post (SOP) Subscription Integration  = 1.20.16 = * 27 July 2019 * UPDATE: Payment Settings * FIXED: billing address validation max length * TESTED: Wordpress Version up to 5.2.2 * TESTED: WooCommerce Version up to 3.6.5 * TESTED: PHP 7 Version up to 7.2.20 * TESTED: MySQL Version up to 5.6.41-84.1  = 1.19.15 = * 20 July 2019 * FIXED: save token not working in the first time checkout * FIXED: PHP SOAP if not exist no method available * TESTED: Wordpress Version up to 5.2.2 * TESTED: WooCommerce Version up to 3.6.5 * TESTED: PHP 7 Version up to 7.2.20 * TESTED: MySQL Version up to 5.6.41-84.1  = 1.19.14 = * 05 May 2019 * UPDATE: Envato Author WordPress Plugin Requirements * UPDATE: WC_Payment_Tokens implementation * UPDATE: add order id into cybersource_add_signed_field_names filter to apply_filters( 'cybersource_add_signed_field_names', $order_id, true ); * FIXED: Offer-Line Details add new validation for a single quote (') item_x_name  = 1.18.13 = * 24 Dec 2018 * FIXED: SO and SOP Card Expiration Year * UPDATE: Add Extra links online documentation and support * TESTED: Wordpress Version up to 5.0.3 * TESTED: WooCommerce Version up to 3.5.3  = 1.18.12 = * 03 Nov 2018 * UPDATE: depricated calls for WC 3.5.x * FIXED: payment form html * TESTED: Wordpress Version up to 4.9.9 * TESTED: WooCommerce Version up to 3.5.1  = 1.17.11 =  * 06 Oct 2018 * UPDATE: Add random number in consumer_id if guest user. * UPDATE: Add save token if merchant notication is active. * FIXED: Deprecated woocommerce order_key  * FIXED: Deprecated woocommerce WC_Cart::get_checkout_url()  * FIXED: Deprecated woocommerce get order id * FIXED: Deprecated woocommerce get status  * FIXED: Deprecated woocommerce woocommerce_clean * FIXED: Deprecated woocommerce credit_card_form * TESTED: Wordpress Version up to 4.9.9 * TESTED: WooCommerce Version up to 3.4.5  = 1.16.10 =  * 05 July 2018 * UPDATE: License API URI Validator  = 1.15.10 =  * 30 June 2018 * UPDATE: Support WooCommerce Subscription Addon  = 1.14.10 =  * 06 June 2018 * UPDATE: add consumer_id field in Secure Acceptance Web/Mobile * UPDATE: Merchant Notifications Post URL Supported (http://my-store.com/?wc-api=WC_API_Cybersource_SAWM&mnp=1). * UPDATE: Redirection Message CSS Div Block Mobile Responsive Supported. * TESTED: Wordpress Version up to 4.9.9 * TESTED: WooCommerce Version up to 3.3.5  = 1.13.10 =  * 10 Mar 2018 * FIXED: woocommerce_clean is deprecated.  * FIXED: item name with special characters. * FIXED: bill_to_company_name maximmum of string(40) length error * NEW: add new feature counter check for the order status if the cybersource payment success but the order status still pending  = 1.12.9 =  * 21 Jan 2018 * NEW: add new readme.txt for plugin compatibality.  * FIXED:  Simple Order API (SOAP) - SOAP-ERROR: Parsing WSDL: Couldn't load  * TESTED: Wordpress Version up to 4.9 * TESTED: WooCommerce Version up to 3.2  = 1.11.8 =  * 01 Dec 2017 * NEW: Fingerprint Device ID Profiler * New: Multisite Supported  * UPDATE: Simple Order API (SOAP) -  Options Settings to disable Address Verification Services (AVS) * UPDATE: Options to set Accepted Card Logos  = 1.10.7 =  * 09 Oct 2017 * UPDATE: Web/Mobile Save Card / eCheck Options  = 1.9.6 =  * 09 Sept 2017 * UPDATE: Total amount type order to (double).  * UPDATE: Add new settings for MDD Fields.  * UPDATE: Add New settings CodeCanyon Purchase Code Activation. * FIXED:  Bugs when submitting cart item name to cybersource with '"'.   = 1.8.5 (30 july 2017 ) =  UPDATE: Additional Signed Field Names          - merchant_id         - Merchant Defined Data (MDD) Fields UPDATE: Request and Response Logger for Cybersource Simple Order API(SOAP) FIXED: Removed Order Noted ($order->add_order_note()) call function creating error on transaction_response()    = 1.7.4 (16 july 2017 ) =  NEW: Cybersource APIs option settings       - Simple Order API (SOAP)       - Secure Acceptance Silent Order POST       - Secure Acceptance Web/Mobile       - Secure Acceptance Web/Mobile & Silent Order POST NEW: additional custom code functionality Merchant Defined Data (MDD) Fields add_filter implementation.       UPDATE: Cybersource Profile credentials live and test option settings UPDATE: additional settings disable round off total amount UPDATE: additional settings disable round off line tax amount and line total amount UPDATE: additional Generate HEADER HTML function into the settings UPDATE: additional Generate HR HTML function into the settings FIXED: Support WC version 3.x Customer information getters function during checkout and order receipt.  FIXED: Get Product SKU.  = 1.6.3 (28 mar 2017) =  UPDATE: Additional Signed Field Names         bill_address1         bill_city  = 1.5.3 (11 mar 2017) =  FIXED: item_0_unit_price invalid format.  = 1.5.2 (02 mar 2017) =  UPDATE: Checkout Reference Order Id change to Order No. UPDATE: Auto Detect if order is virtual. the order status is automatically complete after payment.  FIXED: Web/Mobile Secure Acceptance not using token.  = 1.4.1 (16 feb 2017) =  UPDATE: Option to set enable save card.  = 1.3.1 (06 feb 2017) = FIXED: Fatal error, Can't use method return value in write context line 437 FIXED: Logger Request and Response Parameters  = 1.3.0 (14 Nov 17) = UPDATE: Additional Signed Field Names  ship_to_address_city, ship_to_address_country, ship_to_address_line1, ship_to_address_line2, ship_to_address_postal_code, ship_to_address_state, ship_to_forename, ship_to_phone, ship_to_surname, tax_amount, item_#_name, item_#_code, item_#_quantity, item_#_sku, item_#_unit_price, item_#_tax_amount, line_item_count UPDATE: Additional Offer-Line Details Settings UPDATE: Plugin Name and Description Update UPDATE: Payment Gateway method title and Description Update UPDATE: Additional plugin settings links  = 1.2.0 (22 Nov 17) = UPDATE: Storing card tokens for future payments UPDATE: Web/Mobile and SOP Integration  = 1.0.0 (21 july 15) = INIT: Initial release version