30,909
edits
m (→Configuration) Tag: 2017 source edit |
m (→Variants) Tag: 2017 source edit |
||
| Line 80: | Line 80: | ||
*By going to Home - Setup - Other and adding the constant STRIPE_USE_INTENT_WITH_AUTOMATIC_CONFIRMATION to 1, Dolibarr will use the PaymentIntent Stripe APIs according to the workflow "Automatic Confirmation" (https://stripe.com/docs/payments/payment-intents/quickstart) , which is ready for the SCA. | *By going to Home - Setup - Other and adding the constant STRIPE_USE_INTENT_WITH_AUTOMATIC_CONFIRMATION to 1, Dolibarr will use the PaymentIntent Stripe APIs according to the workflow "Automatic Confirmation" (https://stripe.com/docs/payments/payment-intents/quickstart) , which is ready for the SCA. | ||
*By going into Home - Setup - Other and adding the STRIPE_USE_NEW_CHECKOUT constant to 1, Dolibarr will use the CheckOut Stripe APIs according to the "Server Integration" workflow (https://stripe.com/docs/payments/checkout), which is also ready for the SCA. | *By going into Home - Setup - Other and adding the STRIPE_USE_NEW_CHECKOUT constant to 1, Dolibarr will use the CheckOut Stripe APIs according to the "Server Integration" workflow (https://stripe.com/docs/payments/checkout), which is also ready for the SCA (Still experimental). | ||
When using Dolibarr v11, the default mode is when STRIPE_USE_INTENT_WITH_AUTOMATIC_CONFIRMATION = 1 with no need to change or edit any configuration variable. So if you want to use another method, you must force this constant to 0. | When using Dolibarr v11, the default mode is when STRIPE_USE_INTENT_WITH_AUTOMATIC_CONFIRMATION = 1 with no need to change or edit any configuration variable. So if you want to use another method, you must force this constant to 0. | ||