Comment 11 for bug 2057948

Hi Ken,

I have done some testing on your latest patch. I'm able confirm that the idempotency key is being generated and sent to Stripe when the request is sent.

However, repeated attempts to pay different combinations of circulation charges are failing - all have the same idempotency key.

I discovered that, in Account.pm, 'xact' that you referenced in your commit message represents the selected circulation charges and 'xact_misc' represents the miscellaneous (aka grocery) charges.

If I chose only circulation charges, the idempotency key was a hash of an empty string.

So I think if @payment_xacts aggregates all the charge ids - 'xact' in addition to 'xact_misc', that should do the trick.

Thanks for your work on this!