diff --git a/docs/api-docs/payments/payments-api-overview.mdx b/docs/api-docs/payments/payments-api-overview.mdx index ed72463d3..86c1533a7 100644 --- a/docs/api-docs/payments/payments-api-overview.mdx +++ b/docs/api-docs/payments/payments-api-overview.mdx @@ -21,7 +21,7 @@ Learn more about BigCommerce API [OAuth scopes](/docs/start/authentication/api-a #### Implementation note -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 and then charge it as a stored payment instrument. Attempts to process any payment requiring 3D Secure verification using a card you have not previously saved will be unsuccessful. +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, any 3D Secure-enabled card must first be saved during a shopper-initiated transaction and then charged as a stored payment instrument. Attempts to process any payment that requires 3D Secure verification using a card that has not been previously saved will be unsuccessful. You can process payments charged to either of two main forms of payment: [stored payment instruments](#stored-cards-and-paypal-accounts) or [new cards](#credit-cards), which weren't previously saved. The API flow does not currently support hosted, offsite, or wallet-type providers, such as Amazon Pay.