Autify Digital Ltd Lloyds Cardnet Gateway

Lýsing

A comprehensive payment gateway integration between WooCommerce and Lloyds Cardnet Payments. Accept payments from customers using Visa, Mastercard, American Express, etc via Hosted Payment page or Payment JS solution. This plugin is specifically designed to work with British Pound (GBP) and Euro (EUR) currencies.

Key Features:
– Multiple payment methods: Hosted Payment Page (HPP), Payment JS, Apple Pay, and Google Pay
– Full tokenization support – customers can securely save cards for future purchases
– WooCommerce Subscriptions compatibility for recurring payments
– Smart 3D Secure authentication with dynamic challenge requirements
– MOTO (Mail Order/Telephone Order) support for admin-initiated transactions
– Advanced fraud prevention with customizable security settings
– Comprehensive webhook support for reliable payment status updates

Lloyds Bank Cardnet (LBOP) WooCommerce Integration

Features

= Payment Methods =

Multiple Payment Options – Accept all major credit and debit cards (Visa, Mastercard, American Express, etc.)
Digital Wallets – Integrated Apple Pay and Google Pay support
Express Checkout – Display Apple Pay and Google Pay buttons on product, cart, and checkout pages
Redirect Payment – Secure hosted payment page option for PCI compliance
Embedded Payment (Payment.JS) – Seamless checkout with payment form directly on your site

Advanced Payment Features

Tokenization – Allow customers to securely save card details for faster future purchases
Subscription Support – Set up recurring payments for subscription-based services
MOTO Payments – Process Mail Order/Telephone Order payments securely from WooCommerce admin
Refund Processing – Handle full and partial refunds directly from your WooCommerce dashboard
International Payments – Configure multiple currencies and selling locations

Security & Management

PCI Compliance – Transactions processed by Lloyds Bank Cardnet, not on your server
Secure Payment Handling – All sensitive payment data handled by certified payment processor
Easy Dashboard Management – Monitor transactions and order statuses from WooCommerce
Webhook Support – Real-time payment status updates
REST API Integration – Modern API implementation for reliable performance

Getting Started

Ensure you have an active Lloyds Bank Cardnet merchant account
Purchase and download the plugin from Autify Digital
Install the plugin on your WooCommerce site
Configure with your Store ID and Shared Secret
For embedded payments, add REST API credentials
Configure payment methods and options
Test with sandbox credentials
Go live with production credentials

For detailed installation instructions, refer to the documentation provided with your plugin purchase.

Support

For technical support, customization requests, or general inquiries:
Email: cardnet@autify.co.uk
Visit: https://www.autify.co.uk

External Services

This plugin relies on the following third-party/external services to function. By using this plugin, data may be transmitted to these services as described below. Please review the respective terms and privacy policies.

1. Lloyds Cardnet Payment Gateway

Used for processing card payments through the Lloyds Bank Cardnet merchant account.
Data sent: Order details, payment amounts, currency, customer billing/shipping address, and card transaction data. Sent when a customer initiates a payment.

– Service Link: Lloyds Cardnet
– Terms of Use: Lloyds Cardnet Terms of Service
– Privacy Policy: Lloyds Cardnet Privacy Policy

2. First Data / Fiserv Payment Processing (IPG Online)

Used for processing hosted payment page (redirect) transactions, Payment JS embedded payments, and refunds via the First Data API.
Data sent: Store ID, API credentials, payment amounts, currency, order reference, card tokens, and refund details. Sent when a customer makes a payment, when a session is initialized for embedded payments, or when a merchant processes a refund.

– API Endpoints:
– Hosted Payment Page (Sandbox): https://test.ipg-online.com/connect/gateway/processing
– Hosted Payment Page (Production): https://www.ipg-online.com/connect/gateway/processing
– API (Sandbox): https://cert.api.firstdata.com/
– API (Production): https://prod.api.firstdata.com/
– Terms of Use: Fiserv Terms of Use
– Privacy Policy: Fiserv Privacy Notice

3. First Data Payment JS Client Library

A JavaScript library loaded from First Data servers to render the secure embedded payment form (card number, expiry, CVV fields) on the checkout page. The library handles card data directly — no card details pass through your server.
Data sent: Card details are entered directly into the Payment JS iframe and transmitted to First Data. The plugin receives a payment token in return. The library is loaded when the checkout page renders with the embedded payment method enabled.

– JavaScript (Sandbox): https://lib.paymentjs.firstdata.com/uat/client-2.0.0.js
– JavaScript (Production): https://lib.paymentjs.firstdata.com/prod/client-2.0.0.js
– Documentation: Payment JS Documentation
– Terms of Use: Fiserv Terms of Use
– Privacy Policy: Fiserv Privacy Notice

4. Fiserv Checkout Solution

Used as an alternative checkout integration via the Fiserv eCommerce API for payment processing.
Data sent: Store ID, API credentials, order amounts, currency, and checkout configuration. Sent when a customer initiates a payment using the checkout solution method.

– API (Production): https://prod.emea.api.fiservapps.com/exp/v1/checkouts
– API (Sandbox): https://prod.emea.api.fiservapps.com/sandbox/exp/v1/checkouts
– Terms of Use: Fiserv Terms of Use
– Privacy Policy: Fiserv Privacy Notice

5. Apple Pay

Used to enable Apple Pay as an express payment method on product, cart, and checkout pages.
Data sent: The merchant identifier, site domain, and display name are sent to Apple during merchant validation when a customer initiates an Apple Pay payment. Payment and shipping data is then processed through the First Data / Fiserv API.

– Service: Apple Pay
– Terms of Use: Apple Pay Platform Web Merchant Terms
– Privacy Policy: Apple Privacy Policy

6. Google Pay

Used to enable Google Pay as an express payment method on product, cart, and checkout pages. A JavaScript library is loaded from Google servers to render the Google Pay button and handle the payment flow.
Data sent: Payment token data (encrypted by Google) and customer shipping/billing details are sent from the Google Pay interface to the plugin, then processed through the First Data / Fiserv API. The Google Pay JS library is loaded when the Google Pay payment method is enabled.

– JavaScript: https://pay.google.com/gp/p/js/pay.js
– Service: Google Pay
– Terms of Use: Google Pay Terms of Service
– Privacy Policy: Google Privacy Policy

7. Autify Digital License API

Used to validate and manage the plugin license. The plugin contacts Autify Digital’s license server to verify that the license key is valid and active.
Data sent: License key, plugin version, site domain, admin email, contact name, and activation status. Data is sent when the license is activated, deactivated, or periodically synced.

– Service: Autify Digital
– API Endpoint: https://plugin-licenses.autify.co.uk/wp-json/autifydigital/v1/plugin
– Terms of Use: Autify Digital Terms and Conditions
– Privacy Policy: Autify Digital Privacy Policy

Skjámyndir

  • Plugin Settings – Configure your Lloyds Bank Cardnet payment gateway with Store ID, API credentials, and payment mode selection
  • Payment Failed Page – Clear error messaging when a payment is declined, allowing customers to retry with alternative payment methods
  • Order Management – View and manage orders with complete transaction details including payment reference and customer information
  • Refund Processing – Process full or partial refunds directly from the WooCommerce order page with automatic gateway integration
  • Order Confirmation – Customer order received page showing successful transaction completion with order details
  • Transaction Reports – Comprehensive transaction reporting dashboard showing payment status, order IDs, and transaction history
  • Checkout Experience – Embedded payment form (Payment.js) integrated directly into the WooCommerce checkout page with card details input and Google Pay option.

Uppsetning

This section describes how to install the plugin and get it working.

  1. Upload the plugin in ‘/wp-content/plugins/’ directory
  2. Activate the plugin through the ‘Plugins’ menu in WordPress
  3. Set the plugin settings from payment section in wp admin

SOS

What do I need before installing this plugin?

You need an active Lloyds Bank Cardnet merchant account. The plugin cannot assist with account setup – please visit Lloyds Bank Business website to apply for an account first. You’ll also need WooCommerce installed and configured on your WordPress site.

What credentials do I need from Lloyds Bank?

You’ll need:

Store ID and Shared Secret (provided when setting up your merchant account)
For embedded payments: REST API Key and API Secret from the Developer Portal
The REST API keys need to be linked to your Store ID by Lloyds Bank

Is professional installation available?

Yes, Autify Digital offers a professional installation service where their technical team will configure the plugin to your requirements.

Which payment methods are supported?

The plugin supports all major credit and debit cards (Visa, Mastercard, American Express, etc.), plus Apple Pay and Google Pay digital wallets.

Can I offer both redirect and embedded payment options?

No, you need to choose one payment method – either the redirect to hosted payment page OR the embedded Payment.JS solution on your checkout page.

Where can Apple Pay and Google Pay buttons be displayed?

Express checkout buttons can be displayed on product pages, cart page, and checkout page, allowing customers to skip the standard checkout process.

Can I process refunds through WooCommerce?

Yes, you can process both full and partial refunds directly from the WooCommerce order management interface.

Does the plugin support subscriptions?

Yes, the plugin supports recurring payments for subscription services. This feature is only available with card payments (not digital wallets).

What is MOTO payment functionality?

MOTO (Mail Order/Telephone Order) allows you to securely process payments taken over the phone or email directly from the WooCommerce admin area.

Can customers save their card details?

Yes, through tokenization, customers can securely save their card details for faster checkout in future purchases. The actual card data is never stored on your server.

Is the plugin PCI compliant?

When using either the hosted payment page or embedded payment solution, all transactions are processed by Lloyds Bank Cardnet’s PCI-compliant infrastructure, not on your server. This significantly reduces your PCI compliance scope.

How is sensitive payment data protected?

Card details are never stored on your WooCommerce site. All sensitive data is handled by Lloyds Bank Cardnet using tokenization for saved cards and secure transmission protocols.

Do I still need SSL on my website?

Yes, you should always have a valid SSL certificate on your e-commerce website for general security and customer trust, even though payment processing happens on Lloyds Bank’s secure servers.

What are the minimum requirements?

WordPress 5.0 or higher
WooCommerce 3.5 or higher
PHP 7.2 or higher
Valid SSL certificate
Active Lloyds Bank Cardnet merchant account

Does the plugin support multiple currencies?

Yes, the plugin includes international payment settings allowing you to configure multiple currencies and selling locations based on your merchant account capabilities.

How are payment notifications handled?

The plugin uses webhooks for real-time payment status updates. The webhook URL needs to be configured in your Lloyds Bank Cardnet account.

What if payments are being declined?

Check that:

Your Lloyds Bank Cardnet account is active
API credentials are correctly entered
REST API keys are linked to your Store ID (for embedded payments)
CVV verification is disabled as per setup requirements

Can I test the plugin before going live?

Yes, Lloyds Bank Cardnet provides test credentials and a sandbox environment. Configure these in the plugin settings to test transactions without processing real payments.

Where can I see transaction logs?

Transaction logs and order statuses can be viewed in the WooCommerce reporting dashboard. Detailed transaction information is also available in your Lloyds Bank Cardnet merchant portal.

Is technical support available?

Yes, Autify Digital provides reliable installation and post-integration support. Contact cardnet@autify.co.uk for technical assistance.

Can the plugin be customized for specific business needs?

Yes, Autify Digital offers customization services for businesses needing tailored features or configurations beyond the standard plugin functionality.

How do I update the plugin?

Plugin updates are provided through your Autify account. Always backup your site before updating and test updates on a staging environment first.

What if I need to switch from redirect to embedded payments?

You can switch between payment methods in the plugin settings. For embedded payments, you’ll need to obtain and configure REST API credentials from the Developer Portal.

Is this plugin compatible with other WooCommerce extensions?

The plugin is designed to work with standard WooCommerce installations. Compatibility with specific third-party extensions should be tested on a case-by-case basis.

Can I use this plugin on multiple sites?

Licensing terms depend on your purchase from Autify Digital. Check your license agreement or contact support for multi-site usage rights.

Does the plugin work with WooCommerce Blocks?

Please check with Autify Digital support for the latest compatibility information regarding WooCommerce Blocks checkout.

Umsagnir

There are no reviews for this plugin.

Þátttakendur & höfundar

“Autify Digital Ltd Lloyds Cardnet Gateway&#8221 er opinn hugbúnaður. Eftirfarandi aðilar hafa lagt sitt af mörkum við smíði þessarar viðbótar.

Höfundar

Breytingarsaga

3.0.12 –

  • Compliance: Renamed all script, style, and AJAX action handles to use unique „autify-lloyds-“ prefix to meet WordPress plugin directory naming standards
  • Compliance: Updated nonce names, transient keys, and lock keys with plugin-specific prefixes to prevent namespace collisions
  • Compliance: Renamed global JavaScript variables with „autifyLloyds“ namespace to avoid global scope conflicts
  • Security: Added nonce verification for Apple Pay and Google Pay payment processing AJAX requests (CSRF protection)
  • Security: Added recursive sanitization of webhook data using sanitize_text_field() across all webhook handlers
  • Security: Added input sanitization for $_GET parameters in admin pages using sanitize_text_field() and wp_unslash()
  • Security: Added JSON validation and error checking in PaymentJS webhook handler
  • Security: Added header value sanitization in PaymentJS webhook processing
  • Fix: Added null-safety checks for wc_get_order() across all payment handlers to prevent fatal errors on missing orders
  • Fix: Added isset() guards for AVS/CVV response fields, cart totals, and shipping address data to prevent undefined index notices
  • Fix: Improved JSON decode error handling in Google Pay payment data processing
  • Fix: Added proper validation for shipping methods array access and WP_Query availability checks
  • Enhancement: Order not found errors now display user-friendly notices and redirect to checkout instead of failing silently
  • Enhancement: Improved transaction notification URL validation for incomplete webhook data
  • Code Quality: Removed legacy deleteOldLogFiles() method from Gateway Helper
  • Code Quality: Updated CSS file references to use prefixed filenames

3.0.11 –

  • Compliance: Removed hard-coded „Powered by“ credit link from public-facing payment form to comply with WordPress plugin directory attribution guidelines
  • Compliance: Updated External Services section with full disclosure of all third-party services including Terms of Use and Privacy Policy links
  • Compliance: Added disclosure for Fiserv Checkout Solution, Apple Pay, Google Pay, and Autify Digital License API external services
  • Compliance: Added Fiserv Terms of Use and Privacy Notice links for First Data / IPG Online and Payment JS services
  • Fix: Google Pay Shipment issues

3.0.10 –

  • Performance: Removed flush_rewrite_rules from every page load, now only runs on plugin activation/deactivation
  • Code Quality: WordPress PHPCS compliance improvements
  • Enhancement: 3DS Flow Improvements

3.0.9 –

  • Code Quality: WordPress PHPCS compliance improvements
  • Feature: Configuration to enable or disable subscription
  • Bug Fix: Double Subscription Request

3.0.8 –

  • Code Quality: WordPress PHPCS compliance improvements
  • Bug Fix: GET method call curl issue for the decline transaction

3.0.7 –
– Feature: Transaction Reports table with advanced filtering (status, payment method, date range)
– Feature: CSV export functionality for transaction reports with all filters applied
– Feature: Full-text search across all transaction columns (Order ID, Amount, Status, Card Details, IPs, etc.)
– Feature: Transaction summary statistics showing total transactions, amounts, and refunds
– Feature: Traffic light verification status indicators (CVV, Street, Postcode checks) in reports
– Feature: Transaction details meta box on WooCommerce order view page with payment and fraud details
– Feature: Cardnet Status column in WooCommerce order grid with payment status, verification indicators, and card info
– Enhancement: License sync cron job for automatic license validation
– Enhancement: Unified refund processing across all payment methods (Card, Apple Pay, Google Pay)
– Enhancement: Centralized table name management in gateway helper
– Enhancement: External CSS file for admin styles instead of inline styles
– Enhancement: Support for both legacy post-based orders and HPOS (High-Performance Order Storage)
– Code Quality: WordPress PHPCS compliance improvements
– Code Quality: Added translator comments for i18n strings with placeholders
– Code Quality: Proper variable prefixing for WordPress coding standards
– Code Quality: Added phpcs:ignore comments for WooCommerce core hooks usage
– Dev: Comprehensive unit test coverage for new features
– Dev: Refactored verification status methods to camelCase naming convention

3.0.6 –
– Security: Fixed security vulnerabilities with proper sanitization of $_GET, $_POST, $_REQUEST data
– Security: Added proper validation and sanitization using sanitize_text_field() and wp_unslash()
– Enhancement: Made debug logging conditional – error_log() now only runs when WP_DEBUG is enabled
– Enhancement: Complete WooCommerce address line 2 support across all payment methods (Payment JS, Apple Pay, Google Pay, HPP)
– Enhancement: Comprehensive unit test coverage for all new features and validations
– Fix: Enhanced security for payment token handling and form processing
– Fix: Improved address data handling in redirect payment forms and wallet payments
– Dev: Updated all payment gateway classes with secure data handling practices
– Dev: Enhanced license manager with proper AJAX security and nonce verification
– Dev: Added comprehensive test suite covering address handling, and license management

3.0.5 –
– Enhancement: Full tokenization support for HPP/Redirect payment gateway – customers can now save cards for future use
– Enhancement: Smart 3D Secure handling with dynamic challenge indicators based on transaction type
– Enhancement: Improved code organization with dedicated helper methods for payment data building
– Enhancement: Subscription support improvements with proper token handling for recurring payments
– Fix: Duplicate token saving issue between webhook and order confirmation resolved
– Fix: Session dependency removed from webhook – now uses order meta for reliable server-to-server communication
– Fix: Improved shipping method calculation for wallet payments (Apple Pay and Google Pay)
– Fix: Shipping options now properly update based on customer location
– Fix: Shipping methods now respect WooCommerce zone restrictions and conditions
– Fix: Total calculation now uses backend-calculated values for accuracy
– Enhancement: Dynamic shipping option updates when address changes in wallet payments
– Enhancement: Proper tax and shipping recalculation based on selected address
– Enhancement: PO number building logic refactored for better maintainability
– Dev: Added modular payment request builders (buildPaymentRequestData, buildOrderData, build3DSecureData)
– Dev: Enhanced token storage with duplicate prevention mechanism
– Dev: Removed deprecated class-autify-lloyds-shop-page-handler.php file

3.0.4 –

  • HPOS Declaration

3.0.3 –
– BugFix – Domain issue, as WooCommerce covers it already.
– Apple Pay removal of EMV, as this is not supported.
– Some Code improvements

3.0.2 –
– Feature: Adding Dynamic Order Data configuration and Clear Cookies for My account

3.0.1 –
– Fallback to Hosted Payment Method Support
– A configuration option has been added in Payment JS to enable or disable logging.
– The logger has been standardized to use the WooCommerce logging system, ensuring consistency across all WooCommerce payment methods.

3.0.0 –

  • On-site Wallets: We can process on-site payments via Google Pay or Apple Pay directly from the product, cart, and checkout pages.
  • Tokenisation: The customer can save their cards for future transactions.
  • Subscription: The merchant can accept the subscription of the order via Card payments. The Wallets will not show up if there are subscription products in the cart.
  • MOTO: The merchant can make an MOTO transaction by logging into the Administrator account.

2.0.14 – Fix column addition issue and remove sleep() function
2.0.13 – Load Domain translation issue
2.0.12 – Added configuration for the Order ID suffix as timestamp.
2.0.11 – Fix for country restriction for Embedded Payment and GooglePay Wallet issue.
2.0.10 – Added configuration to pass the order ID or not