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

Docs 4325 #3033

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion content/payment-methods/3ds2.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,13 @@ hidden: false
parentDoc: 62a727569e389a012f577acd
slug: '3ds2'
---

⚠️ Note:
>
> Due to scheme regulations, transactions created with payment method VISA must include correct customer details in the `email` / `phone` parameter.
> See also [Create Order](/reference/createorder/) > customer object.


# Authentication

3D Secure 2.0 (3DS2) is an authentication protocol that <<glossary:card schemes>> use to verify cardholder identity for online credit and debit card payments. Under the [PSD2](/docs/psd2/), MultiSafepay is required to apply it to **all** Europe-based card payments, and we enable it by default for non-EU payments as well.
Expand All @@ -32,7 +39,7 @@ When you collect cardholder data, you also need to collect other contextual info

See also [Cardholder data](/docs/cardholder-data).

Note: Some details are required to comply with scheme regulations. For exmaple, transactions created with payment method VISA must include the `email` parameter.
Some details are required to comply with scheme regulations. For example, transactions created with payment method VISA must include correct information in the `email` or `phone` parameter.

# Exemptions

Expand Down
2 changes: 1 addition & 1 deletion content/payment-methods/card-payments.md
Original file line number Diff line number Diff line change
Expand Up @@ -99,7 +99,7 @@ The table below sets out the <<glossary:order status>> and <<glossary:transactio

For example requests, on the [Create order](/reference/createorder/) page, in the black sandbox, see **Examples** > **Card direct/redirect**. Set `gateway` to `AMEX`, `MAESTRO`, `MASTERCARD`, `VISA`, or the generic `CREDITCARD`.

Note: Consider card-specific requirements for the [Create order request](/reference/createorder/), for example including `email` parameter for VISA payments.
Note: Consider card-specific requirements for the [Create order request](/reference/createorder/), for example including correct details in the `email` or `phone` parameter for VISA payments.

<img src="https://raw.githubusercontent.com/MultiSafepay/docs/master/static/img/APIExamples.png" align ="center"/>

Expand Down
2 changes: 1 addition & 1 deletion content/payment-methods/cardholder-data.md
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@ Set `type` to `direct`.
## 3DS2

When you collect cardholder data, you must also collect the contextual information about the customer's device (fingerprint) required for [3DS2](/docs/3ds2) authentication. The fingerprint can be created through JavaScript interfaces and methods in the customer's browser.
Note: Some details are required to comply with scheme regulations. For exmaple, transactions created with payment method VISA must include the `email` parameter.
Note: Some details are required to comply with scheme regulations. For exmaple, transactions created with payment method VISA must include correct information in the `email` or `phone` parameter.

To learn how to create a fingerprint, see Recipe – <a href="https://docs.multisafepay.com/recipes/create-a-customerbrowser-object" target="_blank">Create a customer.browser object</a> <i class="fa fa-external-link" style="font-size:12px;color:#8b929e"></i>.

Expand Down