This plugin is implemented to integrate Saferpay Payment methods in WooCommerce. It supports the following payment methods of Saferpay to work with WooCommerce plugin.

• VISA
• MASTERCARD
• MAESTRO
• AMERICAN EXPRESS
• BANCONTACT
• DINERS/DISCOVER
• JCB
• SEPA ELV
• PAYPAL
• TWINT
• IDEAL
• EPRZELEWY
• APPLEPAY
• ALIPAY
• CREDITCARD (SAFERPAY FIELDS)
• KLARNA PAYMENTS
• EPS
• SOFORT
• WL CRYPTO PAYMENTS
• GOOGLEPAY
• POSTFINANCEPAY
• CREDITCARD / DEBITCARD
• GIROPAY
• ACCOUNT TO ACCOUNT
• WECHAT PAY
• BLIK
• CLICKTOPAY

This plugin supports all the features of online payment methods like payment capturing, refunding & cancellation. All these payment operations are done in the WooCommerce backend & will be synced to Saferpay account also.

To install and configure Saferpay plugin in WordPress, the following is required:

• WordPress (upto 6.6.1) and WooCommerce (upto 9.2.0) plugin..
• License for Saferpay
• A valid Saferpay account with at least one active Saferpay terminal through which payments can be carried out.
• API credentials like Terminal ID, Customer ID, JSON Username and JSON Password for the Saferpay Live- and/or Test environment.
• Valid acceptance agreement for payment methods. 

We need to enter the provided test credentials into Saferpay settings:

Menu → Settings →Saferpay Settings

Initially, enable test mode and we need to enter the provided test credentials into Saferpay settings:

Required Data:

• Test-Customer ID
• Test-Terminal ID (eCommerce Terminal).
• Test JSON API username.
• Test JSON API password.

Switch to Saferpay Operation mode to live & we need to enter the provided live credentials into Saferpay settings:

The following data is required

• Live-Customer ID
• Live-Terminal ID
• Live JSON API username
• Live JSON API password

Saferpay Plugin configuration includes two sections

• Saferpay general settings
• Payment method specific settings

Configure general Saferpay settings from Menu → Settings →Saferpay Settings

The following configurations are available in Saferpay basic settings

• Enable Test Mode: It defines the Saferpay Operation mode. If it is enabled, it allows the payment gateway to work in test mode by using test API keys otherwise it will work as live mode. By default, test mode is enabled. 
• Saferpay Licence: Choose the Saferpay licence you own. Saferpay has two licenses:
  • Saferpay eCommerce
    
    • Access to:
      • Payment Page Interface
  • Saferpay Business
    
    • Access to:
      • Payment Page Interface,
      • Transaction Interface
      • Saferpay Fields and more

In case you have Saferpay Business without the corresponding license, the API will throw an error.

• Test API Base URL: These fields already have default values of API base URL.
  E.g.: https://test.saferpay.com/api. Note: Recommended not to change it in ideal case. Changes applicable only if there is an update in base test url from Saferpay side.

• Test Customer ID: Enter your test customer id given by Saferpay while creating a partner account in Saferpay.
• Test Terminal ID: Enter your test terminal id given by the Saferpay.
• Test JSON Username: Enter test JSON username given by the Saferpay
• Test JSON API Password: Enter test JSON API password given by Saferpay. To get JSON API username and password you have to login to Saferpay management interface and go to Settings -> JSON API basic authentication. Please refer https://www.sixpayment-services.com/en/site/e-commerce-developer/integration.html and https://docs.saferpay.com/home/integration-guide/introduction terms for more information
• E-Mails: Saferpay will send an email to the address specified in this field. You can add multiple emails separated by a comma. It is not a mandatory field. This is applicable only for PaymentPage interface.
• Force Authentication: Recommended for high-risk businesses (Jewelry, Electronics, etc.) to stick to the highest level of security. Else you can have it as “No, I don’t want extra level of authentication.”
• Liability Shift Behavior: This field determines how to handle the transactions if a fraudulent card is used on the website. When we use this functionality, the liability shifts to the authorizing bank and the store owner receives no claim for any chargeback. It has two options:
  • Option A:” If no liability shift has been granted transaction will be on-hold, merchant can capture or cancel transaction”. Here order placed via fraudulent card will be on-hold and merchant can capture or cancel transaction accordingly.
  • Option B: If no liability shift has been granted transactions will be auto cancelled. Here order placed via fraudulent card will be cancelled.
  •  Option C: All transactions are captured automatically, including those without a granted liability shift. 
• Auto Configure: Added a auto configure button to enable the payment methods in one click.
• Saferpay Fields Access Token: Generated automatically with the API URL. 
• Saferpay Fields API-URL.
• JS-Library-URL: Here enter JS library URL. 
• Payment Page CSS URL: Enter a valid CSS URL which is included in the payment page. This file must be hosted on an SSL/TLS secured web server (the URL must start with https://) Example: https://merchanthost/merchant.css. Refer https://saferpay.github.io/sndbx/CssiFrame.html for more details.
• Description of the order: A human readable description provided by the merchant that will be displayed in Payment Page.
• Payment Page Configuration Name: Here you can define the payment page configuration name. The configuration can be created from Safer pay Backoffice ('Settings > Payment Page Configuration'). If the configuration is not found by in Safer Pay (setting / Backoffice); the default configuration will be used.

• If you are using live mode enter Live Customer ID, Live Terminal ID, Live JSON Username and Live JSON API password given by Saferpay while creating a partner account in Saferpay. To get access information for live environment you have to request an offer here. To get access information to live account please follow this link.
• Payment Page Theme: Choose the theme to customize the appearance of Saferpay payment pages. As per default a lightweight responsive styling will be applied. Three types of settings are available:
  • Default lightweight responsive theme
  • Six
  • No Theme 

• Allow save card in user profile: This allows merchant to enable/disable save card option in user profile. If it is enabled, allows your customer to save the credit card information in ‘My account ‘and to reuse the saved information for future payments. If it is disabled, it will hide the ‘Saved Cards’ menu as well from the ‘My account’
• Force access token generation: This allows merchant to enable/disable Access-token generation. If it is enabled, "Access-token" is generated automatically. Also, you need the CustomerId and TerminalId to be configured for this to work. The generated token will overwrite the current token (if present), for the given environment configured. If it is not enabled, you need to create access-token manually from Saferpay backoffice. This is explained in pg.no. 26 under SAFERPAY (HOSTED) FIELDS SETTINGS (SAFERPAY CREDIT CARD).
• Is User required to re-enter his CVC, when using a saved card: If we choose “Yes, Re-enter CVC “user will be prompted to enter CVC again during checkout while using saved card for their transaction. If “No need to re-enter CVC” chosen user will not be prompted to enter CVC during checkout while using saved card for their transaction

• My Account Add Card template: Here we can choose templates for adding card details in My Account Saved Cards section for users. Four sample templates are available.
  Once you have configured Saferpay general settings, review all the settings carefully. If everything is fine, click Save Changes button.
• Enable Fraud Prevention: This protects merchants from fraudulent online transactions. Based on analysis a fraud prevention status is assigned to each transaction. Possible values: BLOCKED, APPROVED and MANUAL_REVIEW. If set to "YES", Please enable Fraud Intelligence module on your Saferpay account.

Saferpay payment method specific configuration is explained in detail below:

• Enable/Disable: Here you can set the visibility of installed payment method during checkout.
• Title: Here you can set title of payment method which is displayed in shop during checkout.
• Description: Here you can set a description of payment method which is displayed in shop during checkout.
• Minimal Order Total: Here you can set availability of payment method according to minimal order total. If it is set to zero payment method will be always available during checkout irrespective of order total.
• Maximal Order Total: Here you can set availability of payment method according to maximal order total. If it is set to zero payment method will be always available during checkout.

• Allowed Countries: If you wish to accept payment from specific countries, you can select the countries. Multiple countries can be selected by Press Ctrl key. If there is no specification leave it.
• Allowed currency: Choose the currencies that can be processed with this payment. Select allowed currency if any specification else leave it.
• Customer Address: Here you can set customer address sent to SaferpayIf it is set to No, Customer address won’t be sent to Saferpay. If it is set to Send delivery address, Customer delivery address would be sent to Saferpay. If it is set to Send billing address, Customer billing address would be sent to Saferpay. If it is set to Send both shipping and billing address, Customer’s both billing and shipping address would be sent to Saferpay.
• Pre-Authorizations: It extends the validity of an authorization up to 30 days. If it is set to YES, only Manual Capture option will be possible under Capturing settings. 

• Customer Confirmation Email: Here you can set whether Saferpay send confirmation email to customer. It is only applicable if the customer is redirected to Saferpay.
• Card Form – Holder Name: If it is set to None, Saferpay should not display a field requesting the card holder name in payment interface. If it is set to mandatory, Saferpay should display a field requesting the card holder name in payment interface.
• Capturing: Here you can set capturing mode. If it is set as Manual Capture amount is only reserved and you should capture it manually through WordPress back-end. If it is set as Auto Capture amount is captured automatically.

• Authorization Method: Here you can set authorization method used for payment processing. Two options are available under these settings.
  • Payment Page – During the order processing the user will be redirected from the WooCommerce shop to the Saferpay payment gateway interface to process the payment. On successful completion of the payment the user will be redirected back to the WooCommerce shop. The Saferpay Payment Page Interface is intended for a simplified and universal integration of the payment process by using the PaymentPage form. The Saferpay PaymentPage can be used both with a Saferpay eCommerce license and with a Saferpay business license. All Saferpay supported payment methods can be processes with the Payment Page Interface.
  • Transaction Interface (Widget Authorization) - During the order processing the user is served with Saferpay payment forms in a pop up within the WooCommerce shop. The Transaction Interface is an extension to PaymentPage Interface. It offers the Hosted Entry Form (HEF) to process card payments seamlessly. This interface can also be used in combination with Secure Card Data to store/tokenize payment data during the payment process. The Transaction Interface is only for holders of a business licence on the live system.

• Is Save Card Available? Here admin can set Active or Inactive status. By enabling this, the customer can register cards and use it for future payments. Card details will be stored in Saferpay. This option is available only for Widget Authorisation method. Once you have configured Saferpay payment method, review all the settings carefully. If everything is fine, click Save changes button.

 The following links are helpful while configuring each payment methods

• Credit and Debit Cards – Refer:
  • Link - https://docs.saferpay.com/home/integration-guide/payment-methods/mastercard
  • Link - https://docs.saferpay.com/home/integration-guide/payment-methods/maestro
  • Link - https://docs.saferpay.com/home/integration-guide/payment-methods/visa-and-vpay
  • Link - https://docs.saferpay.com/home/integration-guide/payment-methods/americanexpress
  • Link - https://docs.saferpay.com/home/integration-guide/payment-methods/diners-anddiscover
  • Link - https://docs.saferpay.com/home/integration-guide/payment-methods/jcb
  • Link - https://docs.saferpay.com/home/integration-guide/payment-methods/swiss-postcardand-postfinance-1
• TWINT – Refer https://docs.saferpay.com/home/integration-guide/paymentmethods/twint
• PayPal - Refer https://docs.saferpay.com/home/integration-guide/paymentmethods/paypal
• SOFORT - SOFORT is a third party means of payment by Klarna Group. Refer https://docs.saferpay.com/home/integration-guide/payment-methods/sofort-by-klarna
• Klarna Payments - Klarna Payments is a 3rd party payment method, that is split into three ways of payment: Pay Now, Pay Later and Slice It/Financing. Refer https://docs.saferpay.com/home/integration-guide/payment-methods/klarnapayments
• eps - Refer https://docs.saferpay.com/home/integration-guide/paymentmethods/eps
• Giropay - Refer https://docs.saferpay.com/home/integration-guide/payment-methods/giropay
• iDeal - Refer https://docs.saferpay.com/home/integration-guide/paymentmethods/ideal
• SEPA ELV - Refer https://docs.saferpay.com/home/integration-guide/paymentmethods/sepa-direct-debit
• ePrzelewy - Refer https://docs.saferpay.com/home/integration-guide/paymentmethods/eprzelewy
• Bancontact - Refer https://docs.saferpay.com/home/integration-guide/paymentmethods/bancontact
• Apple Pay - Refer https://docs.saferpay.com/home/integration-guide/paymentmethods/applepay
• Alipay - Refer https://docs.saferpay.com/home/integration-guide/paymentmethods/untitled-1
• Crypto Payments – Refer https://docs.saferpay.com/home/integrationguide/payment-methods/crypto-payments
• Google Pay - Refer https://docs.saferpay.com/home/integration-guide/payment-methods/applepay
• BLIK – Refer - https://docs.saferpay.com/home/integration-guide/payment-methods/blik
• CLICKTOPAY – Refer - https://docs.saferpay.com/home/integration-guide/payment-methods/click-to-pay

If you want to customize the default design of the Saferpay interface, Saferpay provides the following options:

• CSS-Styling: The CSS styling options can be used over the following methods.
  • Payment page
  • Transaction Interface
  • Alias Insert

• Theme: This parameter let you customize the appearance of the displayed payment pages. By default, a lightweight responsive styling will be enabled. If you don't want any styling, please choose 'NONE'.

Just like Saferpay transactions, you can also manage the Saferpay refund transactions. Saferpay refund will only be available if transactions are captured properly. If transactions are not captured click ‘Capture’ button available in transaction tab, then only Saferpay refund button will be enabled. Manual refund buttons are available all the time. Admin should have to do manual refund and update details in Saferpay back office manually. Refund is also available for orders having completed status.

For Saferpay Refund do the steps mentioned below

• Capture order from backend
• Then click Refund button

• Click on items to be refunded. Refunded amount will be displayed

• After that Click on button available for Refund via Saferpay. Confirmation pops up will be displayed. 

• If we click OK amount will be successfully refunded and order status will be changed to Refunded.

• For themes that support Gutenberg blocks, please ensure to include the checkout block Gutenberg module on the Checkout page for WooCommerce version 8.3.1 and above

• For themes that do not have block compatibility and WooCommerce versions below 8.3.1, please utilize the [woocommerce_checkout] shortcode.

• Recurring SCA challenge for PSD2 Compliance
  Saferpay module is compatible with WooCommerce Subscription plugin. This field is applicable only for orders with subscription products. It ensures the PSD2 compliance of the recurring payments done through Saferpay while WooCommerce Subscription plugin is enabled.
• Recurring supported payment methods.
  If your customer adds any subscription to the cart, only gateway specific payment methods will be available at checkout. Make sure selected payment gateways are properly configured by going to WooCommerce > Settings > Payments.

Saferpay plugin is compatible with the following features of WooCommerce Subscription plugin,

• Subscriptions
• Manual renewal
• Subscription Cancellation
• Subscription Suspension
• Subscription Reactivation
• Subscription Amount Changes
• Subscription Date Changes
• Multiple Subscriptions (Multiple subscription products in same order)

The following Saferpay payment methods are supported for subscription orders.

• VISA
• MASTERCARD
• AMERICAN EXPRESS
• DINERS
• JCB
• GOOGLEPAY
• SEPA ELV
• APPLEPAY
• CREDIT CARD (SAFERPAY FIELDS)
• TWINT – Payment possible only if there is already saved card data available
• POSTFINANCE PAY – Payment possible only if there is already saved card data available

The renewal subscription orders are created through WooCommerce subscriptions cron. A new subscription order is placed when the scheduled time arrives. If the subscription payment fails, then the subscription gets on-hold and future renewal process not works until the subscription status changed to Active. Merchant can cancel the subscription if requires. During this time the customer is notified with an e-mail, for him/her to go through the process again that is, to reactivate subscription (via my-account) by paying the amount. The payment details are saved in the Saferpay and Wordpress backend provides list of child orders associated with each subscription.

• Checkout with zero amount. (e.g. Free trial and zero signup fee) : The actual supported payment methods for this condition are Credit Cards, Twint and Postcard. But we ignored the methods Twint and Postcard because they can do recurring ONLY via Alias and Authorize Direct. While doing the zero payment normally, we are actually saving the card instead of the processing the payment, so it would be difficult to implement it for Twint and Postcard. So currently Credit Cards only supports the zero payment.
• In Apple Pay ‘pay by wallet’ option, it is possible to checkout subscription product with some cards which does not support recurring payments. E.g. Maestro- even if checkout is possible actual subscription and related features may not work here as Maestro does not support recurring payments.
• In Saferpay back-office normally when an auto renewal is triggered, it creates an order as a child of the first order. But the case is different for manual renewal, when a user does the manual renewal through checkout, that order will be created as a completely new order and there won't be a relation between previous orders under the same subscription. But in WordPress each auto and manual renewals will be placed under the initial parent order itself.
• Saferpay WooCommerce Gateway does not support the following features of WooCommerce Subscription plugin.
  • Subscription payment method change
  • Subscription payment method change by customer
  • Subscription payment method change by admin

The Saferpay API itself does not provide any support for payment method change, because they need to re-initiate the whole process to implement this. So we also have some limitations to do this. 

1.19 to 1.23

• Crypto payments integration in the Saferpay Payment Page
• Added Klarna Payments support for Italy and France
• New currencies for SOFORT: PLN, HUF und CZK added
• New logo updated for Bancontact and iDeal payments
• EPS Refunds supported
• Removed Bonus Card payment
• Saferpay Fields Access Token generation via REST API

1.24 to 1.25

• Pre-authorizations for additional brands(amex,diners,jcb)
• SuccessNotifyUrl and FailNotifyUrl in PaymentPage/Initialize.
• WL Crypto Payments refund.
• Added notification URLs in Transaction/Initialize.
• Update - Saferpay fields JS url.
• Klarna Payments: Support for Extended Merchant Data.
• Management API:
  • Only those payment methods that are enabled in Saferpay backoffice are available at webshop backend.
  • New payment logos.

1.26 to 1.31

• Googlepay Integration
• WL Crypto Refund issue fixed.
• Widget Authorization for Googlepay and Applepay
• Auto configure button added in Saferpay settings.
• PLN and GBP currency are having new country restriction added in Sofort Account. Attention required. 

1.32 to 1.38

• Account to Account Integration
• Postfinancepay Integration
• Credit card/ Debit card Integration.
• Removed Masterpass / Unionpay
• Return URL updated.
• EURO currency introduced for Crypto for Belgium and Luxembourg

1.39 to 1.40

• WeChatpay Integration
• Replaced Postfinance Card and Postfinance E Finance with Postfinancepay.
• Removed Bancontact from Savecard
• Removed Payment Page CSS URL and Payment Page Configuration Name