Bug #7536
closed
Stripe: disputes providing a py_ prefixed charge are not using basket id lookup
Description
When Stripe sends a dispute it has no metadata to lookup the basket associated with the IPN. The backup behavior is to try and find it based off the charge. Disputes are now sending a py_ prefixed charge, which it previously was not doing so there is no lookup behavior for it.
https://www.joomlapolis.com/forum/255-developer-members-support/240893-stripe-dispute-change#311978
Updated by krileon over 5 years ago
There is no mention in the documentation or API documentation for py_ charges. Searching around the web it's reportedly just a normal charge, but to a connected account and can be accessed using the same API as a ch_ charge.
Updated by krileon over 5 years ago
Only getStripeBasket directly checks ch_. Just add an OR case to it to treat py_ same as ch_.
Updated by krileon over 5 years ago
Confirmed py_ is used for alternative payment methods like ACH, but this is undocumented and isn't always the case. In short treat py_ and ch_ the same in all usages.
Updated by krileon over 5 years ago
- Status changed from Assigned to Resolved
- % Done changed from 0 to 100
Fixed in MR !156 with implementation of Hosted Checkout
Updated by