[Evergreen-general] Stripe Duplicate Charges

[Morgan, Michele]

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 and pay against multiple xacts at the same time, I'm not sure how
that would work.

I will go ahead and open a Launchpad bug to continue the discussion there.

Thanks,
Michele

--
Michele M. Morgan, Systems Support Specialist
North of Boston Library Exchange, Danvers Massachusetts
mmorgan at noblenet.org



On Wed, Mar 13, 2024 at 3:37 PM Terran McCanna <
tmccanna at georgialibraries.org> wrote:

> 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
> scenario was the same? Like a combination of the patron ID and the amount
> and the date or something like that?
>
> On Wed, Mar 13, 2024 at 3:16 PM Morgan, Michele <mmorgan at noblenet.org>
> wrote:
>
>> 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 entail including an idempotency key as an element in the payment
>> request sent to Stripe. Here is some documentation from Stripe:
>>
>> https://docs.stripe.com/api/idempotent_requests
>>
>> I will likely open a Launchpad bug about this, but have not heard that
>> others have seen this issue. I would still be interested in hearing if,
>> besides PINES, there are other systems running Evergreen 3.8 or later and
>> using Stripe, and whether or not you have seen any issues.
>>
>> Thanks for any feedback,
>> Michele
>>
>> --
>> Michele M. Morgan, Systems Support Specialist
>> North of Boston Library Exchange, Danvers Massachusetts
>> mmorgan at noblenet.org
>>
>>
>>
>> On Wed, Feb 28, 2024 at 9:42 AM Morgan, Michele <mmorgan at noblenet.org>
>> wrote:
>>
>>> 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 for the same Evergreen bill. These patrons have *not* had any
>>> negative bills.
>>>
>>> Has anyone else seen similar behavior?
>>>
>>> Thanks,
>>> Michele
>>>
>>> --
>>> Michele M. Morgan, Systems Support Specialist
>>> North of Boston Library Exchange, Danvers Massachusetts
>>> mmorgan at noblenet.org
>>>
>>>
>>>
>>> On Tue, Feb 27, 2024 at 5:09 PM Terran McCanna <
>>> tmccanna at georgialibraries.org> wrote:
>>>
>>>> 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 code for a long time (more than 2 years?)
>>>> so the only thing we can think of is that those patrons must be using an
>>>> old device that is stubbornly hanging onto a locally cached version of the
>>>> page. But we haven't been able to recreate the problem, so it's really
>>>> frustrating to troubleshoot.
>>>>
>>>> As far as I can tell, what is happening is that the patron somehow
>>>> loads the old version of the page that didn't do the negative bill check,
>>>> pays, Stripe accepts the payment but it's the wrong amount, so when Stripe
>>>> sends it to Evergreen it fails. Then the patron sees that Evergreen didn't
>>>> accept it and they pay again (still the wrong amount), causing their credit
>>>> card to be charged again.
>>>>
>>>>
>>>>
>>>>
>>>> On Tue, Feb 27, 2024 at 4:59 PM Morgan, Michele via Evergreen-general <
>>>> evergreen-general at list.evergreen-ils.org> wrote:
>>>>
>>>>> 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 Payment Intents?
>>>>>
>>>>> For reference, bug 1894005
>>>>> <https://bugs.launchpad.net/evergreen/+bug/1894005> *Wishlist: Add
>>>>> support for Stripe Payment Intents* was released in Evergreen 3.8.
>>>>>
>>>>> Also, for reference, these two followup bugfixes:
>>>>>
>>>>> bug 1965579 <https://bugs.launchpad.net/evergreen/+bug/1965579> - Stripe
>>>>> Payment Intents and Negative Bills
>>>>> bug 1981628 <https://bugs.launchpad.net/evergreen/+bug/1981628> - Follow
>>>>> up to Stripe payment intents bug
>>>>>
>>>>> Thanks for any insight!
>>>>>
>>>>> Michele
>>>>>
>>>>> --
>>>>> Michele M. Morgan, Systems Support Specialist
>>>>> North of Boston Library Exchange, Danvers Massachusetts
>>>>> mmorgan at noblenet.org
>>>>>
>>>>> _______________________________________________
>>>>> Evergreen-general mailing list
>>>>> Evergreen-general at list.evergreen-ils.org
>>>>>
>>>>> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general
>>>>>
>>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.evergreen-ils.org/pipermail/evergreen-general/attachments/20240314/97d4db94/attachment.htm>