This module is implemented to integrate Saferpay Payment methods in Magento. It supports the following payment methods of Saferpay to work with default Magento 2 checkout. 

• VISA
• MASTERCARD
• MAESTRO
• AMERICAN EXPRESS
• BANCONTACT
• DINERS/DISCOVER
•  JCB
• SEPA ELV
• MYONE
• MASTERPASS
• UNIONPAY
• PAYPAL
• TWINT
• PAYDIREKT
• IDEAL
• EPRZELEWY
• APPLE PAY
• ALIPAY
• CREDITCARD (SAFERPAY FIELDS)
• SOFORT
• GIROPAY
• EPS
• BILLPAY PURCHASE ON RECEIPT
• BILLPAY DIRECT DEBIT
• KLARNA PAYMENTS
• WL CRYPTO PAYMENTS
• GOOGLEPAY 
•  POSTFINANCE PAY
• ACCOUNT-TO-ACCOUNT
• CREDITCARD / DEBITCARD
• WECHATPAY

• CLICK TO PAY

• BLIK

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

To install and configure Saferpay module in Magento, the following is required:

• Magento installation with version between 2.4.0 to 2.4.7 p3
• The license for the Saferpay module.
• 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. 

Saferpay module configuration includes two section

• General configuration
• Payment method specific configuration

• Version : Current Plugin Version
• API Spec Version : Current API Spec version. This gives information about technical features, modifications and enhancements that are integrated 

The following configuration options are available in General section

• Environment: It defines the Saferpay Operation mode. The dropdown will allow merchant to quickly switch between live and test environment. By default, test mode is selected
• Test Customer ID/Live Customer ID
• Test Terminal ID
• Test JSON Username
• Test JSON API Password
• Generate Saferpay Fields access token and url automatically 

• Enter Shop Url

• Test Saferpay Fields Api Key
• Test Saferpay Fields Api URL

           6, 7: if not generated automatically , the details can be obtained from Saferpay backend -> Settings -> Saferpay Field Access Tokens

• Test Saferpay Fields JS URL

           This is the Saferpay Fields Javascript library url. Do not edit this if are unaware of the functionality

• Test Base URL

          These fields already have default values of api base url. Do not edit this if are unaware of the functionality

• Licence: Choose the Saferpay licence you own.

• Liability Shift Behaviour

This field determines how to handle the transactions when Liability Check for card Fails. When using this functionality, the liability shifts to the authorizing bank and the store owner receives no claim for any chargeback if a fraudulent card is used on their website. 

• Force 3D secure authentication during transactions

• Recurring SCA challenge for PSD2 Compliance

Saferpay module is compatible with Amasty recurring module. This field is applicable only for orders with subscription products. It ensures the PSD2 compliance of the recurring payments done through Saferpay while Amasty extension is enabled.

•  Enable Saved Cards Option

Customers can save their card details in customer account if this configuration is enabled. They will get access to tab “Saved cards”.

• Recurring Customer Authentication Email Template

There is a possibility for payment failure due to soft decline of cards during recurring transaction. During such scenarios this template is used to send email to customers notifying them about transaction error.

• Re-enter CVC value when using saved cards for payment

This option is used to provide additional security when the customer uses saved cards for the checkout. While this option is enabled, it asks the cardholder to re-enter his CVC if he uses saved card for checkout, and hence the transaction would be fully secure and PCI compliant

• Merchant email

Email addresses (Merchant email) to which a confirmation email need to be send after successful payment authorizations. (Applicable only for payment page authorization)

• Order Description

• 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

• Payment Page Theme

Choose the theme to customize the appearance of Saferpay payment pages. Per default a lightweight responsive styling will be applied.

• Saferpay Configuration

Saferpay Payment Page configurations is used to configure design and other details inside hosted pages. The configuration can be created from Saferpay Backoffice ('Settings > PaymentPage Configuration'). The configuration marked as 'default' will be used as the standard setting if none

• Enable Log

All the error details regarding a transaction will be logged to custom log if this option is enabled. Refer Log section for more information

• Email Template on cancellation of order

There may be possibilities for cancelling authorized transaction due to failed 3Ds check. During such scenarios this template is used to send email to customers notifying them about payment cancellation.

• GraphQL Support

GraphQL is indispensable for creating Magento PWAs. Saferpay Extension provides GraphQL support so that PWA developers and Mobile app developers can make use of it. This will work for Magento versions from 2.3.3 to 2.4.6 p3 

Individual payment methods which come under Saferpay can be configured from System > Configuration > Sales > Payment Methods section. Not all payment will be in your contract so be careful while enabling payment methods.

Saferpay specific configuration are explained in detail.

• Enabled
  Enable or Disable payment methods
• Title
  The title displayed to the customer on the store front during checkout.
• Description
  Description for the payment
• Payment from Applicable Countries
  By default, it is set to All Allowed Countries.
• Payment from Specific Countries
  If you wish to accept payment from specific countries, you can select the countries in Payment from Specific Countries.
• Accepted Currencies
  Choose the currencies that can be processed with this payment. If no currency is selected payment will not be available even though it is enabled individually.

Some payments like Klarna may have country and currency restrictions. So be careful in choosing countries and ensure that these countries are activated in your Klarna payment settings in saferpay account also.

For Klarna to work properly, currency code should be in-line with country code.

• Authorisation Method
  Authorisation Method defines how the payment method is displayed and processed. Some payments support multiple authorisation methods while others support single.
  • Payment page – During the order processing the user is redirected from the Magento shop to the Saferpay payment gateway to process the payment. On successful completion of the payment the user will be redirected back to the Magento shop. The Saferpay Payment Page Interface is intended for a simplified and universal integration of the payment process by using the PaymentPage payment form. The Saferpay Payment Page 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 - During the order processing the user is served with Saferpay payment forms opened in a lightbox within the Magento shop. The Transaction Interface is an extension to Payment Page 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
  • Saferpay Fields - will be hosted on Saferpay-side and will offer you a level of fflexibility and the possibilities, similar to using your own form. The data is captured by a fully PCI-certified system. 

• Capture Type
  This indicated how payment provider should behave when order is created. There are two options:
  • Autocapture: It will automatically capture the amount in the order.
  • Manual capture: The payment will be authorized, but merchant will have to capture manually form shop Backend
  • In Magento from version 2.4.7-p1 to 2.4.7-p3, manual capture and cancelation of invoices may not function as expected. This is Magento issue identified and the following patches address the solution:
    • Patch for Invoice Cancelation: Addresses issues related to cancelling invoices.
    • Patch for Manual Invoice Capture: Resolves manual invoice capture problems.

• Invoice Generation
  This field determines when to generate invoice for the payments made through Saferpay if the capture type is set to Manual. For automatic Captures invoice will be generated instantly after payment in paid state.

• Send Invoice Email
  If “send invoice” is enabled, invoice email is sent automatically after invoice capture. 

• Pre-Authorize Transaction

When set to true the transaction is processed as pre-authorization otherwise as final authorization. If pre-authorisation is selected, the capture of the payment is prevented even though the capture type is “Autocapture “. 

• Show Payment Icon

When enabled, the payment brand icon will be shown in checkout page and order email.

• Display Payment ID

This field determines whether transaction Id of the payment should be displayed in order confirmation page and order email. 

• Send Customer Address

This option will send customer address to Saferpay. 

• Display card holder name on Saferpay

This parameter let you customize the holder name field on the card entry form. Per default, a mandatory holder name field is shown.

• Register alias and use during checkout

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 Transaction Interface Authorisation method. 

• Send Customer confirmation email from Saferpay

Confirmation email will be sent to the customer after successful authorizations from Saferpay (Applicable only for payment page authorization)

• Minimum Order Total

Using this field merchant can set a minimum order limit. If the grand total of the order is less than the Minimum Order Total value, the payment cannot be processed through the payment method.

• Maximum Order Total

You can specify the maximum amount for the transaction that can be processed through this payment method.

•  Sort Order

This option is for sorting the payment methods to display in the checkout page.

Once you have configured Saferpay payment method, review all the settings carefully. If everything is fine, click Save Config button at the top right corner. 

• Payment Brands

This configuration is available only for Credit Card and Apple Pay payments. It enables the merchant to choose the payment brands which will be accepted by these payments.By default, all brands are selected.

The selected brands will be accepted only if it supports the currency opted for Saferpay transactions. 

• Saferpay Fields CSS URL

• Pre-Select issuer bank account

• CSS-Styling

• Theme

•  Payment Page Configuration

Multipart capture can be used over following methods

• Visa
• Mastercard
• Maestro
• PayPal 
•  American Express
• Diners
•  JCB
• Klarna
• PostFinance Pay

Customer can add below types of payment means to customer account

• Cards
• Twint – Saved card data is used only for recurring payments
• Postfinace - Saved card data is used only for recurring payments

The following Saferpay payment methods are supported for subscription orders.

• VISA
• MASTERCARD
• AMERICAN EXPRESS
• DINERS
•  JCB
• BONUS CARD
• MYONE
• CREDIT CARD (SAFERPAY FIELDS)
• Apple Pay
• Google Pay
• Creditcard / Debitcard
• Postfinance Pay – Payment possible only if saved card data available
• Twint – Payment possible only if saved card data available  

 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 

1.23 to 1.24

• Implementation of refunds of crypto payments
• Soft decline handling of recurring transaction
• Management API: Added configuration in Magento backend to create Saferpay Fields access tokens via API
• Added notification URLs in Transaction/Initialize
• Support for Fraud intelligence business
• Pre-authorizations and multipart-captures for additional brands (American Express, Diners Club International / Discover Card, JCB) 
• Klarna Payments: Support for extended merchant data
• SuccessNotifyUrl and FailNotifyUrl in PaymentPage/Initialize
• Supports additional payment page language (Bulgarian and Icelandic)
• Saferpay Fields improvements

1.25 to 1.28

• Integrated Google Pay payment method in Payment page and Transaction interface
• Integrated Apple Pay in Transaction interface
• Added option to save and use alias card for Google Pay payment in Transaction Interface
• Added option to save and use alias card for Apple Pay payment in Transaction Interface
• Integrated Fraud Intelligence Device Fingerprinting for more accurate fraud check
• Showed Markup and ExchangeRate values of DCC in backend order view section
• Showed Paypal customer email data in backend order view section
• Prevent API-refunds exceeding captured amount
• Management API: Added validation check to each payment while enabling saferpay payment method from Magento backend. This checks whether the
  specific payment is activated in saferpay terminal or not
• Management API: Retrieved logo URLs of available Payment Methods and displayed in the checkout payment section. 

1.29 to 1.30

• Klarna Payments improvements payments
• iDEAL issuer preselection change- remove Handelsbanken from the list of iDEAL issuers

Recurring

• Integrated Apple Pay and Google Pay payment methods for recurring payments
• Integrated Twint and Postfinace cards for recurring payments via Direct authorization. Payment possible only if saved card data is available in customer account
• Removed Maestro and Bancontact payments from recurring payments 

1.31 to 1.34

• "Auto Configure" option is added in Saferpay General Configuration to automatically configure available payments.
• Changes in Return url for Payment page, Transaction page, and Saferpay field transactions.
• Added NotifyUrl to the SecureCardData/AliasInsert request.
• Removed Fraud Intelligence changes: DeviceFingerprint was removed from all versions.
• Removed UNIONPAY as valid value from field PaymentMethods in SecureCardData/AliasInsert requests. 

1.35

• Add CARD as value from field PaymentMethod in PaymentPage/Initialize requests, created as new payment method "Creditcard/Debitcard"
• Added CustomerLicense method to Saferpay Management API
• Removed CustomerLicenseConfiguration method from Saferpay Management API.
• Added container notification to Transaction/Initialize and Transaction/AuthorizeReference.
• API parameter was added for DCC emails to be sent if DCC was used.

Recurring

• enabled new payment method "Creditcard/Debitcard” for recurring payments.

1.36 to 1.38

• Worldline Crypto Payments in EUR - supports the payment method Worldline Crypto Payments in EUR for Belgium and Luxembourg. 
• Removed UNIONPAY as valid value from field Payment Methods in Transaction/Initialize requests.
• Added new payment method PostFinance Pay, which will be the successor of PostFinance E-Finance & Card.
• Updated to newest version of the Prezelewy24, removed cancellation feature.
• Updated to new version of giropay.
• Added new the payment method ACCOUNTTOACCOUNT

• Plugin version upgraded to 1.2.2
• Removed Extra level authentication configuration and replaced it with Force SCA feature configuration
• Transaction overview section will display “3Ds Authentication Type  “ if 3ds data available
• Removed manual capture option from Capture type for ePrzelewy payment
• Removed Refund support for Crypto payments
• Parameter ‘HolderName’ is set to "mandatory" if configuration 'Display cardholder name on saferpay’ set to ‘Yes’ in the Magento backend payment method settings
• Saferpay module is made compatible with Magento 2.4.6-p4 version
• Saferpay recurring module is made compatible with Amasty Subscriptions & Recurring Payments Version 2.0.0.

1.39 to 1.40

• Added new payment method WeChatPay.
• Enabled PostfinancePay, for Recurring Payments.
• POSTFINANCE and POSTCARD have been removed as valid values for PaymentMethods in PaymentPage/Initialize requests.
• BANCONTACT has been removed as a valid value for PaymentMethods in Alias/Insert.
• The Styling container has been removed from PaymentPage/Initialize in all API versions.
• PaymentPage/Assert can now be called up to 120 hours for pending transactions, extending from the previous limit of 96 hours.

Improvements

• Plugin version upgraded to 1.2.3
• Saferpay module is made compatible with Magento 2.4.7 p1 version
• Saferpay recurring module is now compatible with Amasty Subscriptions & Recurring Payments Version 2.0.0.
• Added Save Card Alias Fields for CreditCard.
• Added option to capture the invoice that got interrupted due to Saferpay error..
• Compatible with Hyva theme Version1.3 and Hyva checkout Version 1.1.

1.41 to 1.43

• Added additional info about the used ISO-standard and applied restrictions to field LanguageCode of the Payer container and SecureCardData/AliasInsert requests
• Added new payment method Blik.
• Added new payment method Click to Pay.

Improvements

• Plugin version upgraded to 1.2.4
• Saferpay module is made compatible with Magento 2.4.7 p3 version
• Saferpay recurring module is now compatible with Amasty Subscriptions & Recurring Payments Version 2.0.0, 2.1.0 & 2.2.0
• GraphQL support for Magento versions from 2.4.0 to 2.4.7 p3
• Compatible with Hyva theme Version1.3 and Hyva checkout Version 1.1.