This module adds a Up2pay e-Transactions Payment Gateway to your Installation of WooCommerce.
Up2pay e-Transactions is a Payment Services Provider in Europe, part of the Crédit Agricole Bank.
plugin actions in wordpress:
this plugin offers an admin panel from the order section to the settings of Woocommerce.
it adds payment information to the orders details and changes the status of orders (upon reception of an IPN, see below.) and adds payment means on the checkout page.
This plugin takes information from the order and creates a form containing the details of the payment to be made, including parameters configured in the admin panel of the module that identify the mechant.
The plugin checks for availability of the Up2pay e-Transactions platform, through a call to our servers.
the customer is then presented with a payment page, hosted on the Up2pay e-Transactions Platform (urls above).
The Up2pay e-Transactions Platform sends an Instant Payment Notification (IPN) to the server when the customer actually made the payment, indicating to the merchant the status of the payment.
the plugin generates a url that can catch the IPN call from Up2pay e-Transactions’s server, filtering incoming calls to the Up2pay e-Transactions IP address.
if payment is successfull, then the plugin validates the order though woocommerce.
Upload the entire folder
or through WordPress’s plugin upload/install mecanism.
Activate the plugin through the ‘Plugins’ menu in WordPress
What is the HMAC key in the admin panel for ?
The HMAC key is generated on Up2pay e-Transactions server through your Up2pay e-Transactions back office. it is used to authenticate your calls to Up2pay e-Transactions Server. it is generated on the platform you choose: Production (live) or Pre-Production (test)
My orders are not validated, even though the payment went through ?
The oder paid with Up2pay e-Transactions is only validated upon rectpion of a positive Instant Payment Notification (IPN) this IPN is authenticated with the filter on the IP address, if the IP is somewhow changed, the plugin will give a 500 HTTP error.
Avoid Maintenance mode, or allow Up2pay e-Transactions IP to go through (220.127.116.11,18.104.22.168,22.214.171.124). If the WordPress Installation is in maintenance mode, the Up2pay e-Transactions server will not be able to contact it.
Something is not working for me, how can i get help ?
Contact Up2pay e-Transactions WordPress Support, we will be glad to help you out !
Contributors & Developers
“Up2pay e-Transactions WooCommerce Payment Gateway” is open source software. The following people have contributed to this plugin.Contributors
Interested in development?
-updated compatibility levels declaration
-fixed compatibility with wordpress 5.8.1 (thx glouton)
-fixed test mode switching
-Up2pay branding & Adding many features to the plugin:
-payment mean choice on the woocommerce checkout
-debit upon change of status (when shipping for instance)
-settings is now fully sappable between production and testing:
one can have 2 very different settings for both modes and review settings,
without changing the actual working mode for the website.
Force 3DSv2 for all cards
Add 3DSv2 support
various fixes and alignments
shortening long api names for plugin
fixing Woocommerce active detection mechanism
fixing mcrypt deprecation when goin with php > 7.1.x + translations and adding icon for payment means
Correcting transaction/call mixup and translation of minimal amount label.
adding HTTP/2 compatibility.
Correction for PHP7.2 mcrypt removal: openssl used if no mcrypt present.
Correction for potential HTTP 500 error: thx @.
Correction for network urls, order properties calling.
Correction of url called, to work for mobile.= 0.9.8 =
Correction of minor bugs.
Correction of multisite wordpress bug.
Correction of a potential fatal error on error logging thx @vasyltech!.
Compatibility for folder-based wordpress mono-site.
Added compatibility for folder-based wordpress multi-site.
Removed IPN IP checking
only rely on the $_SERVER data to check for the IP address:
this solves the non reception of the IPN (error 500)
-Missing table now created ok.
-“Syntax error: Unexpected token < ” message when checking out,
-Use of deprecated functions to get pages url: now we use endpoints.
-Informations about the payment on the order detail page, now actually displayed.
-3D Secure status properly rendered
-card numbers appear in the detail
-three time payment IPN properly stored
First stable release