Module Stripe - Revision history

Eldy at 14:05, 18 August 2025

2025-08-18T14:05:42Z

← Older revision		Revision as of 14:05, 18 August 2025
Line 82:		Line 82:
	*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.		*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.

	Since Dolibarr v11, the default mode STRIPE_USE_INTENT_WITH_AUTOMATIC_CONFIRMATION = 1 is automatically enabled, with no need to change or edit any configuration variable. So if you want to use the other method, you must first disable it by setting the constant to 0 (~~experimental,~~ not recommanded).		Since Dolibarr v11, the default mode STRIPE_USE_INTENT_WITH_AUTOMATIC_CONFIRMATION = 1 is automatically enabled, with no need to change or edit any configuration variable. So if you want to use the other experiment method, you must first disable it by setting the constant to 0 (not recommanded).

Eldy at 14:04, 18 August 2025

2025-08-18T14:04:59Z

← Older revision		Revision as of 14:04, 18 August 2025
Line 82:		Line 82:
	*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.		*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.

	Since Dolibarr v11, the default mode STRIPE_USE_INTENT_WITH_AUTOMATIC_CONFIRMATION = 1 is automatically enabled, with no need to change or edit any configuration variable. So if you want to use ~~another~~ method, you must first ~~disablebit~~ by setting the constant to 0.		Since Dolibarr v11, the default mode STRIPE_USE_INTENT_WITH_AUTOMATIC_CONFIRMATION = 1 is automatically enabled, with no need to change or edit any configuration variable. So if you want to use the other method, you must first disable it by setting the constant to 0 (experimental, not recommanded).

Eldy at 14:04, 18 August 2025

2025-08-18T14:04:15Z

← Older revision		Revision as of 14:04, 18 August 2025
Line 82:		Line 82:
	*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.		*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.		Since Dolibarr v11, the default mode STRIPE_USE_INTENT_WITH_AUTOMATIC_CONFIRMATION = 1 is automatically enabled, with no need to change or edit any configuration variable. So if you want to use another method, you must first disablebit by setting the constant to 0.

Eldy at 14:00, 18 August 2025

2025-08-18T14:00:31Z

← Older revision		Revision as of 14:00, 18 August 2025
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.

Eldy: /* Variants */

2025-08-16T23:25:50Z

Variants

← Older revision		Revision as of 23:25, 16 August 2025
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 (~~Still~~ experimental).		*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).

	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.

Eldy: /* Variants */

2025-08-16T23:25:14Z

Variants

← Older revision		Revision as of 23:25, 16 August 2025
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.

Eldy: /* Configuration */

2024-01-19T11:29:23Z

Configuration

← Older revision		Revision as of 11:29, 19 January 2024
Line 50:		Line 50:

	'''What about the Restricted API keys ?'''		'''What about the Restricted API keys ?'''

			This chapter has not been tested yet !!!!

	A restricted API key allows you to specify which Stripe resources the API key has access to read and/or write.		A restricted API key allows you to specify which Stripe resources the API key has access to read and/or write.
Line 57:		Line 59:
	* Events: <code>read</code>		* Events: <code>read</code>
	* PaymentIntents: <code>write</code>		* PaymentIntents: <code>write</code>
	* SetupIntents: <code>write</code> ~~(if using free trials)~~		* SetupIntents: <code>write</code>
	* Checkout Sessions: <code>write</code> ~~(if using Stripe Checkout)~~		* Checkout Sessions: <code>write</code>

			Then, you can replace the secret key with this new restricted key.

	=Usage=		=Usage=

Eldy: /* Configuration */

2024-01-19T11:26:54Z

Configuration

← Older revision		Revision as of 11:26, 19 January 2024
Line 54:		Line 54:
	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:

	~~TODO~~		* Customers: <code>write</code>
			* Events: <code>read</code>
			* PaymentIntents: <code>write</code>
			* SetupIntents: <code>write</code> (if using free trials)
			* Checkout Sessions: <code>write</code> (if using Stripe Checkout)

	=Usage=		=Usage=

Eldy: /* Configuration */

2024-01-19T11:24:58Z

Configuration

← Older revision		Revision as of 11:24, 19 January 2024
Line 52:		Line 52:

	A restricted API key allows you to specify which Stripe resources the API key has access to read and/or write.		A restricted API key allows you to specify which Stripe resources the API key has access to read and/or write.
	To create a restricted key, follow the ~~<a href="~~https://stripe.com/docs/keys#create-restricted-api-secret-key">steps provided by Stripe~~</a>~~. 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:

	TODO		TODO

Eldy: /* Configuration */

2024-01-19T11:24:10Z

Configuration

← Older revision		Revision as of 11:24, 19 January 2024
Line 50:		Line 50:

	'''What about the Restricted API keys ?'''		'''What about the Restricted API keys ?'''

	A restricted API key allows you to specify which Stripe resources the API key has access to read and/or write.		A restricted API key allows you to specify which Stripe resources the API key has access to read and/or write.
	To create a restricted key, follow the <a href="https://stripe.com/docs/keys#create-restricted-api-secret-key">steps provided by Stripe</a>. When creating the key, the permissions needed by Dolibarr include:		To create a restricted key, follow the <a href="https://stripe.com/docs/keys#create-restricted-api-secret-key">steps provided by Stripe</a>. When creating the key, the permissions needed by Dolibarr include: