This tutorial continues building a subscription-based website using Laravel and Recurly. Part 1 established the basic website structure, user roles, and registration. This part integrates Recurly for payment processing and subscription management.
Key Features:
Setup:
Recurly.js Integration: Include recurly.min.js
(from the Recurly.js build folder) in your Laravel application's public/js/libs
directory and link it in your layout. Similarly, add the Recurly CSS theme to your public/css/recurly/themes/default
directory and link it in your layout.
Recurly Account Configuration: Create subscription plans (Bronze, Silver, Gold) in your Recurly account, noting their plan codes ("bronze", "silver", "gold"). Enable API access and Recurly.js, recording your API key, private key, and subdomain. Create a recurly.php
configuration file in app/config/recurly.php
containing these credentials and your default currency (e.g., 'GBP').
Push Notifications: Configure Recurly push notifications, setting the notification URL to your-app-url/recurly
.
Signup Page (app/views/home/signup.blade.php
):
This page displays the available subscription plans. Consider fetching plan details dynamically from the Recurly API for up-to-date pricing. Links direct users to plan-specific registration routes (/user/register/bronze
, etc.). Custom CSS styles are provided to enhance the plan display.
Payment Processing:
Modified Registration Callback: The user registration callback now redirects to a payment page (/user/register/payment
) after creating the user account, storing the user in the session.
Payment Route (/user/register/payment
): This route generates a Recurly.js signature using the user's ID and selected plan. It passes this signature and other necessary data to the payment view (user/register.blade.php
).
Payment View (app/views/user/register.blade.php
): This view contains a div
with the ID "recurly-subscribe" where Recurly.js will inject the payment form. JavaScript code initializes Recurly.js, builds the subscription form using the server-side generated signature, and specifies success and failure URLs.
Confirmation Callback (/user/register/confirm
): This route receives the Recurly token after successful payment. It uses the Recurly library to fetch subscription details, assigns the appropriate role to the user, and removes the pending role.
Account Management:
Protected routes (/user/account
, /user/account/billing
) allow logged-in users to manage their account. The billing page uses Recurly.js to generate a billing information update form, similar to the signup payment process. A confirmation callback handles updates.
Push Notifications (/recurly
):
This route handles Recurly push notifications. The example provided shows how to process a canceled_subscription_notification
, revoking the user's role. Other notification types can be handled similarly.
Frequently Asked Questions (FAQs):
The provided FAQs cover common aspects of integrating Recurly with Laravel for subscription management, including handling different plans, renewals, failed payments, cancellations, refunds, discounts, and multi-tenancy. These answers give a comprehensive overview of the process.
The above is the detailed content of Creating a Subscription-Based Website with Laravel and Recurly, Part 2. For more information, please follow other related articles on the PHP Chinese website!