Latest technical features, modifications and enhancements concerning the e-payment solution Saferpay from Worldline.
The new Saferpay OnSite App gives our merchants the possibility to transform any smartphone into a mobile payment terminal. Accepting payments on-site was never easier – no hardware or additional contract needed!
- Available and automatically activated if you have Saferpay Secure PayGate or Worldline QR Payments
- Compatible with all mobile OS (iOS, Android, etc.)
- Perfectly mobile optimized
- All means of payment and wallets supported (except Klarna Payments)
- 1.Enter amount
- 2.Show QR code to the payer
- 3.Receive instant confirmation
Saferpay now officially supports the payment method Worldline Crypto Payments in EUR for Belgium and Luxembourg.
- Available for all merchants with Worldline acquiring. Please reach out to your Account Manager or the Saferpay Support for the activation.
Saferpay implemented the Klarna integration to Billie, offering Business to Business transactions to be payed via Klarna's cooperation partner Billie.
This feature is available when the transaction was initialized either directly as "Company" in the billing address container or when selecting "Company" in the billing address form as title.
It is now possible to use negative amounts for order items of type "GIFTCARD". These items function as a voucher / deduction. Please refer to the Klarna documentation for more info.
The optional setting "Condition" for 3-D Secure 2.0 authorizations was added to the creation of Single-Use Payment Links either via the Backoffice or directly via the Management API.
This setting is used to control, whether or not, transactions without liability shift should be accepted. By setting this option you can make it easier to prevent losses from fraudulent transactions by moving the liability to the issuing bank. If the liability shift was declined the transaction is not processed, further reducing the risk of covering losses.
- The default value is "NONE" and results in no change of behavior.
- Existing links are using this default.
To follow current password safety guidelines, the new minimum length of passwords for the Backoffice is now 12 characters instead of the previous length of 8.
To improve the usability and increase accessibility of the Payment Page several adjustments were made allowing screen readers like TalkBack to provide a better experience.
Saferpay now supports Account-to-Account Payments (A2A) - new bank transfer payment method based on open banking API.
A2A is a Worldline brand based on PSD2’s Payment Initiation Service. No card, no app download or registration is needed. The two months pilot phase is starting now and the payment method will be available soon.
Saferpay implemented Alipay+ which offers support for additional wallets in many countries compared to Alipay and is now available for Saferpay merchants. The merchants have to sign a separate agreement to switch from Alipay to Alipay+ and will be migrated manually.
In China, Alipay+ is one of the leading mobile payment solutions. Together with its local e-wallet partners in Korea, Thailand, Malaysia, Philippines, Indonesia, India, Bangladesh and Pakistan, Alipay has more than 1.2 billion users. Accepting a variety of wallets means merchants across Europe will see increased customer numbers and revenue from tourists from Asia.
A new entry form was added which can handle debit and credit cards. By using this form a customer can directly enter his credit card information and does not need to click on the brand first. Also the value "Card" was added to the API, which gives the merchant the possibility to select all cards with a single value.
On newly created Saferpay accounts the Universal card entry form is active by default. For existing Saferpay accounts created before the release of API spec version 1.35, this feature must be activated manually.
The validity of Saferpay Secure PayGate links can now be additionally set in hours instead of only choosing the date. Backoffice users now can use a datetime picker to set the expiration date.
Failed transactions can now be filtered by provider which allows to find entries by a specific payment mean quicker.
SPG links can now be deleted over the Management API.
Correction: Logins managed by merchant administrators now required to have two factor authentication set up to be allowed to decrypt a PAN or do a credit.
Unnecessary information was removed from the success page and payer email as there was no benefit for the payer to have this information. Therefore the page looks more minimalist and focused on the important parts.
Multiple possibilities are now available to choose for the expiration of Google Pay tokens therefore making testing easier.
JCB certification was completed. 3DS 2.2 is now available for JCB and providers will be updated to 2.2 in the next weeks.
The country subdivision code can now be sent with or without the prefix for the country.
API parameter was added for DCC emails to be sent if DCC was used.
Liability shift container in the API was restructured and unused properties were removed.
Two-factor authentication (2FA) is now available for users who are maintained by Backoffice Merchant administrators. 2FA can be activated in the Saferpay Backoffice under User Settings by scanning the QR code with an authentication app. Once activated, the authentication code is required every time you log in.
Several improvements have been made to our Microsoft Dynamics 365 Fraud Protection (DFP) based Fraud Intelligence solution:
Furthermore, merchants can now exclude selected payment methods and terminals from the risk checks in the Backoffice.
For Single-Use Payment Links also a QR code is available in the Backoffice. Emails can be sent with QR code. Details for Single-Use Payment Links are now visible in the Backoffice. You can copy and see the details of the link. Journal is only visible for paid links.
In order to reduce GDPR impact, the merchant has now the option to remove the payer data from the email body.
Following Backoffice features are improved:
- 1.If the password for the Backoffice login is forgotten, it can be resetted via email with securly generated token. The reset link is for single use and expires after period of time.
- 2.Alias checkbox for payment mean storage and info tip is not visible for merchants without secure card data alias.
- 3.A link to a feedback form is added to the Backoffice footer.
Transaction stamp (issuer reference) is sent also for Diners Club International and American Express in both eLink and GICC protocols.
Saferpay now supports payments with Payconiq. Development in Saferpay is completed. Tests with the pilot merchants are ongoing.
Payconiq is a company from Luxembourg developing an API-based mobile payment and payment processing platform, active in Belgium and Luxembourg. The Payconiq platform connects banks, merchants, payment service providers and consumers to enable omni-channel payments online, in store, by invoice or peer-to-peer. Your customers can download one of the stand-alone apps or use the Payconiq integration in their mobile banking apps (where available), according to their country of residence. They connect their bank account to the app and then are able to make payments to affiliated merchants by scanning a QR code, or to friends (by e-mail address or mobile number).
We have improved error descriptions for merchants to help them avoid unauthorized retries followed by scheme penalties.
Merchants can choose to get a notification if a new alias is inserted. The notifications work the same way as for payments.
Saferpay now supports the new credentials model of Przelewy24. Every merchant has his own credentials with the new model. Credentials will be generated by Przelewy24 and then updated in Saferpay after the release.
Due to the insolvency of our risk analysis partner Fraugster, a new fraud prevention solution has been integrated into Saferpay. The new solution is based on "Microsoft Dynamics 365 Fraud Protection" to calculate a risk score and block high risk transactions.
As before, Saferpay Fraud Intelligence is available as a separately priced add-on. It allows merchants to model fraud rules and set velocity and risk score thresholds to define their risk appetite, reduce their fraud rate and improve conversion.
For all prepaid transactions the debit number was added to the OrderId for reconciliation.
The API was extended to receive the status of a SecurePayGate Link. Due to this change it is possible to build more sophisticated solutions with SPG links and it' i not necessary anymore to go to the backoffice or wait for the email to see when a link was paid.
Payconiq payments in the Payment Page go live for selected pilot merchants. Authorizations will be captured automatically. Merchants interested to participate in the pilot can reach out to their local sales contact.
ReturnUrlsparameter was replaced with one single
ReturnUrlwhich is called regardless of the transaction status.
Diners Club transactions will now be processed with 3-D Secure 2.1 depending on issuer support and card enrollment status.
A filter option has been added to the Multi-Use Payment Links which allows to show only active, only inactive or all.
Inactive links can now be restored in the link details.
Saferpay users can now change their own email address under User settings / Change email. The email address is updated after the user clicks the link in the confirmation email, enters the password and confirms the change.
Furthermore, several usability improvements have been made to simplify the activation of new users and a "Resend activation email" option will be shown on the user detail page until the new user has been successfully activated.
Since 1st January 2023, it is possible to do refunds in the new currency euro (EUR), when the original transaction was in old currency Croatian kuna (HRK). Captures and reversals are still submitted in the same currency (HRK) as authorization, if authorization was performed before deadline. New authorizations resp. captures must be submitted in the new currency after 1st January. More details are explained on our documentation page.
Scheme transaction IDs (issuer reference information) are now included in the API response to customers with Elavon acquiring.
Release Date: 2022-11-15
Available on Sandbox: 2022-11-01
Giropay and paydirekt have merged its business, therefore giropay will be shutdown as of end of November 2022. Merchants can switch to a paydirekt contract.
Multi-Use Payment Links are extended with extra functionality to provide the same functionality as today with web shop offers:
- no amount input (Multi-Use Links will support fixed or variable amount)
- additional option for entering delivery address and/or billing address (both, only one, none)
Journal export and batch export contain the delivery and billing address.
SourceUrl can contain now 2048 instead of 128 characters.
Merchants can access their license information via API.
As Croatia is switching from HRK to EUR on 1 January 2023, Saferpay now allows referenced refunds with a different currency. This is only the case if the currency of the original transaction is in HRK, the refund in EUR and after 1 January 2023. Also general improvements were made to handle future currency changes. Merchant information will follow. For more information please see our campaign site.
GXID will be sent if there is no OrderId. GXID is an unique id within Saferpay.
Release Date: 2022-09-20 Available on Sandbox: 2022-09-06
- Setup of users with access to multiple customer accounts: User administrators can now create a multi-customer access user by adding the user with the same email under another customer account they have access to.
- Change permissions of multi-customer access users: User administrators can now also modify multi-customer access users within the currently active customer account of the user administrator.
- User profile changes: First name, last name and email language preference of Saferpay users can be modified by the users themselves on the User Profile page in the Backoffice.
The User Administration functionality is still in pilot phase.
Want to participate in the pilot? Feel free to contact your account manager.
In the Klarna order item details, the merchant can now submit a product image and link to a product detail page. Klarna can display this additional information to allow the buyer to verify that it is the intended item.
Merchants who are using the iDEAL issuer preselection on their site need to remove Handelsbanken from the list of iDEAL issuers: From 1st of October 2022 onwards, iDEAL issuer Handelsbanken will no longer process iDEAL transactions anymore.
Release Date: 2022-07-19 Available on Sandbox: 2022-07-05
It is now possible in the Multi-Use Link configuration to define a reference number prefix. If given, each related payment will get an unique reference number assigned which is generated by using the prefix followed by a number. Based on the static prefix, merchants can easily tell to which Multi-Use Link a transaction is related.
In the Multi-Use Payment Link configuration a "Payer Email configuration" option has been added which allows to set the email entry field mandatory (default), optional or hidden so that no email entry is possible.
The payer now always gets to see the payable amount on the PayPal page.
Merchants with other acquiring contracts than Worldline (formerly SIX Payment Services) can now also use tokenization and recurring payments with Apple Pay.
Partial Approval (amount-reduced authorization) is now also supported in Transaction/Initialize. If the
AllowPartialAuthorizationflag is set, the issuer can authorize a lower amount than requested in case the cardholder has no sufficient funds or reached the card limit.
Release Date: 2022-05-17 Available on Sandbox: 2022-05-03
To better cater the needs of customers with B2B sales, it is now possible to provide a VAT number when entering billing address data.
On the Payment Page is the VAT field displayed only once a company name has been entered or if the VAT was prefilled by the merchant.
Release Date: 2022-03-15 Available on Sandbox: 2022-03-01
You can now use PayPal Express Checkout by creating your own checkout button which will open the Payment Page, pre-selecting PayPal only.
All needed customer data to fulfill the order including address and email will be returned to you.
Furthermore, we have added support for multiple certificates in the Server2Server integration to ensure interruption free processing of Apple Pay transactions during a certificate change.
The certificates are shown in the Apple Pay configuration pop-up of the terminal settings.
Added support for Ireland.
A new Device Fingerprinting functionality allows even more accurate fraud checks as we can now detect if the user device has been used before.
DeviceFingerprintparameter of the
RiskFactorscontainer in all relevant requests:
For added clarity, we have improved the way how Dynamic Currency Conversion (DCC) details like exchange rate and markup are shown on the Payment Page and in the payer confirmation email.
Furthermore, markup and exchange rate have been added to the
Dcccontainer in all relevant responses:
Internet Explorer version 11 and older will no longer be supported in the Saferpay Backoffice.
Mastercard has announced that they have discontinued their Masterpass mobile wallet service.
Therefore, Masterpass has been removed as a means of payment from Saferpay.
Release Date: 2022-01-18 Available on Sandbox: 2021-12-30
After launching the Multi-Use Payment Links functionality in November 2021 we collected feedback from pilot merchants to find out how they are using them and how we could adapt the solution give them an even better experience.
In this release Saferpay improved the amount entry on the first page of the Multi-Use Payment Link flow so that it respects the user's language, location and their device.
Klarna is getting more popular among our merchants and their payers so Saferpay enabled Secure PayGate (SPG) links to get paid with Klarna Payments (Pay Now, Pay Later and Financing).
As Klarna requires merchants to send details about the cart items that are sold, Saferpay now accepts these information when merchants create their SPG payment links using the Management API. See the API specification for version 1.26 for details. When providing the cart item details, Klarna Payments become available as a payment method in the Payment Page.
In order to benefit from Klarna Payments, merchants can activate the acceptance of Klarna Payments on their SPG terminals in the Saferpay Backoffice.
A new parameter called
AddressSourcewas added to the Payment API, which makes it easier for merchants to control whether the delivery address details should be collected from the selected payment method (if applicable forms exist for this payment method) or from the Saferpay Payment Page.
This is in particular useful for merchants who want to benefit from the PayPal Seller Protection program.
Saferpay aims at making payments as easy to integrate and consistent as possible and embraces every merchant's business. In some cases the so far used terminology ("payment") to describe the process does not match very well with what the merchant is offering to the consumer.
Therefore the Payment Page Configuration was extended to allow merchants to define the appropriate wording for the payment process. This supplements the existing configuration for the labeling of the pay button.
Card verifications are particularly useful to check whether an entered card number exists and give merchants the opportunity to let consumers authenticate the registration of cards in a PSD2 compliant way.
For merchants who operate in a PCI DSS Level 1 environment, ie. they are allowed to process plain text card numbers, the Saferpay Payment API was extended to accept plain text card details when initiating a card registration flow by calling the Alias/Insert method.
Merchants who offer PayPal as a payment method may want to benefit from the PayPal Seller Protection program which protects merchants from fraudsters. Saferpay now returns whether a PayPal transaction is eligible for the PayPal Seller Protection program in the Payment API parameter
The information is also shown on the transaction details page in the Saferpay Backoffice.
Poland is now supported as a consumer country when paying with Klarna. The issuer reference (sometimes referred to as "transaction stamp") is now also returned in Alias/AssertInsert responses if applicable.
Release Date: 2021-11-16 Available on Sandbox: 2021-11-02
Saferpay e-commerce merchants can now offer Google Pay in their online shops by activating it by themselves in the Saferpay Backoffice.
- Automatic self-onboarding in the Saferpay Backoffice (free of charge)
- No additional contract with Saferpay or Google needed
Merchants who want to use custom Apple Pay button integrations, can now activate this feature in the Saferpay Backoffice (see the "Apple Pay > Business" section in the terminal configuration).
The onboarding procedure guides the merchant through the process of creating the necessary cryptographic certificate.
Secure PayGate can now generate QR code links which can be used for multiple payments.
The QR code can be printed out and used on site or used online on websites or in emails. The link of the QR code leads to a form where the payer can enter the amount to be paid and optional the email address for the payment receipt. Upon successful payment the merchant receives a confirmation email.
Use cases for multi-use payment links include:
- Markets stalls & retail stores without terminals
- Unattended self-service shops (honesty box)
- Street food restaurants and catering
- On-site or online donations
- Club & community fee collection
Multi-Use Payment Links are available for all merchants who have Secure PayGate enabled.
In our ongoing efforts of reducing friction for merchants to set up their ideal payment environment we release the first version of a new way of managing users and their permissions on their own. This increases the overall security of the merchant's account as staff changes are reflected easier and quicker.
One core element of this new feature set is that users can login with their email address and do no longer need to remember their login ID. In future releases many new features around users, permissions and login experience will become available, e.g. two-factor authentication and multi-customer access. Stay tuned!
With this release we start a pilot phase where selected merchants can benefit from creating and managing users and their permissions within the Saferpay Backoffice.
Want to participate in the pilot phase? Feel free to contact your account manager.
From JSON API 1.25 onwards the Transaction/Refund method has an additional field
RestrictRefundAmountToCapturedAmountwhich can be set if refunds via API should be rejected if they exceed the captured amount. Unless the merchant chooses to set
true, the behavior remains as in previous JSON API versions.
Release Date: 2021-09-14 Available on Sandbox: 2021-08-31
Our new fraud solution for small and medium-sized customers is now available for pilot merchants. Transactions go through our AI-based engine for real-time risk analysis, resulting in a risk score. Merchants can configure to automatically decline risky transactions or to label them for manual review. Details can be found in the Integration Guide.
The Apple Pay Button can now be placed in external locations to process express checkout wallet transactions through Saferpay.
- Business Applications
Merchants can now provide additional merchant data for extended risk check capabilities on Klarna side. Details can be found in the API documentation of PaymentPage/Initialize under
Pre-authorizations and multipart-captures have been implemented for the following brands:
- American Express
- Diners Club International / Discover Card
The Transaction Journal can now be exported with the specified filter criteria applied.
The validation behavior of the Saferpay Fields has been changed to take place while typing, to display validation errors as early as possible.
New Payment Page languages:
- Bulgarian (BG)
- Icelandic (IS)
New Backoffice languages:
- Croatian (HR)
- Bulgarian (BG)
- Romanian (RO)
- Slovak (SK)
- Slovenian (SL)
Release Date: 2021-07-13 Available on Sandbox: 2021-06-29
Omni-Channel merchants are now able to reference an original POS authorization when creating a refund. This is achieved by supplying the SIX Transaction Reference of the original POS authorization to Saferpay. This functionality is currently available for card transactions and Alipay payments.
Alias/InsertDirect added support to provide an existing Transaction Stamp when available. This functionality is relevant only for PCI SAQ-D certified merchants who are allowed to handle and store plaintext card data.
The Transaction Interface was extended to support processing scheme tokens. Typical use cases are merchants who integrated wallets (e.g. Apple Pay, Samsung Pay, Google Pay), process credit cards through Saferpay and like to do this as well for the tokens. Details can be found in the Integration Guide.
A new Management API method allows to list activated payment means and currencies for a terminal. This can be used e.g. by shop plugins to reduce manual configuration efforts and allows a more user friendly onboarding procedure. Details can be found in the Management API documentation.
A new user interface for our pay-by-link solution Secure PayGate:
- Improved usability, look & feel
- Re-arranged sections for more intuitive use
- "Offers" have been renamed to "links"
For re-authorizations (where a follow-up payment is being made which references an earlier payment), merchants can now choose a different terminal than the one which was used for the original payment.
Improved terminal selection dropdown with filtering capabilities and other optimizations for customers with large amounts of terminals.
Release Date: 2021-05-18 Available on Sandbox: 2021-05-04
Bitcoin (BTC) and Ethereum (ETH) crypto payments go live for selected pilot merchants.
An announcement will be made as soon as the solution becomes available for all merchants.
- Full payment guarantee for merchants
- Swiss Francs (CHF) is only supported currency
Refunds on eps payments are now available except in some cases where the issuer eps scheme doesn't have the required data to process the refund. Furthermore it is now possible to process giropay payments via eps.
The direct bank transfer by Klarna (formerly known as SOFORT respective Sofortüberweisung) payment integration was extended to support the additional languages Spanish (ES), Hungarian (HU), Italian (IT), Slovak (SK) and Czech (CS). Also the supported currencies have been extended and PLN, HUF und CZK have been added.
The responses to PaymentPage/Assert, Transaction/Authorize, Transaction/Inquire and Transaction/QueryAlternativePayment have been extended with additional PSD2 relevant information.
The Liability container now contains a new field InPsd2Scope with possible values
The ThreeDs container has been extended with two new fields: Field Version shows which 3-D Secure version has been used and the AuthenticationType field with possible values
NONEindicates the type of the authentication.
Release Date: 2021-03-23 Available on Sandbox: 2021-03-09
Transaction Risk Analysis (TRA) and Low Value Payment (LVP) exemptions can now be automated. Risk appetite, velocity checks and other criteria can be defined as conditions. The exemptions are then automatically requested if applicable for the current transaction and all other specified conditions are met.
Transactions checked by Fraud Intelligence now also show the calculated risk score and Fraud Intelligence Insights in the Backoffice transaction detail views.
A new BlockReason field is added to JSON API responses if the transaction was blocked by the Saferpay Risk Management. The BlockReason tells whether the transaction was blocked due to IP address, IP location, issuer country or card blacklist entries.
The transaction details in the Transaction Journal and Declined Journal now show if a Transaction Risk Analysis (TRA) or Low Value Payment (LVP) exemption was requested.
A new Initiator field in Transaction/AuthorizeDirect requests can be used to indicate whether the transaction was initiated by the merchant (default) or by the payer.
The response of every successful authorization now contains an IssuerReference with a TransactionStamp and in case of a Mastercard transaction, a SettlementDate. The TransactionStamp and SettlementDate can be used to reference the authorization even if it was made by a business partner or via another PSP.
To reference an existing authorization, the IssuerReference can be passed on in Transaction/AuthorizeDirect requests.
Saferpay Fields Access Tokens can now be created by calling SaferpayFields ApiKeys in the Saferpay Management API.
The former Declined Reservations view has been renamed into Failed Transactions, and shows now also transactions blocked by the Saferpay Risk Management which have been shown before in the Event List view.
The Event List view now only shows old events and will be removed with a coming release.
- Added Klarna Payments support for Italy
- Added support for American Express account verifications (online checks) with optional SCA during Secure Card Data alias registration
Release Date: 2021-01-19 Available on Sandbox: 2021-01-05
Saferpay upgraded to the latest 3-D Secure version 2.2 for Visa Secure, Mastercard ID Check and American Express Safekey.
With the beginning of 2021, important PSD2 deadlines became active, forcing issuers to respond with a so called Soft Decline to certain not fully authenticated authorizations.
It is highly recommended for every merchant in PSD2 scope to implement proper handling of Soft Declines.
In case of a Soft Decline, the merchant needs to contact the payer so he can initiate another authorization with SCA. In case of Recurring Payments, a new initial transaction has to be made or a new Alias with SCA and a forced challenge flow need to be created.
All Aliases registered after the January release will have a SCA Transaction Stamp which is sent in subsequent transactions using this Alias. This means that newly registered Aliases might have a better approval rate compared to the old ones which don't have a SCA Transaction Stamp.
Multi-part captures and refunds are now available for Klarna Payments through the API and the Saferpay Backoffice. This allows you to partially capture an order to send and bill it in separate parts.
Saferpay is now connected to Worldine's omni-channel platform. This allows merchants to track transactions from Saferpay and other solutions combined in one portal.
Release Date: 2020-11-10 Available on Sandbox: 2020-10-27
Saferpay extends Fraud Intelligence module with additional features:
- Fraud check is now available for all supported card brands
- Added support for the Bancontact QR flow
- Fraud check support for MIT payments
- Suspected fraud can be flagged in the Saferpay Backoffice
The Saferpay Fields functionality was extended and improved:
- The CVC field is now set mandatory except for cards where no CVC exists
- Added preselection support for BonusCard and myOne
An SCD alias of a co-branded card is now stored together with the brand chosen by the cardholder for the authorization. This is to ensure that in later alias payments the same brand is being used again.
The terminal used for the alias payment must have the brand activated which was used in the authorization.
The AllowPartialAuthorization flag can be set in Direct Authorizations, to allow that the issuer can authorize a lower amount than requested, in case that the cardholder has no sufficient funds or reached the card limit.
Release Date: 2020-09-15 Available on Sandbox: 2020-09-01
Saferpay extends Fraud Intelligence module with additional features:
- Fraud checks can be activated/deactivated for individual payment methods in Saferpay Backoffice
- JSON API extended with additional data points for fraud check
- Fraud check is supported for Bancontact payments
Saferpay now supports Klarna Payments within the Payment Page for pilot merchants. Test envionment is available for all merchants. Public launch will be announced seperately.
- Pay Now
- Pay Later
The configuration of the payment button is now taken into the customers Secure PayGate email. E.g. if you configured the button in the Payment Page to "Donate" we will show the same text in the customers email.
Release Date: 2020-07-14 Available on Sandbox: 2020-06-30
You can now provide a payer ID to link transactions and stored aliases to your client by providing a unique ID. The Payer ID will help you filter, search and analyze transactions and aliases linked to your native system like CRM.
Saferpay is extending this functionality step by step, so far we've implemented:
- Transaction/AuthorizeDirect API call
- PaymentPage/Initialize API call (Transaction)
- Transaction/Initialize API call (Transaction)
- Journal search
- Server-side BIN range detection
- The expiry date drop-down fields were replaced with text input fields as used with Saferpay Fields
- A warning is shown if the refund amount exceeds the cumulated captured amount.
You can now store a card in the Saferpay Secure Card Data by sending a payment link created in the Saferpay Backoffice or via API.
Saferpay now accepts cards with all expiry dates and processes them according to the response of the issuer.
- An expired card will no longer be refused in JSON API calls
- Entering an expired card will show a warning in the Saferpay Backoffice but will not be refused
Release Date: 2020-05-12 Available on Sandbox: 2020-04-28
- Added support for card registration with or without performing a transaction
- Added support for new card brands
- American Express