diff --git a/docs/api-docs/payments/payments-api-overview.mdx b/docs/api-docs/payments/payments-api-overview.mdx index 796ccf8cc..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 -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-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