Archives For ecom

Stripe Testing and Tricks

February 13, 2013
This entry is part 8 of 8 in the series Processing Payments with Stripe

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...

Handling Stripe Errors

January 30, 2013
This entry is part 7 of 8 in the series Processing Payments with Stripe

If you’ve sequentially followed this series on implementing payments with Stripe, you now know everything you need to be processing payments with Stripe today. In theory. This series, the six posts to this point, has already walked through all of the code needed for the system to work, assuming everything does work. Which is to say I have yet to explain how to watch for and handle the errors and problems that will inevitably occur. That’s the focus in this post.

Note that this article assumes that you have read the previous articles and are comfortable with PHP.

Continue Reading...

When I compose a newsletter, I look at my well of possible materials–questions, links, blog posts, etc., and try to come up with a theme, if at all possible. When looking at these this time around, the ones that seemed most worth sharing immediately all focus on, well, me. For example, there’s the presentation I gave to Boston PHP: you can view the slides and the raw video of it. Or there are some articles that I’ve published online that you might like. And there’s the status on “The Yii Book”.

So this newsletter is far more me-centric than most, but hopefully it’ll be of use to you still. Because, presumably, you subscribed to this newsletter in the first place because you were interested in what I’m doing, thinking, interested in, and so forth.

Also, if you do have something you’d like me to write about, address, or answer in future newsletters, now is a good time to send that in, as my well of topics is getting shallow. I think my next newsletter is going to be on goals, if you have any thoughts or questions along those lines (e.g., technologies to learn, ways to learn, etc.). I’ve also got an upcoming newsletter planned on public speaking.

And, as always, thanks for your interest in what I have to say and do!

Continue Reading...
This entry is part 6 of 8 in the series Processing Payments with Stripe

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...
This entry is part 5 of 8 in the series Processing Payments with Stripe

In my previous post in this series, I covered how you create an HTML form for securely handling payments via Stripe. 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 much. 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 JavaScript to handle the client-side of that process. Note that this article assumes that you have read the previous article. And comfort with JavaScript and jQuery is required, too.

Continue Reading...