Hi Terran,
I've only read about this recently, but I would imagine that the
combination of data elements you describe would at least take care of
double clicks and connection errors. It would be nice if we could use
something truly unique, like the billable_xact ids, but because users can
select
I read about that a while back, but I was under the impression that it
would only solve double-click types of problems, not problems where the
patron is actually filling out the form again. Is it just that we'd need to
design the idempotency key in a way that it generated the same key if the
I wanted to share some information from Stripe's support about the
duplicate credit card charges issue we have seen since our upgrade to 3.10.
Stripe support indicated that making the requests from Evergreen idempotent
will prevent retried requests from creating duplicate charges. This would
Thanks Terran!
We've seen that negative bill issue once since our upgrade, and we're
double checking that our tt2 files have the correct code.
We have also seen issues where the payment looks fine on the Evergreen
side, but on the Stripe side we see that more than one successful charge
was made
We still see it sometimes when a patron has a negative bill on their
account (even when the overall balance isn't negative).
The current code shouldn't even be showing the payment option if there are
any negative bills, but somehow some patrons are still getting the option.
We have been on the new
Hi Everyone,
Since moving to Stripe Payment Intents with our upgrade in early January,
we've seen issues with duplicate charges to the patron for the same billing
in Evergreen.
I've searched Launchpad, but haven't found a relevant bug.
Have others experienced similar issues since moving to
