To wrap things up on my eight-part series on processing payments with Stripe, I’ll mention a few random things under the guise of testing and tricks. Most of the information will only make sense if you already understand how processing payments with Stripe works (i.e., if you’ve read the entire series).
Continue Reading...Archives For payment
In an earlier post in this series, I covered how you create an HTML form for securely handling payments via Stripe. In the previous post, I walked through the JavaScript that goes with that form. As explained in that post, thanks to the Stripe.js library, the proper HTML, and a bit of JavaScript, you can easily and securely handle payments on your site without getting mired in the PCI compliance muck. The secret is the Stripe.js library: it sends the customer’s payment information from the client to Stripe’s server and returns a token that Stripe associated with that payment information. Then, when the form is submitted, the token can be used by the PHP on your site to actually process the payment. The customer’s payment information, however, never touches your server. You get paid and the customer is protected.
In this post, I’ll walk through the necessary PHP code that actually processes the payment request. Note that this article assumes that you have read the previous articles and are comfortable with PHP.
Continue Reading...When you go to use any payment system for the first time on a project, you’ll need to create a test account. As with almost every step of the process, Stripe again makes this ridiculously easy. In this post I’ll explain how to create a test account in Stripe, and how that process is different than the other payment systems I’ve worked with, in a couple of ways. If you’re not currently planning on using Stripe, you may want to read my first post in this series, which explains how Stripe works and what its pros and cons are.
Continue Reading...