craftzing/laravel-mollie-webhooks

Handle Lokalise webhooks in a Laravel app

This package serves as a starting point to create a new Laravel package. Everything's in place to get you started quickly:

• Documentation outline
• Basic workflows
• Basic config files
• Laravel-specific code starters
• ...

Perform a "search and replace" action for the following placeholders and update them with an according value:

• laravel-mollie-webhooks: Please make sure to use lowercase and dashes as a separator (e.g. my-package)
• MollieWebhooks: Not that the default namespace is already set to be Craftzing\Laravel (e.g. MyPackage)
• Handle Mollie webhooks in a Laravel app
• Rémi Pelhate
• [email protected]

Replace the banner at the top of this file with one for this package.

Then, replace this section with a short description about what the package does. You can add a short code-snippet if you want. From then on, you can start implementing some code, write the docs, ...

🔥 Features

• Short feature title. Short feature description. Make it sound zazzy!

📚 Docs

• Getting started
• Usage

📝 Changelog

Check out our Change log.

🤝 How to contribute

Have an idea for a feature? Wanna improve the docs? Found a bug? Check out our Contributing guide.

💙 Thanks to...

• The entire Craftzing team
• All current and future contributors

🔑 License

The MIT License (MIT). Please see License File for more information.

laravel-mollie-webhooks's Issues

WebhookCallPaymentHistory should not take failed webhook calls into consideration

Webhook calls that exited with an exception should be excluded from the payment history to prevent an invalid state of the payment history.

WebhookCallPaymentHistory sometimes updates the webhook payload when it shouldn't

How to replicate the bug

1. Create a Mollie payment.
2. Follow the checkout URL and fake the status to paid. This will make Mollie call the webhook, which should add the payment status to the ongoing webhook call payload in the database.
3. Create a refund for the payment. Refunds in test-mode typically need about 20min to reach the refunded status, which is the point at which Mollie calls the webhook again.
4. Mollie calls the webhook, which should add the refund ID and status to the ongoing webhook call payload in the database.
5. Hit the webhook route manually while nothing has changed on the payment. Notice that the webhook calls once again receives the payment status in the payload in the database. => This shouldn't happen, as the status didn't actually change.