On the Quick Admin Panel blog there's a tutorial posted showing you how to accept Stripe payments in your Laravel application using their "Stripe Checkout" functionality. This feature allows the Stripe platform to be the only one that handles the payment data and doesn't require you to store any information in your application.

Stripe is one of the most popular payment merchants for web, but information about Laravel integration is pretty fragmented, so I decided to write a really long tutorial about this topic.

We will cover: general logic how Stripe works, simple one-time payment integration, testing and production environment setup. [We will also cover] saving transaction data for future reference, recurring payments with Laravel Cashier [and] getting invoices data and PDF download.

The tutorial then gets into the use of the Stripe Checkout functionality on your site (after setting up an account) and the flow of the checkout and transaction. Then comes the Laravel portion of the tutorial. They show you how to set up a new application and create the view containing the required Stripe form. They show you where it integrate the keys specific to your application and how to test the implementation. Next they show how to handle the response back from Stripe that contains a token that can be used to identify the payment method in the future. This is used to charge the card via the Stripe SDK tools.

The tutorial finishes looking at Laravel Cashier to handle recurring billing and subscription plans. It shows you how to integrate this with your application and how to use it for payments and invoices.

The PHPBuilder.com site has a tutorial posted helping you integrate Stripe into your PHP application as a payment gateway service.

Stripe is a payment gateway that is becoming increasingly popular in the Web industry. It offers payment processing services, which can be easily integrated into your Web application using the Stripe API.

Although it is not free (2.9% + 30 cents per transaction), Stripe saves time and reduces cost in many ways: seamless integration and good documentation reduces the amount of time and development hours needed, while it offers complete control over sensitive data which saves hundreds of thousands of dollars that would otherwise be spent on ensuring PCI compliance.

They then show how to set up and use the PHP Stripe API package to create a simple checkout form to accept credit card information and use the stripe.js handling to send it directly to Stripe. Once the service receives it, it then makes a call back to your callback endpoint to create a token value for the transaction and customer. This callback then uses the API to make the actual charge using the token for the payment method and the customer information.

NetTuts.com has continued their series showing how to integrate a custom payment method into your OpenCart instance with part three of the series. In this tutorial they focus more on the frontend aspects, creating controller and model handling for the new method.

If you've been following along with this series, you should be familiar with the kind of file structure we set up for our custom payment method in the back-end. [...] We'll use a similar kind of file setup for the front-end section as well.

He starts with the controller, building a handler for the Custom method, doing some data filtering and getting the order information. He walks you through what each of the lines are doing and shows how to output the result back to a view. He also includes the model code needed for the custom payment method as well as language/template files to display the form needed to gather the necessary data.

On the NetTuts.com site today they've posted the first part of a series showing the integration of the BitPay bitcoin payment service into an OpenCart instance. In this first part they focus on getting some of the initial setup and administration handling set up.

In this series, we are going to look at building a Bitcoin payment system into our installation of OpenCart. Before we get started, I recommend that you practice the basic OpenCart module development if you are not familiar with how to build your own modules. Once done, you should have enough knowledge to continue with developing more advanced modules. In this series, that's exactly what we aim to do.

They start by having you download the BitPay API library and dropping it into the root directory of your OpenCart installation. Next they show you how to create an "Admin" controller with the data you'll need to pass into the view including data pulled from a model. They also create the admin view showing the current orders using bitcoin as payment, their status and options to change the speed of the API requests, status and toggling test mode on and off. Finally they include the code to save the results of the admin form submission and a bit of validation around user permissions and API key validity.

On KodeInfo.com there's a new tutorial posted showing you how to let your users pay with Bitcoin made possible using Coinbase, a Bitcoin wallet service, and BitPay, a payment gateway. Their example is a Laravel-based application.

Today we will learn how to integrate payment with bitcoins , we will integrate coinbase and bitpay to pay with bitcoins .

They walk you through the full process, including getting the accounts set up on the needed services:

• Setting up Bitpay
• Setting up Coinbase
• Creating migrations
• Views and Routes
• Config File
• Creating models
• Integrating Bitpay
• Integrating Coinbase

Each step is accompanied by screenshots or code, depending on what steps are needed. If you want to jump to the end, you can also grab the full code directly from GitHub.

On the SitePoint PHP blog there's a new tutorial posted showing you how to integrate Laravel and Stripe to make a simple system for selling downloads of software. Stripe is a developer friendly, easy to use payment system that helps you take and manage payments.

Digital goods are an increasingly valuable commodity. [...] In this article I'll show how you can implement a simple store selling digital goods using PHP along with Stripe, a payment provider who aims to make it easier than ever to take online payments since you don't need to set up special merchant accounts or deal with complex payment gateways.

He points you to the Stripe site to set up an account before getting started. With that in hand, They start in on the Laravel setup and project creation. He helps you make a "downloads" table to handle path to the file and price. Also included are the model for the Downloads and a "seeder" with some fixture data to work with. From there he shows how to make a simple home page and a "buy" page with a form for the payment information. The Stripe javascript library is then integrated and the response is handled. If it's a success, the user is then forwarded to another endpoint to download the file they paid for.

The SitePoint PHP blog has posted the second part of their series about making a subscription -based website with Laravel and Recurly (part one is here). Improving on the code from the previous part of the series, they create the interface with Recurly.

In the first part of this series we created the bare bones of a subscription-based website using Laravel. We also set the site up with roles, and granted a pending role to new users. We’re now at the point where we can perform basic registration, login, and logout. In this second part, we’ll integrate Recurly to set up our paid membership plans.

Using the Recurly javascript library and the PHP packages installed in the first part of the series, they show you how to set up the API and configure the script to connect with your account. They integrate this with the signup process and include the PHP (Laravel) code to handle the registration and the Javascript to make the Recurly call. There's also some code creating some of the management pages letting users update things like plan choice and billing information.

On NetTuts.com there's a new tutorial that shows you how to integrate an up and coming payment method into your site's flow - Bitcoin. The tutorial uses a combination of Javascript and a PHP backend and BIPS as the payment processor.

Bitcoin has definitely started to become more mainstream, and with its global reach and minimal fees, it is a payment method worth considering. In this article, we will take a look at what Bitcoin is, as well as how to start accepting them in your applications. [...] I'm not going to get into the specifics, but essentially each time a transfer of currency takes place, the money is signed with the two parties keys and then hashed, and these transactions are appended to the global log. This allows coins to be publicly traced back, and to see if the money really belongs to someone or not.

He starts off explaining what the whole bitcoin system is based on and some of the common advantages and disadvantages around it. He then gets into the actual application, creating a simple structure using the Slim microframework and a bit of HTML to make a simple payment site. The BIPS processor is used to handle the payment and the Mandrill service to send the confirmation emails. Curl requests are used to call the services, so you'll need it installed as a PHP extension to make their examples work.

On PHPMaster.com today there's a new tutorial that talks about PCI compliance with PHP applications and some of the technology you can use to help conform to its requirements.

In reality, PCI is a set of security guidelines drawn up by a consortium of credit card companies and industry security experts to govern how applications should behave when handling credit or debit card information. The card companies impose these standards on the banks who then impose them on those of us who operate e-commerce sites and the like. In this article we will dispel a couple of persistent myths about PCI, take a 20,000-foot look at what PCI encompasses, and then zero in on those requirements that are most closely associated with coding in general and PHP specifically.

He starts with some common myths about PCI (Payment Card Industry) compliance, including that it only applies to "the big guys" taking payments on the web. He then goes through some of the major points of the PCI requirements and talks about a few of them that specifically relate to the backend code side of things.

On the Symfony blog, there's two new posts highlighting some recent improvements to the Symfony2 framework - the addition of static page caching and payment validators:

• Static page caching support in the routing configuration
• Payment validators with docblock assertions, including error messages for failures.

These features are all a part of the upcoming Symfony 2.2 release that's planned to be moved in the "stabilization" status in early 2013. It should be able two months following that when the stable version will be released.