Page tree
Skip to end of metadata
Go to start of metadata

This article aims to support integrators in deciding which alterations have to be made in order to comply with PSD2.

Basic facts about PSD2

For a somewhat comprehensive overview, please refer to this article at bundesbank.de: https://www.bundesbank.de/en/tasks/payment-systems/psd2/psd2-775954

One part of PSD2 is SCA (strong customer authentification), which is what most of this page will be about.

Affected Payment Methods

Credit Cards

To comply with the SCA requirement, credit cards will implement 3-D Secure 2.0. More Info on this here (in German)

Amazon Pay

The required changes are outlined here at Amazon: https://developer.amazon.com/de/docs/eu/amazon-pay-onetime/sca-upgrade.html

SEPA Direct Debit

Direct Debits will not be affected by SCA according to this Q&A by the EBA.

Changes to Our API

Some payment methods require changes to the way they are implemented.

We'll update this section as soon as more needed changes become available.

Credit Card Integrations

Keeping Transactions Frictionless

3DS 2.0 requires far more information about an order to be eligible for an exemption of the 3DS customer authentication challenge. If you want to make sure credit card payments stay as frictionless as possible after PSD2 comes into effect, please make sure that the following info is sent with all payment requests using credit card payments:

This is relevant for these payment requests:

  • initiating payment reservation (preauthorization)
  • initiating payment process (authorization)
  • creating a contract (createaccess)
  • initiating payment process in the billing module (vauthorization)

The more data that is provided, the greater the possibility of exemption on the part of the acquirer or issuer to circumvent the input of the 3-D Secure credentials.

If you don't currently use 3-D Secure 1.0, please make sure that your system is at least able to process 3DS 1.0 transactions and activate 3DS in your merchant backend. Transactions that don't use any form of 3DS will likely be declined starting mid-September 2019!

Fore more Information, please refer to this chapter of our Special Remarks for 3DS: https://docs.payone.com/display/public/PLATFORM/Special+remarks+-+3-D+Secure#Specialremarks-3-DSecure-3-DSecure2 - we strongly advise you read through this page to get a grip on the challenge process.

Example Request

This request is technically valid, but will very likely lead to a redirect including a challenge by the issuer. The customer would then have to provide more personal info and complete the issuer's challenge for SCA via an app or other second factor.

aid=12345 (your aid)
amount=25000
api_version=3.11
backurl=https://example.com/back
clearingtype=cc
country=DE
currency=EUR
encoding=UTF-8
errorurl=https://example.com/error
key=3adxxxxxxxxxxxxxxxxxxxxxxxx1cb9e (your portal key as md5)
lastname=Payer
mid=12345 (your mid)
mode=test
portalid=1234567 (your portalid)
pseudocardpan=9410010000164968406 (tokenized card data)
reference=565473895081303
request=authorization
successurl=https://example.com/success

This request contains more info on the order as well as the customer's IP and will likely apply for an exemption by the issuer (as long as no other risk assessment raises red flags)

aid=12345 (your aid)
amount=25000
api_version=3.11
backurl=https://example.com/back
city=Kiel
clearingtype=cc
country=DE
currency=EUR
de[1]=description article 1
email=shopper@example.com
encoding=UTF-8
errorurl=https://example.com/error
firstname=Paul
id[1]=artNum_0001
ip=192.168.0.1
it[1]=goods
key=3adxxxxxxxxxxxxxxxxxxxxxxxx1cb9e (your portal key as md5)
language=de
lastname=Payer
mid=12345 (your mid)
mode=test
narrative_text=frictionless please
no[1]=1
portalid=1234567 (your portalid)
pr[1]=25000
pseudocardpan=9410010000164968406 (tokenized card data)
reference=206486578761802
request=authorization
street=Fraunhoferstr. 2 - 4
successurl=https://example.com/success
telephonenumber=043125968200
va[1]=1900
zip=24118

Amazon Pay Integrations

Amazon implemented a new step in their payment flow. This "confirm order" step is documented here: https://docs.payone.com/display/public/PLATFORM/Special+remarks+-+Amazon+Pay#Specialremarks-AmazonPay-Confirmorder(newwithPSD2)

add_paydata[action]=confirmorderreference
add_paydata[reference]=reference5678
add_paydata[amazon_reference_id]=referenceid1234
aid=12345 (your aid)
mid=23456 (your mid)
portalid=12345123 (your portalid)
key=abcdefghijklmn123456789 (your key)
amount=6413
api_version=3.10
clearingtype=wlt
currency=EUR
encoding=UTF-8
mode=test
request=genericpayment
successurl=hhtp://www.your-success.url
errorurl=hhtp://www.your-error.url
wallettype=AMZ
workorderid= WORKORDERID12345
status=OK
workorderid= WORKORDERID12345

  • No labels