Created
June 2, 2013 23:33
Revisions
-
JeffreyWay created this gist
Jun 2, 2013 .There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode charactersOriginal file line number Diff line number Diff line change @@ -0,0 +1,16 @@ So you want to accept payments online with PHP? - Well, you probably don't want to handle that process manually. Too dangerous and risky. - So learn the Stripe API. Works great! - But you'll still need to setup SSL. So go learn how to do that. - Stripe provides a PHP package, so download that through Composer. If you're not familiar with Composer, you'll need to learn that too. - If you want the most flexibility, you'll want to manually create the payment form. - So you'll need to send an AJAX request with a special token to Stripe's API. jQuery makes this easy, so go learn jQuery. - Once the payment completes, you'll likely want to send the buyer a "Purchased" email, so learn how to send email. - But don't make the user wait for the email to send. That takes too long. Add that to a background job. - If you want to use queues, then you'll need to learn how to use a service, like Iron.io. - Unless you want to do all of this with raw PHP, learn how to use a framework, like Laravel. - Finally, once you have everything working, are you sure that you're following the separation of concerns pattern? Go refactor. Don't know how? Well watch countless presentations, and learn how. ...And we wonder why we get overwhelmed.