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

Product Updates


  • Release Notes

Getting Started


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

Implementing Chargebee


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

AI in Chargebee


  • Chargebee Agents
  • Chargebee Copilot
  • Chargebee MCP Server (Model Context Protocol)

Developer Resources


  • Developer Resources Overview
  • Articles and FAQ

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

Entitlements


  • Entitlements Overview
  • Features Overview
  • Feature Management
  • Managing Product Entitlements
  • Subscription Entitlements
  • Customer Entitlements
  • Grandfathering Entitlements
  • Articles and FAQ

Usage Based Billing


  • Understanding Usages
  • Setting up Usage Based Billing
  • Usage Alerts
  • Metered Billing
  • Articles and FAQ

Chargebee CPQ


  • Chargebee CPQ
  • Chargebee CPQ for Salesforce
  • Chargebee CPQ for HubSpot

Invoices, Credit Notes, and Quotes


  • 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
  • Pricing Table
  • Managing Payments with Chargebee.js
  • Mobile-Optimized Hosted Pages
  • Articles and FAQ

Site Configuration


  • Users & Roles
  • Custom Fields & Metadata
  • Approvals
  • 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

Multi Business Entity


  • Multi Business Entity Overview
  • Customer Transfer Overview
  • Articles and FAQ

Mobile Subscriptions


  • Overview
  • Omnichannel Subscriptions
  • Omnichannel One-Time Orders
  • Mobile Subscriptions (Legacy)

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
  • eInvoicing
  • Marketing
  • Stitch
  • Collaboration
  • Contract Management
  • Ecommerce Management
  • 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. Subscriptions
  3. Articles and FAQ
  4. Working with Subscriptions
  1. Billing
  2. Subscriptions
  3. Articles and FAQ
  4. Working with Subscriptions

My customer has added a payment method but they are not being charged automatically for payments. Why is this happening?

Problem Statement

This article helps you understand my customer has added a payment method but they are not being charged automatically for payments. why is this happening.This article also covers

How does Auto Collection work

Summary

The Auto Collection status (ON/OFF) determines whether your customers are charged automatically or not. There are two places in which the Auto Collection status can be defined - at the Customer level and at the Subscription level.

For subscriptions, the Auto Collection has 3 different status:

  1. Use Customer's default

If this is chosen, depending upon the Auto Collection status at the Customer level, the same status would apply to the Subscription as well.

  1. Always On

If set to Always On, irrespective of the Auto Collection status at the Customer level, the customer will still be charged automatically for any invoices associated to the subscription.

  1. Always Off

If set to Always Off, then customers will not be automatically charged for any invoice associated to the subscription, and payments will have to be recorded manually against the invoice(s).

Points to remember:

  1. At the customer level, the Auto Collection status will automatically change to ON when a payment method is added.
  2. Auto collection status at the subscription level overrides the customer level auto collection.
  3. It will not be possible to set the Auto Collection status as Always ON at the time of creating the subscription if there is no payment method available.

Solution

In order for the subscription Auto Collection to change to ON automatically when a payment method is added, the Auto Collection needs to be set to Use Customer's default, such that when Auto Collection changes to ON at the customer level, this happens for the subscription as well.

If Auto Collection at the subscription level is set to Always Off, even when a payment method is added, the customers will not automatically be charged via their payment method and any invoice raised for the subscription will remain in the Payment Due status, and the Collect Now option will need to be used to charge the customer's payment method.

Was this article helpful?