For the complete documentation index, see llms.txt. This page is also available as Markdown.

Overview

3DS2 allows you to authenticate your transactions to reduce fraud and shift liability

3DS2 is a payments industry standard that promotes secure, frictionless consumer authentication for online payments. 3DS2 allows you to reduce fraud by providing methods to verify the authenticity of online payments.

The steps required to implement 3DS2 using the GreenPay Gateway will depend on:

  1. If you have already have an MPI (Merchant Plug-in) or require the GreenPay Gateway to act as your MPI

  2. Your PCI level

  3. Your preferred integration method

MPI

I already have an MPI

If you have an existing MPI integration you will need to follow your MPI's instructions in order to authenticate a payment transaction. After authentication your MPI will provide you with 3DS data which may include:

  • Cryptogram, CAV, CAVV or AAV

  • Ecommerce Indicator (ECI) or Security Level Indicator (SLI)

  • PARes

  • VERes

You will then need to set the 3D Secure fields on your GreenPay Gateway Purchase or Refund API calls in order to complete a 3DS2 transaction.

I don't have an MPI

The GreenPay Gateway can act as your MPI. Please contact your GreenPay representative for more information on how to add the GreenPay Gateway's 3DS2 MPI to your account.

Using the GreenPay Gateway's MPI, there are various integration methods to choose from depending on your PCI level:

Integration Method
Description
3DS Integration Guide

Hosted Payments Page

PCI SAQ A required Your website uses the GreenPay Gateway's payment form through the GreenPay Gateway Hosted Payments Page iframe. Payment processing is entirely outsourced to the GreenPay Gateway, meaning you do not need to handle any raw card data.

Direct Post

PCI A-EP required Your website hosts the payment form and you are responsible for collecting card details on front end code you host. Card data exchange with the GreenPay Gateway will take place via an AJAX call from your frontend directly to the GreenPay Gateway.

API

PCI SAQ D required Your website hosts the payment form and you are responsible for collecting card details in both your backend and frontend. Card data exchange with the GreenPay Gateway will take place via API calls from your backend system to the GreenPay Gateway.

Last updated