Changeset 3488135
- Timestamp:
- 03/22/2026 10:02:10 AM (13 days ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
sagepay-form-gateway-for-woocommerce/tags/1.4.7/readme.txt
r3488133 r3488135 1 1 === SagePay Form Gateway for WooCommerce === 2 2 Contributors: patsatech 3 Tags: ecommerce, payment gateway, woocommerce, sagepay form,sagepay go3 Tags: ecommerce, payment gateway, woocommerce, opayo, sage pay, elavon, checkout 4 4 Requires at least: 4.5 5 5 Tested up to: 6.9 … … 9 9 License: GPLv2 or later 10 10 11 SagePay Form Gateway for accepting payments on your WooCommerce Store.11 Accept card payments in WooCommerce using Opayo Form (hosted payment page), formerly Sage Pay Form — Elavon. 12 12 13 13 == Description == 14 14 15 SagePay Form integration is the easiest way to start processing online payments. It can take as little as 20 minutes to set up and is by far the quickest way to integrate Sage Pay.15 This plugin adds a WooCommerce payment gateway for Opayo Form integration (Sage Pay Form / Elavon hosted form). Customers pay on Opayo’s secure page, so your site does not collect or store card numbers, which reduces PCI scope compared with on-site card fields. 16 16 17 Form integration is designed to pass transaction details from your website to Sage Pay to carry out authorisation. Outsourcing your payment processing in this way means that no sensitive data is collected, stored or transferred from your site. 17 How it works: 18 18 19 This Plugin allows you to accept SagePay Payments removing the need for you to maintain highly secure encrypted databases, obtain digital certificates and invest in high-level PCI DSS compliance. 19 * At checkout, the shopper is redirected to Opayo with an encrypted payload (Crypt) built from the order. 20 * After payment, Opayo sends the customer back to your site; the plugin decrypts the response, checks the order and amount, and completes the order when the payment is successful. 21 * Supports classic checkout and registers with WooCommerce Blocks checkout when the block checkout is enabled. 22 23 Requirements: 24 25 * WordPress and WooCommerce (see readme headers for tested versions). 26 * An Opayo account with Form integration and credentials from MyOpayo (Vendor name, Encryption password). 27 * HTTPS is strongly recommended for checkout and payment return URLs. 28 29 Notes: 30 31 * Uses Elavon’s current Form register hosts (`sandbox.opayo.eu.elavon.com` / `live.opayo.eu.elavon.com`) and VPSProtocol 4.00. Override the register URL with the `woocommerce_sagepayform_register_url` filter if your account requires a different endpoint. 32 * Override the return/notify URL with `woocommerce_sagepayform_notify_url` if needed. 33 34 Use Elavon / Opayo’s official documentation for account setup, test cards, and regional rules. 20 35 21 36 == Installation == 22 37 23 1. Download and unzip the latest release zip file. 24 2. If you use the WordPress plugin uploader to install this plugin skip to step 4. 25 3. Upload the entire plugin directory to your `/wp-content/plugins/` directory. 26 4. Activate the plugin through the 'Plugins' menu in WordPress Administration. 38 1. Install and activate WooCommerce. 39 2. Install this plugin: 40 * WordPress admin: Plugins → Add New → Upload Plugin, select the zip, Install Now, then Activate; or 41 * Copy the plugin folder into `wp-content/plugins/` (FTP, Git deploy, etc.), then activate under Plugins. 42 3. Open WooCommerce → Settings → Payments, enable “SagePay Form”, then Manage / Set up. 43 4. Enter Vendor Name, Encryption password, Vendor email, and set Mode to Test or Live to match your MyOpayo (sandbox vs live). Adjust 3-D Secure, transaction type (Payment / Deferred / Authenticate), emails, and card icons as needed. 44 5. Save settings. Complete a test payment in Test mode using Opayo’s test card details before going live. 45 46 After installation: 47 48 * Use HTTPS on the storefront and ensure pretty permalinks (or your server rules) allow the WooCommerce API callback at `/wc-api/woocommerce_sagepayform`. 49 * For staging or extra domains, configure allowed URLs or IPs in MyOpayo so Success/Failure redirects are accepted. 27 50 28 51 == Changelog ==
Note: See TracChangeset
for help on using the changeset viewer.