Overview

This document is intended for all NETELLER merchants migrating to the Paysafe Payments API to comply with SCA regulation.

The second Payment Services Directive (PSD2) introduced a new European Economic Area (EEA) regulation called Strong Customer Authentication (SCA). It is necessary for all NETELLER merchants to be SCA compliant in order to accept NETELLER payments.

To ensure SCA compliance, Paysafe is introducing the Paysafe Payments API as its new payment technology for the NETELLER platform.

Paysafe will be disabling Payin, Payout and Lookup Payment functions via the NETELLER REST API on 15 May 2020. In order to continue transaction processing via the NETELLER service, you must integrate these functions via the Paysafe Payments API before 15 May 2020.

SCA-Compliance

As of 14 September 2019, SCA regulation has come into effect to make online and in-app payments more secure in the European Economic Area (EEA). With this, online transactions that originate from EEA customers are required to go through the two-factor authentication.

SCA aims to:

  • Reduce fraud

  • Enhance customer protection

  • Make online payments more secure

It is important to use two out of the three forms of authentication (as conveyed during an earlier communication) to meet your SCA requirement.

The new requirements are set out in the Revised Payment Services Directive (PSD2) and in the Regulatory Technical Standards on SCA and Common and Secure Communication under PSD2 (RTS), which the European Commission published on 27 November 2017.

Migration to the Paysafe Payments API

The Paysafe Payments API not only enables you to comply with the new SCA regulation but it also offers a single integration to service all your payment needs. In fact, the Paysafe Payments API allows you to handle both Payments/Standalone Credits transactions using a variety of payment methods with minimal changes to your integration.

The Paysafe Payments API has been designed to be:

  • Easy to integrate

  • The centralized API for Paysafe’s products as it offers a variety of payment methods

  • Simple to maintain as you can benefit from additional payment methods with limited development efforts

  • Robust, scalable, and flexible solution

Migration Phases

Migration to the Paysafe Payments API will be carried out in the following two phases:

  • Phase I: Payments and Standalone Credits integration with the Paysafe Payments API

  • Phase II: Integration of the remaining features with the Paysafe Payments API

Phase I – Payments and Standalone Credits integration with the Paysafe Payments API

The new Paysafe Payments API will initially replace only the following features:

The legacy NETELLER REST API continues to support the following features through the existing APIs:

  • Customer lookup
  • Plans
  • Subscriptions

You should continue using the existing NETELLER Merchant Dashboard during Phase I.

Phase II – Integration of the remaining features with the Paysafe Payments API

All of the NETELLER REST API features will be migrated to the Paysafe Payments API by the end of this phase. You can then:

  • Ability to perform customer verification
  • Enhanced support for multi-item orders
  • Recurring billing

And much more, all through the single Paysafe Payments API.

Did you find this page useful?