-
Notifications
You must be signed in to change notification settings - Fork 849
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Which ID should I save in the DB so I can compare and write it off later? #1685
Comments
@tiagocaus This looks like an integration support better directed at our support team for 1:1 help instead. You can contact them here: https://support.stripe.com/contact |
When a charge is created, there is no such thing as
|
@tiagocaus Sorry you had never mentioned using Checkout in your original question. The docs https://docs.stripe.com/payments/checkout/fulfill-orders cover this in a lot of details and tell you how to handle fulfillment exactly. |
@remi-stripe I've already tried talking to support. They can't help. This would be easily resolved if stripe adopted the standard of creating a unique ID, from the beginning to the end of the process! Why don't they do that? |
@tiagocaus I'm sorry but this is exactly what the doc I linked you to explains in a lot of details. Please work with our support team for 1:1 help as you are asking for integration support. |
Is your feature request related to a problem? Please describe.
I'm creating a microsaas, and I would really like to use stripe, as it is
accepted in all countries.
My problem is understanding which ID to save in the DB so that after it is paid, the webhook receives the IDs and thus compares them with the DB and thus cancels them.
This is because I intend to use a card and "Brazil Boleto" which is a payment method where the webhook will only receive data within 24 to 48 hours.
Could I have your help?
Describe the solution you'd like
Unique ID so we can save it in the DB
Describe alternatives you've considered
Frustrated, no solution!
Additional context
No response
The text was updated successfully, but these errors were encountered: