=== Fortis for WooCommerce === Contributors: fortispay Tags: e-commerce, woocommerce, payment, fortis, credit card Requires at least: 6.0 Tested up to: 7.1 Requires PHP: 7.4 Stable tag: 1.3.5 License: GPLv3 License URI: https://www.gnu.org/licenses/gpl-3.0.html This is the official Fortis extension to receive payments for WooCommerce. == Description == The Fortis plugin for WooCommerce lets you accept online payments including credit cards, debit cards and ACH. Features: 1. Embedded payments iframe on the checkout page 2. ACH and CC payment methods supported 3. Level 2 and Level 3 processing supported for interchange optimization 3.1 To make use of this function, you will need to add the following product attributes to each product: commodity_code e.g. cc123456 unit_code e.g. gll 4. Webhooks for ACH status update on Settlement 5. Logged-in customers can store CC and ACH details to use for future payments 6. Refund and Void from the Order screen 7. Sandbox mode for testing 8. Customizable payments iframe appearance with two different view options 9. Compatible with WooCommerce Blocks == About Fortis == Fortis delivers comprehensive payment solutions and commerce enablement to software partners and developers, processing billions of dollars annually. The company’s mission is to forge a holistic commerce experience, guiding businesses to reach uncharted growth and scale. Fortis for WooCommerce enables you to offer a seamless and secure payment experience for customers using your e-commerce store. Guest customers make payments via a secure and customizable payments iframe hosted by Fortis. Customers that create accounts have the option to store multiple payment cards to use for future payments that they can select on checkout for a seamless payment experience. == FAQ == = Does this require a Fortis merchant account? = Yes! To use this plugin you will need an account with Fortis. For more information on application and pricing please [contact us](https://go.fortispay.com/woocommerce) = How do I test the plugin? = We recommend testing the plugin in Sandbox mode before you release it on your live e-commerce website. To sign up for a test account please sign up on our [Developer Portal](https://developer.fortis.tech/users/register). = How do I disable rate limiting for local testing? = Rate limiting is enabled by default. For local development only, you can disable rate limits by adding the following to your `wp-config.php`: define( 'WP_DEBUG', true ); define( 'FORTIS_DISABLE_RATE_LIMITS', true ); Both constants must be set to true. This dual-requirement prevents accidental production bypass. Do not enable these settings in production. = How is the User API Key encrypted? = Newly saved User API Keys use versioned, authenticated encryption with a secret independent of your WordPress `AUTH_KEY`/`AUTH_SALT` values. Readable older keys are migrated automatically when used. Legacy keys whose original WordPress salts have already been lost must be re-entered. By default the encryption secret is stored in the options table alongside the encrypted keys. This improves reliability during salt rotation but does not protect API keys from a database-only compromise: someone with a database dump can decrypt them. To keep new encryption key material outside the database, define it in `wp-config.php`: define( 'FORTIS_ENCRYPTION_SECRET', 'a long random string unique to your site' ); When you first add this constant, keys encrypted with the existing database secret remain readable and are re-encrypted with the configured secret when used. Re-save both sandbox and production API Keys and verify both environments before removing the old `woocommerce_fortis_encryption_secret` option. Defining the constant alone does not remove that option or migrate unused keys. Protect and back up the configured secret; do not replace or remove it without first migrating all keys. Existing database backups may still contain the old secret and keys. = Does this require an SSL certificate? = Yes! An SSL certificate must be installed on your site to use Fortis. = Where can I find documentation? = For help setting up and configuring the Fortis plugin please refer to our [installation guide](https://docs.fortispay.com/merchants/woocommerce-new/plugin-installation) and [setup guide](https://docs.fortispay.com/merchants/woocommerce-new/plugin-setup). = Where can I get support? = If you have any questions please send an email to devsupport@fortispay.com. == Screenshots == 1. WooCommerce Checkout Page with Credit Card 2. WooCommerce Checkout Page with Credit Card and ACH 3. WooCommerce Admin Fortis Configuration Page 4. WooCommerce Admin Fortis Appearance Configuration Page == Third Party services == https://api.sandbox.fortis.tech https://api.fortis.tech https://js.sandbox.fortis.tech/commercejs-v1.0.0.min.js == Service Terms == https://fortispay.com/fortisplatform-serviceagreement/ == Privacy Policy == https://fortispay.com/privacy-policy/ == Changelog == = 1.3.5 - 2026-11-19 = * Security updates and hardening. * Fixed the gateway not working when Fortis issues a User API Key, User ID, Product ID or Location ID of 32 to 35 characters. Any plausible Fortis credential is now accepted. * Fixed stored API key encryption so a salt change or a failed save no longer clears the key. * Fixed the Fortis gateway disappearing from checkout on sites that use a persistent object cache. * Fixed block checkout sessions, the card form, wallet buttons, and the form coming back after an address or shipping change. * Fixed a declined saved-card payment emptying the cart, and the checkout using the previous order's amount. * Fixed ACH settlement not completing the order, and the ACH refund note not showing. * Fixed Apple Pay domain verification when the site has no /.well-known/ folder, and the connection-timeout message staying after the card form has loaded. * Fixed a PHP warning on saved-card payments, and a server error on guest checkout. * Fixed shoppers being unable to pay again on the classic checkout after a declined card. * Fixed the block checkout card form being redrawn while a payment was being made, including during a 3-D Secure challenge. * Fixed saved-card surcharges being calculated from the shipping postcode instead of the billing postcode. * Fixed Complete Auth being sent to Fortis more than once when its answer was slow. * Improved handling of payments that Fortis approves when the store cannot complete the order. * Fixed ACH orders staying on hold after the bank debit settles. * Fixed block checkout orders losing tax, so the amount charged matches the order. * Fixed a blank page on the classic checkout when paying again after a declined card with the block checkout also open. * Fixed a product removed from the cart coming back while the card form was loading. * Fixed a coupon applied while the classic card form was loading being charged at the old total. * Saved cards and bank accounts are now checked against the order total before they are charged. = 1.3.4 - 2026-10-06 = * Restricted the Complete Auth success notice to the individual order details page. = 1.3.3 - 2026-09-09 = * Fixed a bug where the Complete Auth button was not displaying in the order row actions for authorized transactions on non-HPOS sites. * Fixed payment verification failures during sandbox checkout caused by transaction description field mismatches between WooCommerce and Fortis on some sites. * Resolved checkout flow interruptions where some sites would stall without redirecting to Fortis Pay gateway. * Fixed shipping address field population and validation issues preventing proper address data submission on some configurations. = 1.3.2 - 2026-06-17 = * Security improvements and vulnerability fixes. * Added server-side cart validation to block payment token generation with empty carts. * Added autofill detection for Safari/iPhone: polling-based detection now triggers checkout update when browser autofill populates multiple fields simultaneously (classic and blocks checkout). * Fixed successful captures marked as failed on some configurations. * Fixed shipping field population logic for postcode and state fields. * Fixed billing data not being populated from customer session for tokenized payments in blocks checkout. * Added short-term caching for surcharge lookups to reduce redundant API calls during checkout. * Minor bug fixes and code improvements. = 1.3.1 - 2026-04-20 = * Surcharge subtotal now correctly accounts for discounts and coupons in blocks checkout. * Prevented classic checkout form from rendering during blocks checkout flow. * Checkout JS now uses dynamic ajaxUrl for better compatibility with sites in subdirectories. * Saved-card surcharge recalculation now reacts to cart total changes instead of relying on individual DOM event listeners. * Important security updates. = 1.3.0 - 2026-02-19 = * Removed the phone number requirement from checkout, allowing orders to be completed without it. * Allowed shipping/billing addresses of any length. * Resolved issue where the Terms & Conditions acceptance error message persisted after acceptance. * Enhanced ACH payment reliability by adding extra validation for webhooks. * Updated the plugin to meet the latest WordPress coding standards. = 1.2.0 - 2025-07-12 = * Added real-time declined payment error messages for customers. * Introduce Surcharges. * Load Commerce.js source script according to the Test Mode setting. * Minor bug fixes. = 1.1.2 - 2025-04-22 = * Addressed bug fixes and security improvements. = 1.1.1 - 2025-01-30 = * Resolved compatibility issue with WooCommerce Blocks on sites hosted in subdirectories, ensuring proper AJAX request handling. * Updated the order status flow for pending ACH payments, changing it from “Pending Payment” to “On Hold”. = 1.1.0 - 2024-11-22 = * Support for capturing authorization-only transactions. * Resolved an issue where the payment total due did not include the shipping amount on the classic checkout page. * Verified compatibility with WordPress 6.7 and WooCommerce 9.4.1. = 1.0.8 - 2024-09-22 = * Tested on WordPress 6.6.2 and WooCommerce 9.3.2 * Corrected plugin slug on text domains = 1.0.7 - 2024-07-15 = * Tested on WordPress 6.5.5 and WooCommerce 9.1.1 * Apple Pay and Google Pay support * Code quality improvements = 1.0.6 - 2024-05-21 = * Tested on WordPress 6.5.3 and WooCommerce 8.8.3. * Code quality improvements. = 1.0.5 - 2024-02-21 = * Improve compatibility with WooCommerce Blocks. * Code quality improvements. * Tested on WordPress 6.4.2 and WooCommerce 8.5.1. * Fix refund compatibility when HPOS is enabled. * ACH reliability improvements. * ACH refunds feature added. * Add option to enable/disable the agreement checkbox. = 1.0.4 - 2023-10-05 = * Fix issue adding Tokenized card using 'Add Payment Method' from 'My Account'. * Test on WooCommerce 8.1.1. = 1.0.3 - 2023-09-15 = * Load elements iFrame on checkout after billing and shipping address is entered. * Add support for High Performance order storage. * Test on WooCommerce 8.1.0 and WordPress 6.3.1. = 1.0.2 - 2023-07-31 = * Improve billing and shipping detail compatibility. = 1.0.1 - 2023-07-26 = * Bug fixes and improvements. = 1.0.0 - 2022-10-06 = * Initial release.