From 6d5e89c6c707e39e0c1cad994bf6be36e693fd85 Mon Sep 17 00:00:00 2001 From: Ines MultiSafepay <“ines.mayer@multisafepay.com”> Date: Wed, 11 Sep 2024 10:48:58 +0200 Subject: [PATCH 1/4] DOCS-4325 Visa email --- content/payment-methods/3ds2.md | 2 +- content/payment-methods/card-payments.md | 2 +- content/payment-methods/cardholder-data.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/content/payment-methods/3ds2.md b/content/payment-methods/3ds2.md index d45566287..3c3100c80 100644 --- a/content/payment-methods/3ds2.md +++ b/content/payment-methods/3ds2.md @@ -32,7 +32,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. +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` parameter. # Exemptions diff --git a/content/payment-methods/card-payments.md b/content/payment-methods/card-payments.md index 70c789500..0cbe41e0e 100644 --- a/content/payment-methods/card-payments.md +++ b/content/payment-methods/card-payments.md @@ -99,7 +99,7 @@ The table below sets out the <> and < **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` parameter for VISA payments. diff --git a/content/payment-methods/cardholder-data.md b/content/payment-methods/cardholder-data.md index 717d22fb2..a89b5abbf 100755 --- a/content/payment-methods/cardholder-data.md +++ b/content/payment-methods/cardholder-data.md @@ -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` parameter. To learn how to create a fingerprint, see Recipe – Create a customer.browser object . From 7dd435cc880c6220602c0258f3a07c18875fdad0 Mon Sep 17 00:00:00 2001 From: Ines MultiSafepay <“ines.mayer@multisafepay.com”> Date: Wed, 11 Sep 2024 11:05:44 +0200 Subject: [PATCH 2/4] DOCS-4325 Visa email --- content/payment-methods/3ds2.md | 2 +- content/payment-methods/card-payments.md | 2 +- content/payment-methods/cardholder-data.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/content/payment-methods/3ds2.md b/content/payment-methods/3ds2.md index 3c3100c80..4f9730863 100644 --- a/content/payment-methods/3ds2.md +++ b/content/payment-methods/3ds2.md @@ -32,7 +32,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 correct information in 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. # Exemptions diff --git a/content/payment-methods/card-payments.md b/content/payment-methods/card-payments.md index 0cbe41e0e..f52c1703c 100644 --- a/content/payment-methods/card-payments.md +++ b/content/payment-methods/card-payments.md @@ -99,7 +99,7 @@ The table below sets out the <> and < **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 correct details in the `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. diff --git a/content/payment-methods/cardholder-data.md b/content/payment-methods/cardholder-data.md index a89b5abbf..be80d78d4 100755 --- a/content/payment-methods/cardholder-data.md +++ b/content/payment-methods/cardholder-data.md @@ -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 correct information in 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 – Create a customer.browser object . From 64a7c0ef466dfabbb5763e3dba94ae91baaccbbc Mon Sep 17 00:00:00 2001 From: Ines MultiSafepay <“ines.mayer@multisafepay.com”> Date: Wed, 11 Sep 2024 11:21:25 +0200 Subject: [PATCH 3/4] DOCS-4325 Visa email --- content/payment-methods/3ds2.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/content/payment-methods/3ds2.md b/content/payment-methods/3ds2.md index 4f9730863..6c2ba906d 100644 --- a/content/payment-methods/3ds2.md +++ b/content/payment-methods/3ds2.md @@ -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 <> 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. @@ -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 correct information in the `email` or `phone` parameter. +Note: 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 From a47d3da5c33ebf0f92735858f0a4478436bb08bb Mon Sep 17 00:00:00 2001 From: Ines MultiSafepay <“ines.mayer@multisafepay.com”> Date: Wed, 11 Sep 2024 11:23:57 +0200 Subject: [PATCH 4/4] DOCS-4325 Visa email --- content/payment-methods/3ds2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/payment-methods/3ds2.md b/content/payment-methods/3ds2.md index 6c2ba906d..18c76bc5f 100644 --- a/content/payment-methods/3ds2.md +++ b/content/payment-methods/3ds2.md @@ -39,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 example, transactions created with payment method VISA must include correct information in the `email` or `phone` 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