Stripe: Killer Payment Processing + ??? = Profit

Hi Nizar!

Hmm. I don't think it changes much in Stripe... if you're buying some products, there is no problem with "checking out" multiple times with multiple amounts. Is there some specific doubt or problem you're running into?

Cheers!

I do not know how to do?
What mechanism should I use in stripe?

Hey Nizar!

That's a pretty big question, unfortunately. We have the tutorial to help, but I don't think I can answer such a large inquiry. If you have some specific questions, please definitely let me know.

Good luck!

Hi ryan ,
Thanks you for your response.
To pay in multiple times on my website, I thought of this following solution:
I create the customer via stripe during his first payment, then I store his id in my database and I charge the customer later by using his Id.
(by using a cron to automate this task)

what do you think of this solution ?

Hey Nizar!

This is a great idea - we do something similar on SymfonyCasts (creating the customer via Stripe on first payment and saving that in the database). About the cron, that should work fine - if you need to, sort of, "schedule" when the next payment should happen (but it's not a recurring subscription), you could have a table in the database - e.g. scheduled_payments - that you query during this cron job. For example, that table might have charge_amount and charge_at (a date time column). The cron would then query the table for all rows where charge_at is < NOW().

Anyways, it seems like you are, indeed, in the right path. Here is some info about this topic - https://stripe.com/docs/pay...

Btw, much of the Stripe API has evolved and changed since this API - so check their docs thoroughly - this course is getting out of date.

Cheers!

Ryan,
Thank you very much for his useful information
Have a nice week end

Hey Camille,

Agree with Diego. But along with error messages Stripe also provides you error codes, you can check them here: https://stripe.com/docs/err... - thought not sure if it's the full list of possible errors or no - most probably it's full, at least for now. So, instead of translating full strings - better to translate error codes because there's much less chance that they will be changed, though Stipe may tweak error messages.

So, for example, instead of translating "The card has expired. Check the expiration date or use a different card" translate this "expired_card".

I hope this helps!

Cheers!

Thank you victor !

Thanks for your kind words ojtouch :)

I think you can do something similar as we do with security messages. Just get the full string (stripe message) and add a translation, but don't forget to actually translate the text before rendering it

Cheers!

Thank you MolloKhan !

Hey ojtouch

Not really, although Stripe already re-designed his dashboard but everything been taught in this tutorial is still relevant and useful

Cheers!

Thanks !

Hey Rodolfo!

Absolutely :). I don't think I used any features that are new in Symfony 3.1 for this tutorial, so everything should work fine. The "newest" feature I use is service autowiring... which is optional anyways (there are a few minor things with autowiring that were improved in 3.1, so it's possible that autowiring may not work in some cases... but it probably will). The biggest difference will be to translate the different directory structure from Symfony3 to Symfony2 - most importantly that bin/console in Symfony3 is app/console in Symfony2, var/cache is app/cache and a few other minor things.

So yea, get to it! If you have questions along the way, just let us know.

Cheers!

So as I'm understanding right now, every course in this site is built on top of symfony framework? I'm telling you this because in the course description you don't mention anything about symfony, so I'm deducting that It's because of every course here is built with symfony

Yes and no :). Our courses mostly fall into 3 different categories

1) Courses about Symfony where we're teaching Symfony (e.g. anything on http://knpuniversity.com/tr...
2) Courses about some topic (REST, Stripe, Behat). We *often* use Symfony in these, but we try to keep the information as "agnostic" of Symfony as possible, trying to use only the more basic features of Symfony so that someone who doesn't know Symfony well can learn the topic.
3) Beginner courses that are not built on any framework (e.g. http://knpuniversity.com/tr... and http://knpuniversity.com/tr....

So, the trickiest ones are category (2) - it's not very realistic to build real application without a framework... but you also don't want the framework to be a barrier to entry. So, we do our best :).

Cheers!

Hey Shairyar,

Yes, it will. Actually, the downloaded course code always contains 2 directories: the "start/" directory holds initial data at the start of course, so you could easily start coding from there when you start a course. The "finish/" directory holds the code of all chapters, i.e. the code after the latest chapter in the course.

Cheers!

Thanks Victor

Hey!

We'll release this tutorial this week! And I've added PayPal to our list of ideas - we actually integrate with both Stripe and PayPal (via Braintree) here on KnpU - and it was a bit difficult to support both - and interesting topic!

Cheers!

Thank you so much for the reply! Would be great to have PayPal integration too as many of us still use PayPal along with other payment processor such as PayPal Express Checkout. I do really appreciate you putting up the Stripe tutorial, as we are planning to add Stripe support soon.

Awesome! Yes, we use PayPal here on KnpU (in addition to Stripe) - via Braintree. It's not *quite* as smooth as using Stripe, but it makes life much easier than working with PayPal directly. We've had someone else already ask about PayPal as well, so it's on our list!

Cheers!

PayPal would be great! Any idea when this would be coming?

Unfortunately, it's not on the schedule for any time too soon :/. I'll add a vote for you on that topic - which always helps! But we've got some other tutorials we need to get out first before considering it. But definitely, Braintree makes it *somewhat* simple - it's similar to Stripe in many ways. If you do start implementing Braintree and have any questions, feel free to ask.

Cheers!

If we have braintree tutorials, it would be excellent! I am looking to implement braintree and after reading the documentation, I am still lost! Please do update us if there are any progress yet. Really in love with your videos!! and thank you so much for your effort.

Sorry - no progress to report - it's not one of our highest priorities! I *can* tell you that our Braintree setup is very similar to our Stripe setup: we have all the same webhooks and all the same flow (creating customers, subscriptions, etc). The biggest difference is just learning the differences between the API's themselves. If you have some specific questions, we can do our best to help - we do have a wealth of knoweldge on this... but won't be able to publish anything too soon about it!

Cheers!

Hey Jovan,

More videos should be in 1-2 weeks. Stay tuned! :)

And part 1 is all up! Next up: https://knpuniversity.com/s... - video already recorded. It's big and fun :D

Awesome - thanks for the nice message :). We're already recording part 2 about subscriptions. And it's big!