Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

API update 2020 - SCA #2

Open
res0 opened this issue Apr 29, 2020 · 0 comments
Open

API update 2020 - SCA #2

res0 opened this issue Apr 29, 2020 · 0 comments

Comments

@res0
Copy link

res0 commented Apr 29, 2020

Issue

There is a new EU regulation, which requires additional mandatory data about the user(buyer) - name, billing street, city, ZIP, country and e-mail.

Description

Source: https://doc.trustpay.eu/v01#apiUpdate2020Sca

What is SCA?

Strong Customer Authentication (SCA), as part of the Payment Services Directive (PSD2) in the European Economic Area, requires changes to customer authentication of online payments. In order to increase the security of online payments, a new version of customer verification will be required.

What SCA means for you?

TrustPay amended its payments gateway to meet the new regulatory requirements of SCA in a way that will require as few changes from the merchant´s side as possible. You will be required to send us some additional information about your customer in the payment requests for card payments and the rest will be done by TrustPay.

What changes do you have to make in your integration?

You have to send us the following additional fields in your payment requests for card payments:

Name Description Format
CardHolder The cardholder name Varchar(100)
BillingStreet The street name and number of customer's billing address Varchar(100)
BillingCity The town, district or city of customer's billing address Varchar(80)
BillingPostcode The postal code or zip code of customer's billing address Varchar(30)1
BillingCountry The country of customer's billing address Char(2)
Email Customer email Varchar(254)

1 Only alphanumeric characters are allowed. Other characters may be lost or changed during payment process.
For more information please check this section of our integration manual: Cards-Purchase

What is the deadline to update the integration?

You should ensure that your systems will comply with the above-mentioned changes by October 1st,2020. If you fail to update your integration, your transactions missing the new mandatory elements may be rejected by the issuing banks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant