🔥 Feature: webhook-support-51

[msalbrain]

Description

This pull request addresses #51 with the following changes:

• Two new fields added to settings table (stripe_webhook_url and stripe_webhook_id)
• The settings queries were updated to accommodate to new fields
• The UpdateSettings handler was update to accept a webhook url input and make update to stripe as neccesarry
• A webhook listener handler was added at /api/_/stripe-webhook. Although it wasn't set as default
• Removed webhook secrete field from frontend stripe setting and added a webhook url field instead. Because the webhook secrete and webhook id are retruned from updating the webhook url on stripe
• what to do with webhook event is left unimplemented 👇🏼

Type of change

Please delete options that are not relevant.

• [x] New feature (non-breaking change which adds functionality)

Checklist:

• [x] I have performed a self-review of my own code
• [x] I have commented my code, particularly in hard-to-understand areas
• [x] I have made corresponding changes to the documentation
• [ ] New and existing unit tests pass locally with my changes

[shurco]

Hi @msalbrain,

Thank you for the work done, but it's not exactly what I wrote about in https://github.com/shurco/litecart/issues/51#issuecomment-1777152848 I meant that litecart should send a webhook to the specified address when one of the triggers is activated.

Your code sends a webhook from Stripe. Since payment is made in a sliding mode, such hooks are not needed.

[msalbrain]

thanks for the heads up. I see where you're coming from with the updates to the cart in the DB. I'll use that to trigger the webhook/API calls for payment updates.

Quick question: Should I ditch the webhook secret key, or is that part of another cool feature you've got in mind?

[shurco]

Quick question: Should I ditch the webhook secret key, or is that part of another cool feature you've got in mind?

You don't have to use the webhook key.