-
Notifications
You must be signed in to change notification settings - Fork 63
Dealing with chargebacks and refunds #157
Comments
Mollie has no separate status for I'm thinking about a solution for detecting state changes, may become a separate package. Would require a database modification ,so |
@sandervanhooft I think they should change that it's weird when a payment is |
Not going to happen. Semantically they are not wrong, a charged back payment is still paid for, so paid is an end-state here. One of the possible solutions that were discussed is introducing events or an events API. This would be a big thing so if Mollie decides to go that way it would take a long time. For now/cashier-mollie: I'm looking into handling chargebacks and refunds. For a refund: the subscription should continue and an invoice should be generated. We can use In exotic cases, a payment can simultaneously refunds and chargebacks. For supporting these cases properly would require to store payments locally and diff them. This would require a more sophisticated approach, perhaps even an event store. It may be interesting for cashier-mollie v2. For v1, we could simply check for the payment having a refund or chargeback. I expect this to cover 98% of the use cases without introducing a breaking change. |
@sandervanhooft thanks that makes sense 👍 |
Hi,
I was wondering how this package handles a chargeback. I can see here that when a payment status
is
paid
it set's the payment to paid.However when a payment is a
chargeback
we still get the statuspaid
from mollie. So in this caseit would go through that
handlePaymentPaid()
method again right?cashier-mollie/src/Http/Controllers/WebhookController.php
Line 26 in d2b85e9
--EDIT
It will nog go into the switch because of this
$order->mollie_payment_status !== $payment->status
. But now de order status keepspaid
but it should bechargeback
.The text was updated successfully, but these errors were encountered: