Customer Portal & Billing History
Integrate the Stripe Customer Portal, allowing users to manage their subscriptions and view billing history directly.
Customer Portal & Billing History is a free AI Powered SaaS: Stripe + Auth + Billing + Deploy lesson on CoddyKit — lesson 3 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the AI Powered SaaS: Stripe + Auth + Billing + Deploy learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.
Meet the Stripe Customer Portal
Welcome! In this lesson, we'll integrate the Stripe Customer Portal. This powerful tool empowers your users to manage their own billing information and subscriptions directly.
Think of it as a self-service hub for their payment details.
Empowering Your Users
The Customer Portal provides a secure, Stripe-hosted page where your users can:
- Update payment methods: Change credit cards or add new ones.
- Change subscription plans: Upgrade, downgrade, or cancel their subscription.
- View billing history: Access past invoices and receipts.
- Update billing information: Change their address or tax IDs.
This reduces support requests and improves user experience.
Quick Setup in Stripe Dashboard
Before writing code, you enable and configure the Customer Portal in your Stripe Dashboard. Go to Settings > Customer Portal.
- Customize your branding (logo, colors).
- Choose which actions users can perform (e.g., allow plan changes, cancel subscriptions).
- Set a return URL for when users finish.
These settings define the user experience.
Creating a Portal Session
To send a user to the Customer Portal, your backend needs to create a Portal Session with Stripe. This generates a unique, temporary URL for that specific customer.
The process is:
- User clicks a 'Manage Billing' button in your app.
- Your frontend calls your backend API.
- Your backend calls the Stripe API to create a
billing_portal.Session. - Stripe returns a URL, which your backend sends to your frontend.
- Your frontend redirects the user to that URL.
Backend: Generate Portal Link
Here's how your backend might create a Stripe Customer Portal session. Remember to replace YOUR_SECRET_KEY and customerId with actual values.
This example uses Java, but the logic is similar for other languages.
import com.stripe.Stripe;
import com.stripe.exception.StripeException;
import com.stripe.model.billingportal.Session;
import com.stripe.param.billingportal.SessionCreateParams;
public class Main {
public static void main(String[] args) {
// Set your secret key. Use your test key during development.
Stripe.apiKey = "sk_test_YOUR_SECRET_KEY";
// This customer ID should come from your database
// associated with the logged-in user.
String customerId = "cus_N5fK1ZlW2X3Y4Z"; // Example ID
String returnUrl = "https://your-app.com/settings/billing";
try {
SessionCreateParams params =
SessionCreateParams.builder()
.setCustomer(customerId)
.setReturnUrl(returnUrl)
.build();
Session portalSession = Session.create(params);
System.out.println("Customer Portal URL: " + portalSession.getUrl());
} catch (StripeException e) {
System.err.println("Error creating portal session: " + e.getMessage());
}
}
}Frontend: Directing Users
Once your backend provides the Customer Portal URL, your frontend simply redirects the user's browser to that link. This snippet shows a basic HTML button and JavaScript to handle the redirection.
In a real app, /api/create-portal-session would be your backend endpoint.
<!DOCTYPE html>
<html>
<head>
<title>Billing Portal</title>
</head>
<body>
<h1>My SaaS Dashboard</h1>
<p>Click below to manage your subscription.</p>
<button id="manageBilling">Manage My Billing</button>
<script>
document.getElementById('manageBilling').addEventListener('click', async () => {
try {
// Call your backend to get the portal URL
const response = await fetch('/api/create-portal-session', {
method: 'POST',
headers: { 'Content-Type': 'application/json' }
// You might send a user ID or token here
});
const data = await response.json();
if (data.url) {
window.location.href = data.url; // Redirect!
} else {
alert('Failed to get portal URL.');
}
} catch (error) {
console.error('Error opening portal:', error);
alert('Error connecting to billing portal.');
}
});
</script>
</body>
</html>Tailoring the User Portal
The SessionCreateParams used in the backend call offers customization options:
setReturnUrl(): The URL Stripe redirects the user to after they finish in the portal. Make sure it's a valid URL in your app.setConfiguration(): For advanced control over what features are available in the portal, overriding dashboard settings.
Carefully configure these to match your application's flow.
Listening for Portal Changes
When users make changes in the Customer Portal (e.g., update their plan, change payment method), Stripe emits webhooks.
You can listen for events like customer.subscription.updated or customer.source.updated to keep your application's database in sync. This was covered in the previous lesson!
Ensure your webhook handler can process these events to reflect changes in your app.
Testing Your Portal
Always test your Customer Portal integration thoroughly:
- Use Stripe's test mode API keys and test customer IDs.
- Simulate various user actions: updating cards, changing plans, viewing invoices.
- Verify that your application correctly redirects to and from the portal.
- Check that webhooks are received and processed correctly after portal actions.
This ensures a smooth experience for your users.
Portal Link Logic
You want to provide a 'Manage Billing' button in your SaaS application. When a user clicks it, what is the correct flow to open the Stripe Customer Portal?
Recap: Self-Service Success
Great job! You've learned how to integrate the Stripe Customer Portal.
- It empowers users to manage their billing and subscriptions.
- You create a session URL from your backend via the Stripe API.
- Your frontend redirects users to this secure, Stripe-hosted page.
- Webhooks keep your app updated on portal changes.
This integration significantly enhances user experience and reduces your support overhead.
Frequently asked questions
Is the “Customer Portal & Billing History” lesson free?
Yes — the full text of “Customer Portal & Billing History” is free to read here on the web, and the AI Powered SaaS: Stripe + Auth + Billing + Deploy course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the AI Powered SaaS: Stripe + Auth + Billing + Deploy course, upgrade to CoddyKit PRO.
What will I learn in “Customer Portal & Billing History”?
Integrate the Stripe Customer Portal, allowing users to manage their subscriptions and view billing history directly. You practise AI Powered SaaS: Stripe + Auth + Billing + Deploy with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.
Do I need any experience to start AI Powered SaaS: Stripe + Auth + Billing + Deploy?
No prior experience is required. AI Powered SaaS: Stripe + Auth + Billing + Deploy on CoddyKit is structured for beginners through advanced learners; this is — lesson 3 of 4, so you can start here or from the beginning and move at your own pace.
How long does the “Customer Portal & Billing History” lesson take?
Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.
Can I write and run code in this AI Powered SaaS: Stripe + Auth + Billing + Deploy lesson?
Yes. Every AI Powered SaaS: Stripe + Auth + Billing + Deploy lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.
All lessons in this course
- Subscription Management
- Handling Stripe Webhooks
- Customer Portal & Billing History
- Metered Billing & Usage-Based Pricing