WPPizza – Saferpay Gateway

Description

WPPizza Gateway Saferpay – Gateway for WPPizza

Enables Saferpay Payments for orders using the WordPress WPPIZZA Plugin

Requirements

WPPizza 2.15+, cUrl, php 5.3+
you must (obviously) have a Saferpay account
your Saferpay account must accept your curency as set in WPPizza–>Order Settings
at a minimum you must set your Saferpay account number, Terminal ID, json api credentials to correspond with the settings in your Saferpay account
PHP >5.2. (5.3+ recommended)
test cc numbers can be found here

Setup

install by uploading the zip file in the normal wordpress manner from withing the plugin screen (add new->upload) and activate
go to wppizza->gateways and set options as required

Screenshots

admin panel

3.3
* Added: Allow refunds from within WPPizza order history
* Tweak / Added: Automatically capture payments where possible after authorization (to avoid having to do this manually within Saferpay account)
* Tweak: Updated license handling
* Tweak: Updated .pot/.po/.mo language files
* Dev: Some code tidyup
21st January 2021

3.2
* Fix: re-added missing support for Twint, Alipay, Paydirekt, Unionpay
18th January 2021

3.1
* fix: verify_payment priority was too low/early and did not allow other plugins to add to the order details
* updated saferpay api version to 1.14
* added: support for Twint, Alipay, Paydirekt, Unionpay
* added: .pot file
1st December 2019

3.0.1
* fix: eliminated some possible php notices when used with wppizza v3.x
20th April 2017

3.0
* added: support for wppizza v3.x
24th March 2017

2.1
* updated: added variable action hook priority for gateway_process_payment to work with WP 4.7
* updated: minimum required wppizza version upped to 2.15+
16th December 2016

2.0
* update: updated plugin to use the strongly recommended - and supposedly safer - JSON API as development of the previous API has been discontinued by Saferpay.
* IMPORTANT NOTICE FOR UPGRADES FROM VERSIONS <=1.3.1:
- Older Saferpay Accounts: It is strongly recommended to switch to the JSON API by entering the relevant details in the plugin (your json api credentials can be found in your Saferpay account settings).
- Gateway Settings Verification: Although this should still be compatible and work even with older Saferpay accounts and gateway settings, you *might* have to add some more info into the gateway settings depending on your current Saferpay account. In fact, it is strongly recommended to add your json api credentials for security reasons.
Therefore, if you are updating from an older version (<=1.3.1) of this plugin, please check and re-save your Saferpay gateway settings and do at least one test transaction (Please note that account id's and terminal id's are now split into 2 distinct setting fields). 17th August 20161.3.1
* tweak: updated test account details as previous test account credentials were removed by saferpay
1st August 2016

1.3
* fix: textdomain action hook misnamed and not loaded correctly
* fix: possible erroneous customer redirection after payment
* tweak: increased action hook priority to stop other plugins possible interference before redirecting to payment processor
11th April 2015

1.2
* bugfix: the_content filter directly output the string as opposed to returning it
* bugfix: language po/mo files had the wrong name to be recognised by other multilingual/language plugins
20th January 2015

1.1
* fix: test/live switch was reversed when sending order
10th November 2014

1.0
* Initial Release
10th October 2014