Skip to content
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

Duplicate transaction because the first one is not completely finished #8195

Open
novoselt opened this issue Feb 18, 2025 · 0 comments
Open

Comments

@novoselt
Copy link
Collaborator

Describe the bug

  • Stripe shows Payment1 and a minute later Payment2. Minutes of the time stamps: 28 and 29.
  • CoCalc shows Payment2 and a second later Payment1, i.e. the order is reversed. Minutes of the time stamps: 30.
  • User reports "When I purchased the first time it said successful then when I went to use it. It said I didn’t have a valid license. So I went back to purchase again."

So it was not a matter of being impatient - CoCalc confirmed success, but something didn't finish yet. It seems that making Payment2 was the trigger to "completely finish" processing of Payment1.

To Reproduce
Unclear, unfortunately. Transactions 117390-117393 are an example.

Expected behavior
After any payment attempt the transaction is failed, successful, or still being processed. If the user is shown "success", no further steps/conditions should be required.

Additional context
This a rare event, but it is recurrent. In particular this "switch" of the payment order in Stripe and CoCalc and very short time between transactions on the CoCalc side.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant