[SERVICE-API] Fixing bug: updating stripe order model so that customer details can be accessed #292
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
…throught he charge object
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.
I have been messing around with your boiler plates and had an error from the service API once I connected stripe and tried to do a test checkout.
The current code is trying to access the 'charges' object with paymentIntent.charges;
I changed this to 'latest_charge' and to access this I had to also expand on this object (as per Stripe documentation) with the line above - stripe client.retrieve().
Doing so in my own project seemed to fix the problem so I thought I would also add a PR for the boilerplate