Docschargebeedocs

HomeBillingPaymentsRevRecGrowthReveal
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

AI in Chargebee


  • Chargebee Agents
  • Chargebee Copilot
  • Chargebee MCP Server (Model context protocol)

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
    • Email logs
    • SMTP Configuration
    • Mail Merge Usage
    • Sending Manual Emails
    • DMARC Regulation
    • Domain Authentication
  • Branding
  • Configure Multiple Languages
  • Articles and FAQ

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
  • 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. Email Notifications
  4. Domain Authentication
  1. Billing
  2. Customers
  3. Email Notifications
  4. Domain Authentication

Domain Authentication

What is Domain Authentication

When you use Chargebee's SMTP server to send emails to your customers, you can improve email deliverability and compliance by enabling Chargebee to sign your emails with your DKIM (DomainKeys Identified Mail) signature through the Domain Authentication solution. This helps ensure your emails are DMARC-compliant, reducing the risk of delivery issues and building customer trust.

Why Should You Consider Domain Authentication

Enabling Domain Authentication for Chargebee SMTP is beneficial in the following scenarios:

  1. Strict or Quarantine DMARC Policy: Your domain's DMARC policy is set to strict or quarantine, and you want to ensure seamless delivery of your emails.
  2. Regional Hosting in Australia or Europe: Your site is hosted in Australia (AU) or Europe (EU), and you want advanced visibility into the delivery status of your emails. While US-based sites currently receive real-time notifications on delivery statuses such as Delivered, Opened, Dropped, and Bounced, enabling Domain Authentication will allow your AU or EU-hosted site to gain similar insights. Learn more about delivery status updates.
  3. Enhanced Email Deliverability for 'None' DMARC Policy: Your DMARC policy is set to none, but you want to send authenticated emails to improve deliverability, build credibility, and strengthen customer trust in your communications.
  4. Compliance with Google/Yahoo Email Regulations: Recent updates to Google or Yahoo's email-sending regulations have impacted your emails, and you need to adapt to ensure continued deliverability and compliance. Learn more about the regulations.

How to Onboard Your Site to Domain Authentication

Onboarding your site to Chargebee's Domain Authentication solution is straightforward. Follow these steps for a smooth setup:

Prerequisites

Before starting the onboarding process, make sure to:

  • Remove all sender profiles associated with the chargebee.com domain.
  • Remove sender profiles linked to other domains for which you do not have DNS access, since you will be unable to update their DNS settings.

Onboarding Steps

  1. Reach Out to Support Contact Chargebee Support to express your interest in onboarding your site to the Domain Authentication solution.
  2. Update DNS Records
    • Chargebee will send you an email containing the required DNS records for each domain in your site.
    • Add these records to your domain's DNS settings as specified in the email.
      image
  3. Verification and Confirmation
    • After updating the DNS records, reply to the email to notify Chargebee.
    • Chargebee will verify the DNS updates. Upon successful verification, you will receive a confirmation email.
      image

Post-Onboarding

After successful onboarding, Chargebee will automatically start signing your emails with your DKIM signature. This completes the process and enhances your email deliverability and compliance.

Here is a sample DNS record file shared by Chargebee:

image

If your domain already has a DMARC policy, you can skip adding the DMARC record again.

Was this article helpful?