30,909
edits
Module Stripe: Difference between revisions
Jump to navigation
Jump to search
m
no edit summary
m (→Variants) Tag: 2017 source edit |
mNo edit summary Tags: Visual edit Mobile edit Mobile web edit Advanced mobile edit |
||
| Line 56: | Line 56: | ||
To create a restricted key, follow the [https://stripe.com/docs/keys#create-restricted-api-secret-key steps provided by Stripe]. When creating the key, the permissions needed by Dolibarr include: | To create a restricted key, follow the [https://stripe.com/docs/keys#create-restricted-api-secret-key steps provided by Stripe]. When creating the key, the permissions needed by Dolibarr include: | ||
* Customers: <code>write</code> | *Customers: <code>write</code> | ||
* Events: <code>read</code> | *Events: <code>read</code> | ||
* PaymentIntents: <code>write</code> | *PaymentIntents: <code>write</code> | ||
* SetupIntents: <code>write</code> | *SetupIntents: <code>write</code> | ||
* Checkout Sessions: <code>write</code> | *Checkout Sessions: <code>write</code> | ||
Then, you can replace the secret key with this new restricted key. | Then, you can replace the secret key with this new restricted key. | ||
| Line 79: | Line 79: | ||
The v10 is ready for this change. Dolibarr v10 offers 2 other modes of operation: | The v10 is ready for this change. Dolibarr v10 offers 2 other modes of operation: | ||
*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". This is the recommanded method enabled by default since Dolibarr v11 (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 (not required, for experimental purpose only). | *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 (not required, for experimental purpose only). This is an experimental variant. You should not have to set it. | ||
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. | ||