Update to Stripe v3 #6121
Merged
Update to Stripe v3 #6121
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
There is 1 last detail to figure out, I had to go back to creating one customer entry per subscription (instead of reusing the customer entry) due to how declines are now handled. Reached out to Stripe regarding that, we'll see if I have a way to put it back to using the same customer object, otherwise we'll merge as-is. |
|
@jrouzierinverse, please review this for inclusion in 10.3 |
jrouzierinverse
requested changes
Mar 23, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Stripe now required to use the latest version of Stripe checkout (elements) for auto compliance, this updates the integration to use Stripe elements (also known as Stripe checkout v3)
Impacts
Stripe integration
Delete branch after merge
YES
NEWS file entries
Enhancements