New in Chargebee: Explore Reveal and understand your payment performance end-to-end.Try Now
Docschargebee docs
HomeBillingCPQPaymentsRevRecGrowthReveal
Support

Product Updates


  • Release Notes

Getting Started


  • Overview
  • Chargebee Billing Data Centers
  • Object Relationship Model
  • Understanding Sites
  • Developer Resources
  • Chargebee Tech Glossary
  • Articles and FAQ

Implementing Chargebee


  • Implementation Guide
  • Go-live Checklist
  • Articles and FAQ

Agentic AI


  • Chargebee Copilot
  • MCP Servers

Product Catalog


  • Product Catalog Overview
  • Coupons
  • Articles and FAQ

Subscriptions


  • Working with Subscriptions
  • Billing
  • Orders
  • Articles and FAQ

Customers


  • Managing Customers
  • Account Hierarchy
  • Email Notifications
  • Branding
  • Configure Multiple Languages
  • Articles and FAQ

Invoices and Credit Notes


  • Invoices
  • Credit Notes
  • Quotes [Legacy]
  • Transactions
  • Articles and FAQ

Taxes


  • Overview
  • Configuring Taxes
  • Country-specific Taxes
  • Articles and FAQ

Hosted Capabilities


  • Overview
  • Hosted Checkout
  • Hosted Self-Serve Portal
  • Hosted Pages Features
  • Additional Hosted Pages
  • Payment Components
  • Managing payments with ChargebeeJS
  • Mobile-Optimized Hosted Pages
  • Articles and FAQ

Site Configuration


  • Users & Roles
  • Custom Fields & Metadata
  • Mandatory Fields
  • File Attachments & Comments
  • Advanced Filter Options
  • Multicurrency Pricing
  • Multi-decimal Support
  • Configuring Reason Codes
  • Events and Webhooks
  • API Keys
  • Time Zone
  • Time Machine
  • Transfer Configurations
  • Articles and FAQ

Reports and Analytics


  • RevenueStory
  • Home Dashboard
  • Frequently Asked Questions
  • FAQs for Classic Reports Sunset
  • Articles and FAQ

Integrations


  • Sales
  • Customer Support and Success
  • Finance
  • Tax
  • Marketing
  • Stitch
  • Collaboration
  • Contract Management
  • Order Management
  • Mobile Subscriptions (Legacy)
  • Other Integrations
  • Articles and FAQ

Data Privacy & Security


  • Two Factor Authentication
  • SAML Single Sign-On
  • System for Cross-Domain Identity Management (SCIM)
  • EU-GDPR
  • Consent Management
  • Personal Data Management
  • Compliance Certificates
  • HIPAA Guidelines
  • PCI Recommendations and Integration Types
  • Articles and FAQ

Data Operations


  • Bulk Operations
  • Migration
  • Articles and FAQ
  1. Billing
  2. Customers
  3. Articles and FAQ
  4. Managing Customers
  1. Billing
  2. Customers
  3. Articles and FAQ
  4. Managing Customers

Can I restrict having one subscription per customer?

Problem Statement

You want to know if you can restrict having one subscription per customer.

Solution

Summary

You can restrict users from creating multiple subscriptions and customer records with the same email address using Chargebee's checkout page in the UI or the API.

If you are using Hosted Pages: Disable "Allow customers to have multiple subscriptions" and make "Email" field mandatory in the Checkout & Self-serve portal. Refer to this article for a detailed explanation.

If you are using APIs:

To restrict users from signing up more than 1 subscription,

  1. On your sign up page, collect the customer's email ID as a primary check.

  2. Once the customer submits their email ID, use our List Customers API, with the email[ ]filter parameter to check for any customer record in Chargebee with the same email ID.

  3. Now that you have the customer ID, use our List Subscriptions API, with the customer_id[ ]filter parameter to check for any subscription record in Chargebee associated with the customer ID.

Note

You can also use the status filter parameter to fetch only the active subscriptions.

  1. If the response returns with a subscription ID, then the customer already has an active subscription.

    1. You can display a message on your web page, informing the customer on the same and stop them from accessing the checkout.
  2. If there are no subscription IDs with a response then the customer has no active subscription and they can access the checkout page.

The above workflow requires development effort at your end. Contact support to know more.

Was this article helpful?