Any ideas for webhooks integration?

I think I might have figured it out. I gleaned some ideas from the recurly module and ended up creating a "listener" page. Thus far I've only got it posting log messages, but the basic functionality is working.

So next I'll try create rules for each possible Stripe Event type.

I'll be happy to post all my modifications (possible contributions) once I've had a chance to finish, test and clean up my messy code.

I'll definitely post a patch once I've got everything working/cleaned up. Probably about a month or more from now.

Thanks again for creating this module, it's got us really close to finishing our site! : )

I did have some success setting up webhooks and rules "events" that could be triggered when a webhook was sent from Stripe. However, I found that the webhooks from Stripe aren't as detailed as I would have liked, thus I've since decided to explore using the drupal recurring framework module to setup recurring payments.

Sorry for the delayed response, honestly for the past couple of months I've been snowed under with other work (freelance VFX is still my day job), but hopefully that will be finishing up this week (or next) and I can start working on drupal stuff again. : )

A little off topic, but, I'm ashamed to admit that I don't even know how to use github. Where's the best place to learn how to make patches, so that I can share anything I come up with?

Finishing up some work on this now. Hopefully I'll have something to post this next week - although I've made a ton of changes and it might be unwieldy as a patch, we'll see. Basically at this point I've got webhooks -> rules working and integration with Commerce Recurring Frameworks, hopefully it'll be some useful updates for everyone. :)

Okay, here's the patch that I've created, I'll also upload a zip of the entire folder in case I've made any errors in my patching (first patch yay!).

There's a ton of stuff in this patch (probably should've split it up somehow), I'll do my best to explain everything. But honestly this may be enough of a departure from the original to constitute a new branch, not my place to say though. Either way, here's what we've got in this patch…

1 - Webhooks

In the settings page you can define your Webhooks "listener page" this needs to match whatever you've also setup in the Stripe.com admin settings.

Next you have a bunch of new rules events for the webhooks. When a webhook is sent the corresponding event is triggered, you can use these as you like.

note: I didn't setup all the webhooks (left out the subscription ones because that is covered by Commerce Recurring Framework), but if you look at the code in the module it would be simple to add the missing webhooks.

2 - Commerce Recurring Framework Integration

There is a new user-field called "Stripe Customer ID" this is where we store the customer ID that is created whenever a charge processed via Stripe. This is important because it allows us to do the recurring charges (via Commerce Recurring Framework) without requiring the user to redo the checkout process.

By default this field is set so that only admins have access to it. However, I'd recommend also installing Field Permissions so that you can really make sure no customer would ever have access to it.

Also included are some more new rules that pertain to recurring orders. These are gleaned directly from the Commerce Recurring Framework module and are meant to directly replace the payment rules used by default in that module. However, they don't require/use the Commerce Card on File module, instead they use the Stripe Token to process charges against the card on file with Stripe.

For example, you can now override the default "Trigger Payments against recurring orders" replacing the action Process payments against recurring orders with the new Process Stripe payments against recurring orders.

3 - User can manage their card on file

There's a simple little form on the user page that allows users (with the proper permissions) to see/edit their credit card on file.

4 - Misc updates

- added "short_title" and "display_title" info to the payment method
- fixed a glitch in commerce_stripe.js file that caused errors when using PayPal or other payment option alongside Stripe (token was being sent regardless of payment choice)
- modified the checkout submission form so that it accounts for the various options (anonymous user, authenticated no Stripe ID, authenticated w/Stripe ID)
- a default rule to add the Stripe Customer ID to new users (for anonymous checkouts)

5 - Caveats:

• I'm a hacker/coder by necessity not training, so please help me discover any errors I've made and most importantly if there are any security issues!

• If a user is setup for recurring orders and then completes an additional checkout with a different credit card their credit card on file will be updated to their most recent card used. This is a limitation of Stripe, they only keep 1 card on file and I don't see what we could do as a workaround, but it shouldn't be a big problem either, just worth noting.

Again, any and all feedback is welcome. Hopefully these updates will be useful to the community!

-Brad

@drastik

I originally left out the invoice webhooks because Stripe waits 1 full hour after charging a payment to create the invoice. Basically I just found that not very useful (for me) and there are a decent amount of invoice webhooks items, so I was a bit lazy about adding them.

Maybe I misread their documentation on that, but the other problem is that its pretty much impossible to test some of these webhooks quickly. They have the webhooks testing interface in the admin area, but those send out hooks with an event ID of evt_0000000000, which just throws an error on the receiving end.

Regardless of my reasoning, it should be simple enough to add those in. Feel free to add to the patch if you'd like, or maybe we should just wait to see what iler decide's to implement before making any more updates.

@Iler - that sounds like a good plan. I'll try to get a new patch out sometime over the next month.

@drastik - I'll add in those invoice webhooks whenever I get around to creating the new patch for the 7.x-2.x branch.

I see your point about the invoice webhooks in regards to Stripe's built in subscription service, but keep in mind that my patch does not integrate at all with Stripe's built in subscription/plan functionality. My patch integrate this module with the Commerce Recurring Framework module, so that all charges, updates, cancellations are handled in directly in drupal via Rules. Which makes for a much more flexible & scalable solution.

I found that Stripe's subscription options were very limited (one example, there's no way to do weekly or quarterly subscription), so I contacted them directly and while they do plan to expand the features they suggested that its best to handle subscriptions within Drupal and just use the stripe token to charge recurring payments and the updating of credit cards, etc.

All that said, it'll be easy enough to add in the invoice items and I'll do so with the next patch. Having all the webhooks available could never be a bad thing. But I just wanted to make it clear that it was not my intention with this patch to use Stripe's subscription features, but rather to handle all of that within Drupal.