From ca6c849fdfe9b0e8da94ec730c8c0607801e6645 Mon Sep 17 00:00:00 2001 From: Traci Porter Date: Thu, 21 Dec 2023 13:33:43 -0600 Subject: [PATCH 1/2] DEVDOCS-5689: [update] update 3DS Support --- docs/api-docs/payments/payments-api-overview.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/api-docs/payments/payments-api-overview.mdx b/docs/api-docs/payments/payments-api-overview.mdx index 796ccf8cc..d634c86dd 100644 --- a/docs/api-docs/payments/payments-api-overview.mdx +++ b/docs/api-docs/payments/payments-api-overview.mdx @@ -349,7 +349,7 @@ The payment gateway your application uses must be able to send raw card data thr #### Implementation note -Attempting to process a payment through the API using the full credit card information may fail if the card issuer requires 3DS authentication. In that case, the card must be saved through a shopper-initiated transaction before it can be charged using the Payments API. +3D Secure is a storefront experience that requires the shopper's (end-customer) interaction. As this API is a server-to-server API (not a storefront API), attempting to process any payment that requires 3D Secure verification will fail, as these payments inherently require shopper interaction. Whenever 3D Secure is required, you must save cards via a shopper-initiated transaction before they can be charged as a stored payment instrument using this API. ### Create an access token From e362527d31c955c33d2b8861048dbc3e8f8f5794 Mon Sep 17 00:00:00 2001 From: Traci Porter Date: Tue, 26 Dec 2023 10:40:18 -0600 Subject: [PATCH 2/2] Update docs/api-docs/payments/payments-api-overview.mdx Co-authored-by: Sarah Riehl --- docs/api-docs/payments/payments-api-overview.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/api-docs/payments/payments-api-overview.mdx b/docs/api-docs/payments/payments-api-overview.mdx index d634c86dd..ba0470dba 100644 --- a/docs/api-docs/payments/payments-api-overview.mdx +++ b/docs/api-docs/payments/payments-api-overview.mdx @@ -349,7 +349,7 @@ The payment gateway your application uses must be able to send raw card data thr #### Implementation note -3D Secure is a storefront experience that requires the shopper's (end-customer) interaction. As this API is a server-to-server API (not a storefront API), attempting to process any payment that requires 3D Secure verification will fail, as these payments inherently require shopper interaction. Whenever 3D Secure is required, you must save cards via a shopper-initiated transaction before they can be charged as a stored payment instrument using this API. +3D Secure is a storefront-based experience that requires the shopper's interaction to authenticate the transaction. Because requests to our Payments API must be initiated in a server-to-server context, rather than from the storefront, you must save any 3D Secure-enabled card during a shopper-initiated transaction, then charge it as a stored payment instrument. Attempts to process any payment that requires 3D Secure verification prior to saving the instrument will be unsuccessful. ### Create an access token