ISVforce Guide
jSummer '25 (API version 64.0)
Spring '25 (API version 63.0)
Winter '25 (API version 62.0)
Summer '24 (API version 61.0)
Spring '24 (API version 60.0)
Winter '24 (API version 59.0)
Summer '23 (API version 58.0)
Spring '23 (API version 57.0)
Winter '23 (API version 56.0)
Summer '22 (API version 55.0)
Spring '22 (API version 54.0)
Winter '22 (API version 53.0)
Summer '21 (API version 52.0)
Spring '21 (API version 51.0)
Winter '21 (API version 50.0)
Summer '20 (API version 49.0)
Spring '20 (API version 48.0)
Winter '20 (API version 47.0)
Summer '19 (API version 46.0)
Spring '19 (API version 45.0)
Winter '19 (API version 44.0)
Summer '18 (API version 43.0)
Spring '18 (API version 42.0)
Winter '18 (API version 41.0)
Summer '17 (API version 40.0)
Spring '17 (API version 39.0)
Winter '17 (API version 38.0)
Summer '16 (API version 37.0)
Spring '16 (API version 36.0)
Winter '16 (API version 35.0)
Summer '15 (API version 34.0)
Spring '15 (API version 33.0)
Winter '15 (API version 32.0)
Spring '14 (API version 30.0)
No Results
Search Tips:
- Please consider misspellings
- Try different search keywords
Use Managed Packages to Develop Your AppExchange Solution
Pricing Plans in AppExchange Checkout
Payment Methods in AppExchange Checkout
How Is Revenue Shared in AppExchange Checkout?
Collect VAT for AppExchange Checkout Transactions
What Is Strong Customer Authentication?
How Strong Customer Authentication Affects AppExchange Checkout
Prepare Your Customers for Strong Customer Authentication
Manage AppExchange Checkout Subscription Payments That Require Customer Authorization
View AppExchange Checkout Subscription Payments That Require Customer Authorization
Authorize an AppExchange Checkout Subscription Payment
OEM User License Guide
Strong Customer Authentication Best Practices for AppExchange Checkout
If you sell an AppExchange solution in a region that requires strong customer
authentication (SCA), follow these Checkout best practices.
-
Prepare Your Customers for Strong Customer Authentication
If you serve customers in the European Economic Area, communicate how strong customer authentication (SCA) affects online payments, including payments for your AppExchange solution. -
Manage AppExchange Checkout Subscription Payments That Require Customer Authorization
If a Checkout subscription payment fails because it requires customer authorization, determine how Stripe handles the related subscription. For example, you can configure Stripe to cancel the subscription, mark the subscription as unpaid, or take no action. -
View AppExchange Checkout Subscription Payments That Require Customer Authorization
If a Checkout subscription payment can’t be processed because it requires customer authorization, Stripe marks the payment as failed. View these payments in the Stripe dashboard to see transaction details, including customer contact information. You can use this information to follow up with the customer and provide instructions for authorizing the payment on AppExchange. -
Authorize an AppExchange Checkout Subscription Payment
In regions that require strong customer authentication (SCA), a customer’s bank or credit card issuer may require the customer to authorize Checkout subscription payments periodically. To see payments that require customer authorization, check your Stripe dashboard. If authorization is required, we prompt the customer when they log in to AppExchange. However, you can also provide customers with self-service instructions for authorizing a payment.