trust-payments-hosted-payment-pages-integration
Last commit date
Firebase
1 month ago
admin
1 month ago
assets
1 month ago
i18n
1 month ago
includes
1 month ago
templates
1 month ago
vendor
1 month ago
CHANGELOG.md
1 month ago
README.md
1 month ago
composer.json
1 month ago
composer.lock
1 month ago
readme.txt
1 month ago
woocommerce-securetrading-gateway.php
1 month ago
readme.txt
266 lines
| 1 | === Trust Payments Gateway for WooCommerce === |
| 2 | Contributors: magenestjsc, trustpayments |
| 3 | Tags: Trust payment Gateway, Credit card, Apple pay, Google pay, Wallet |
| 4 | Requires at least: 4.7 |
| 5 | Tested up to: 6.9.1 |
| 6 | Requires PHP: 8.1.20 |
| 7 | Stable tag: 2.1.2 |
| 8 | License: GPLv3 or later |
| 9 | License URI: http://www.gnu.org/licenses/gpl-3.0.html |
| 10 | |
| 11 | This plugin offers a simple and easy to implement method for merchants to add e-payment capabilities to their WooCommerce online commerce setup. |
| 12 | |
| 13 | == Description == |
| 14 | Easily add payment capabilities to your ecommerce website: |
| 15 | |
| 16 | * Build a seamless, fully customised online payment experience with or without any redirects (hosted payment page or JavaScript plug-in available) |
| 17 | * Accept multiple payment types - credit/debit cards, Apple Pay and Google Pay. |
| 18 | * Easily process Mail Order Telephone Order (MOTO) transactions through the admin panel. |
| 19 | * The Trust Payments extension can integrate with multiple APIs to facilitate typical back-office functions such as transaction updates and refunds. |
| 20 | |
| 21 | == Features == |
| 22 | With Trust Payments, merchants can: |
| 23 | |
| 24 | * Accept all major payment cards (Visa, Mastercard, Amex, Diners/Discover) |
| 25 | * Alternative payment methods supported |
| 26 | * Offer recurring subscriptions |
| 27 | * Feature the gateway on your existing website by using a JavaScript Library integration |
| 28 | * Process payments securely on dedicated HTTPS server hosted by Trust Payments |
| 29 | * Reduce your level of PCI DSS compliance to the lowest possible level by not handling sensitive payment data |
| 30 | * Benefit from the Saved Cards feature, returning customers can save their card details for faster transactions in the future |
| 31 | * Customise your checkout page to reflect your brand and maintain great customer experience |
| 32 | * Accept a large variety of currencies and settle in 15 of these |
| 33 | * Deploy other new payment methods quickly with minimal configuration needed |
| 34 | * View and manage all transactions using our online portal including a Virtual Terminal for transactions not processed in-person |
| 35 | * Supports multiple languages for both the hosted payment and API flow. For further information on localisation please see https://help.trustpayments.com/hc/en-us/articles/4402728226321-Localisation |
| 36 | |
| 37 | == Installation == |
| 38 | = Using the WordPress Dashboard = |
| 39 | |
| 40 | **Please note: This plugin requires WooCommerce to work. Please install WooCommerce before proceeding.** |
| 41 | 1. Navigate to Plugins -> Add New |
| 42 | 2. Use the search field on the top right and enter "Trust Payments Gateway for WooCommerce" |
| 43 | 3. Click the "Install Now" button to install the plugin |
| 44 | 4. Click the "Activate" button or navigate to Plugins -> Installed Plugins -> Find the "Trust Payments Gateway for WooCommerce" plugin in the list and click "Activate" |
| 45 | 5. Next, you are ready to configure the plugin with your unique account details provided by our Support team |
| 46 | 6. (Optional) If you want to support recurring subscriptions you will also need to download and install the WooCommerce subscription engine |
| 47 | |
| 48 | |
| 49 | = Manual installation = |
| 50 | |
| 51 | Manual installation method requires downloading the WooCommerce plugin and uploading it to your web server via your favorite FTP application. The WordPress codex contains [instructions on how to do this here](https://wordpress.org/support/article/managing-plugins/). |
| 52 | |
| 53 | = Updating = |
| 54 | |
| 55 | Automatic updates should work smoothly, but we still recommend you backup your site. |
| 56 | |
| 57 | If you encounter issues with the shop/category pages after an update, flush the permalinks by going to WordPress > Settings > Permalinks and hitting Save. That should return things to normal. |
| 58 | |
| 59 | == Screenshots == |
| 60 | |
| 61 | 1. Additional payments/wallets |
| 62 | 2. Hosted Trust Payments checkout page |
| 63 | 3. Hosted checkout with an Iframe |
| 64 | 4. Embedded payment form on checkout page with wallets |
| 65 | |
| 66 | |
| 67 | == Frequently Asked Questions == |
| 68 | |
| 69 | = Where can I get support? = |
| 70 | If you get stuck, you can contact us [here](https://www.trustpayments.com/contact-us/) |
| 71 | |
| 72 | = How our service works? = |
| 73 | Find out more about [our services](https://www.trustpayments.com/) |
| 74 | |
| 75 | = What are our Terms of Use? = |
| 76 | Please follow our terms of use at [Trust Payments - Terms of Use](https://www.trustpayments.com/legal-terms-of-use/) |
| 77 | |
| 78 | = Where can I find the user guide of the WooCommerce Trust Payments Gateway plugin? = |
| 79 | You can find more information on the WooCommerce Trust Payments plugin [here](https://help.trustpayments.com/hc/en-us/sections/9682549422353-WooCommerce-using-Payment-Pages) |
| 80 | |
| 81 | = Why am I getting an 'Invalid details' message on my page? = |
| 82 | Please ensure you have correctly entered in your Webservices details into the plugin settings. If you are still experiencing this issue, please contact our support team to get this checked. |
| 83 | |
| 84 | = How can I offer recurring subscriptions? = |
| 85 | Firstly you will need to install the WooCommerce subscription engine [here](https://woo.com/products/woocommerce-subscriptions/?quid=92aa6bb884a316a4a8f03fe0747c1486) to your WordPress setup, create an account with Trust Payments and confirm with your acquirer that they support recurring, enable the plugin and provide your details within the configuration page, setup a recurring product and you should be all set. Trust Payments provide the gateway and can be your acquirer. |
| 86 | |
| 87 | = What is an acquirer? = |
| 88 | An acquirer is licensed to process and settle payments by shoppers on behalf of its merchants. Trust Payments is a regulated financial institution and international payment processor which allows us to do this. |
| 89 | |
| 90 | = I am using the hosted checkout flow and I want to support wallets, how can I do that? = |
| 91 | Please contact our support team asking them to enable wallets, and include your site reference in the request. Please note that some wallets aren't supported in an Iframe, if you are experiencing this, please disable "Use Iframe" in the plugin settings. |
| 92 | |
| 93 | = Do I need to setup a Url Notification on my WooCommerce setup? = |
| 94 | We strongly recommend you using URL Notifications with your WooCommerce setup to correctly update the order after payment has been completed. The plugin will work with URL notifications not enabled but if the customer experiences any browser issues, this may cause the order to not update correctly. |
| 95 | |
| 96 | = I have enabled "Url Notification" but my orders are not updating? = |
| 97 | Please ensure that you have reached out to our support team asking them to setup a URL Notification on your site reference, more information can be found [here](https://help.trustpayments.com/hc/en-us/articles/19827934081809-Being-written-Notifications-for-WooCommerce). |
| 98 | Also ensure that our IP's have been whitelisted or any restrictions have been removed, [EU platform](https://webapp.securetrading.net/ips.html). If you are still experiencing this problem, please contact our support team. |
| 99 | |
| 100 | = How do I add Apple Pay and Google Pay? = |
| 101 | If you are using our hosted payment pages, this should be enabled for you already when you open an account with Trust Payments. |
| 102 | |
| 103 | If you are using our API, you will need to enable this within your integration. More information can be found [here](https://help.trustpayments.com/hc/en-us/articles/4413290345361-Getting-started-with-WooCommerce) |
| 104 | |
| 105 | = Why are my payments soft declining? = |
| 106 | Please check that the option "3D Secure" is enabled in the plugin settings. |
| 107 | |
| 108 | = Why am I getting an error "invalid request type" on the payment pages? = |
| 109 | Please reach out to the support team to confirm that your site reference is configured correctly. |
| 110 | |
| 111 | = I am using the API flow why is the Pay button greyed out, when attempting to perform a production payment? = |
| 112 | Check that the test mode setting is unticked in your plugin configuration. |
| 113 | |
| 114 | |
| 115 | == Changelog == |
| 116 | ### version 2.1.2 |
| 117 | - Added support for using newer STPP PHP JSON Library (https://github.com/SecureTrading/PHP-API/tree/4.0.9) |
| 118 | |
| 119 | ### version 2.1.1 |
| 120 | - Tested compatibility with WooCommerce version 10.5.3 |
| 121 | - Tested compatibility with WordPress version 6.9.1 |
| 122 | - Tested compatibility with PHP 8.3.19 |
| 123 | - WTP-230 Refactored webhook implementation to eliminate Transaction queries, utilising data directly from the gateway URL notification instead |
| 124 | - WTP-231 Modified paymentFormValidityChange callback to initialise within the paymentInitCompleted event from st.js. This ensures the field is added only after the Trust Payments iframe has been successfully mounted to the DOM, rendering the solution independent of theme template overrides |
| 125 | - WTP-233 Enhanced submitCallback implementation to validate JWT tokens and update orders directly using the verified payload |
| 126 | - WTP-234 Refined process_payment() functionality to execute exclusively within front-end context |
| 127 | - WTP-228 Resolved invalid field error occurring within the payment pages flow |
| 128 | - WTP-226 Updated STJS initialisation logic to ensure form-id is correctly set during the API checkout flow |
| 129 | - Implemented action for Applepay to resolve status failures when order creation fails, preventing payment processing from proceeding |
| 130 | - Resolved an issue where a declined payment followed by a successful payment was not updating the order status correctly on the hosted pages |
| 131 | - Resolved an issue preventing payment retry attempts on orders with "Failed" status on the hosted pages |
| 132 | |
| 133 | |
| 134 | ### version 2.1.0 |
| 135 | - Tested compatibility with WooCommerce version 10.4.3 |
| 136 | - Enhanced card animation functionality for the API flow |
| 137 | - Implemented guest checkout support for Apple Pay payment method |
| 138 | - Introduced onPaymentValidity callback support to provide additional validation and prevent unnecessary order creation |
| 139 | - Added 'Supported Card Types' feature for Apple Pay, enabling merchants to restrict processing of either credit or debit cards |
| 140 | - Implemented compatibility for sites utilising the Bedrock framework |
| 141 | - Enhanced failover support for order updates, allowing both webhooks and callbacks to be processed and accepted |
| 142 | - Added decline notifications to the HPP flow to update order status and append order notes |
| 143 | - Optimised Order Payment page by implementing minified JavaScript files to improve performance |
| 144 | - Enhanced Apple Pay configuration to utilise onPaymentAuthorize feature for improved order creation flow management |
| 145 | - Refined styling on JavaScript payment input frames |
| 146 | - Updated credentials-on-file flagging to enable merchants to perform MIT (Merchant Initiated Transactions) |
| 147 | - Modified HPP flow to use shortcode functionality, allowing merchants to customise pages |
| 148 | - Improved error logging for enhanced reporting when issues occur |
| 149 | - Resolved issue where orders were not updated to 'Failed' status when a decline occurred |
| 150 | - Resolved issue where HPP configuration would take precedence over API configuration when both were enabled and attempting to utilise wallet functionality |
| 151 | - Resolved character encoding issue when performing MOTO payments using the API flow |
| 152 | - Resolved issue where Google Pay button would disappear when changing payment methods on the checkout page |
| 153 | - Removed redundant card-info.php file from plugin |
| 154 | |
| 155 | ### version 2.0.1 |
| 156 | - Fixed issue with Guest users performing payments when enforced account creation is enabled |
| 157 | - Added extra error messages to be returned on the checkout to improve customer experience. |
| 158 | |
| 159 | |
| 160 | ### version 2.0.0 |
| 161 | - Added compatibility for WooCommerce version v9.7.1 |
| 162 | - Fixed security issue |
| 163 | - Fixed issue with Apple Pay not creating correct order in certain cases |
| 164 | - Updated Trust Payments Transaction data to now work with HPOS and WordPress legacy posts storage |
| 165 | - Fixed issue with the Enable Choice Page feature |
| 166 | - Fixed issue with Apple Pay allowing the DPAN to be saved to the customers account |
| 167 | - Changed logic to how the JavaScript and JWT is being initialised on the checkout |
| 168 | - Fixed issue with Pay by bank incorrectly updating the order status for virtual and non-virtual products |
| 169 | - Added links and extra text within the settings of the plugin |
| 170 | - Added Button Text, Button Radius, Button Style, Button Width and Height to Google Pay settings |
| 171 | - Added Button Type to Apple Pay settings |
| 172 | - Fixed issue on ST Transaction page loading too slow |
| 173 | - STJS controlled button takes precedence over the 'place order' button on the checkout for additional validation. |
| 174 | |
| 175 | |
| 176 | ### version 1.1.4 |
| 177 | - Added compatibility for WooCommerce version v9.5.2 |
| 178 | - Added compatibility for Wordpress version v6.7.1 |
| 179 | - Added support for using newer STPP PHP JSON Library (https://github.com/SecureTrading/PHP-API4.0.1) |
| 180 | - Added support for PHP 8.2 |
| 181 | - Added additional feature support for Applepay |
| 182 | - Improvements to notification handling |
| 183 | - Added support for 3 decimal currencies |
| 184 | - Fixed issue with Trustpayments transaction data not shown in order screen for specific flow |
| 185 | |
| 186 | ### version 1.1.3 |
| 187 | - Fixed issue with Applepay not displaying in certain cases. |
| 188 | - Fixed issue with Pay for Order page not working with our payment methods. |
| 189 | - Added supported to WooCommerce plugin "All Products for Woo Subscriptions". |
| 190 | - Prevented JSINIT request from being submitted if the module is disabled. |
| 191 | - Added compatibility for WooCommerce version v9.1.2 |
| 192 | - Added compatibility for Wordpress version v6.5.5 |
| 193 | |
| 194 | ### version 1.1.2 |
| 195 | - Added Account 2 Account (Pay by bank) payment type to the checkout |
| 196 | - Fixed issue with payment options not correctly displaying for "Customer payment page" link |
| 197 | - Fixed PHP warnings |
| 198 | - Added compatibility for WooCommerce v8.5 and v8.6 |
| 199 | - Fixed issue with Apple Pay where the wallet verify would not dispay in certain cases |
| 200 | - Added locale support |
| 201 | |
| 202 | ### version 1.1.1 |
| 203 | - Fixed issue with notifications not being accepting with the hosted checkout flow |
| 204 | - Fixed issue with the API flow where the option wasn't visible to guest users |
| 205 | - Fixed issue with saved cards on the US platform |
| 206 | - Added compatibility for WordPress v6.4.1 |
| 207 | |
| 208 | ### version 1.1.0 |
| 209 | |
| 210 | - Added new checkout flow that utilises the JavaScript library |
| 211 | - Added recurring subscriptions using the WooCommerce subscription engine (for hosted checkout and API) |
| 212 | - Added Google Pay, Apple Pay and PayPal to the checkout |
| 213 | - Added URL notifications in order to improve order status updates |
| 214 | - Updated plugin to support the newest versions of WooCommerce and WordPress |
| 215 | - Added support for PHP 8.1 |
| 216 | - Users can now add a logo to their payment method within the plugin settings |
| 217 | - Fixed iframe redirect issue on hosted checkout which duplicated the page |
| 218 | - Added extra information in the order comments |
| 219 | - Fixed URL notification issue with MOTO transactions |
| 220 | - Updated the flow of saved cards of where now the user does not get redirected to make payment |
| 221 | - Added backwards compatibilty for previous versions |
| 222 | |
| 223 | ### version 1.0.7 |
| 224 | |
| 225 | - Resolved issue with incomplete payments showing as successful |
| 226 | - Declined notification now correctly shown when using a saved card |
| 227 | |
| 228 | ### version 1.0.6 |
| 229 | |
| 230 | - Fixed decline payments to correctly update order status to 'pending payment' |
| 231 | |
| 232 | ### version 1.0.5 |
| 233 | |
| 234 | - Fixed issue with saving card to customers account |
| 235 | |
| 236 | ### version 1.0.4 |
| 237 | |
| 238 | - Dont save card if walletsource=applepay/googlepay |
| 239 | - Add threedquery to accountcheck (saving your card on My account) |
| 240 | - Apdate saved card to use v3 JS library |
| 241 | |
| 242 | ### version 1.0.2 |
| 243 | |
| 244 | - ApplePay address override |
| 245 | - Sending notifications |
| 246 | - Fix: Saving your card in "Payment Method" flags invalid field |
| 247 | - Fix: Incorrect URL redirect |
| 248 | |
| 249 | ### version 1.0.1 |
| 250 | |
| 251 | - Fix: can't save cards when iframe is enabled |
| 252 | - Fix: MOTO + iframe doesn't show success page |
| 253 | - Add address update when using saved card |
| 254 | |
| 255 | |
| 256 | ### version 1.0.0 |
| 257 | |
| 258 | - Integrate your Trust Payments account with the WooCommerce store. |
| 259 | - Allow customers to checkout using credit and debit cards. |
| 260 | - Support of Saved Card functionality, using Tokenisation for security. |
| 261 | - Allows admin to easily track the transaction history. |
| 262 | - Allows logged in customers to pay using credit/debit cards saved on their account. |
| 263 | - Allows logged in customers to manage their saved payment card(s) on the My Account page. |
| 264 | - Allows admin to perform payments from the WooCommerce admin interface (MOTO). |
| 265 | - PayPal, Apple Pay and Visa Checkout are supported. |
| 266 | - First release |