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

DEVDOCS-5680: [update] Payments, clarify 3DS support #2121

Closed
wants to merge 2 commits into from
Closed
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
2 changes: 1 addition & 1 deletion docs/api-docs/payments/payments-api-overview.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -349,7 +349,7 @@ The payment gateway your application uses must be able to send raw card data thr

<Callout type="info">
#### 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.
</Callout>

### Create an access token
Expand Down