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

Introduction


  • Overview

Transactions


  • Get Started
  • Insights
  • Understand Payment Performance
  • Alerts

Settlements


  • Get Started
  • Reconciliation
  • Fees
  • Records

Data Security


  • Data Control
  • PII Data
  • Card Vaulting
  • Data Policies, Processes and Methods

Glossary


  • Standard Terms
  1. Reveal
  2. Data Security
  3. Card Vaulting
  1. Reveal
  2. Data Security
  3. Card Vaulting

Card vaulting

Reveal analyzes payment and settlement data from the Gateway Accounts you connect. For Transactions and Settlements, Reveal is designed to work with the card and payment-method attributes your processors expose for reporting (for example brand, expiry, and last four digits), not to collect full primary account numbers (PANs) from your shoppers at checkout.

This page explains how card-related data fits Reveal’s security model and how that relates to Chargebee’s PCI DSS compliance. For personal data choices beyond card attributes, see PII data. For encryption and hosting, see Data policies, processes, and methods.

Card data in Reveal

When you connect a payment processor, Reveal may ingest payment-method fields that the processor returns for the credentials and scopes you grant. Typical examples include card brand, funding type, expiry, and last four digits. Those fields help you segment authorization rates, declines, settlements, and fees without requiring full card numbers in Reveal analytics.

Reveal does not replace your processor’s vault. Cards used for live charges remain with your payment Gateway Accounts (or with the vault those Gateway Accounts use). Reveal reads outcomes and attributes so your payments and finance teams can investigate performance and reconcile money movement.

Chargebee and PCI DSS

Chargebee maintains a PCI DSS Level 1 Service Provider compliance program for environments that handle payment card data according to that standard. Reveal runs as part of Chargebee’s product portfolio and inherits Chargebee’s enterprise security controls for service data, including encryption in transit and at rest as described in Data policies, processes, and methods.

Storing or transmitting full card numbers expands PCI scope. Reveal’s Transactions and Settlements workflows are built around processor-sourced analytics data and truncated card identifiers where available, so you can gain observability without treating Reveal as a place to deposit full PANs.

Attestation of compliance

If you need Chargebee’s attestation of compliance (AoC) or related certification materials for vendor review, contact Chargebee or your Chargebee account team. They can provide the appropriate documentation for your evaluation.

Take the next step

  • Data control: What Reveal can ingest and how you control sources.
  • PII data: Non-payment personal data versus payment-related attributes.
  • Data policies, processes, and methods: Encryption, hosting, and security operations.
  • Chargebee PCI DSS: Chargebee’s public PCI compliance overview.

See also

  • Reveal overview
  • Get started with Transactions

Was this article helpful?