Our Mission

At Chargent, we build trust through security, compliance, and transparency – protecting customer data while enabling innovation on every platform we support.

Certificates

Chargent by AppFrontier

Chargent takes security and compliance seriously. Click the link below to request our compliance documentation.

Salesforce

Chargent is native to Salesforce; therefore, Salesforce’s compliance documentation also applies to Chargent.

Gateways

Select your payment gateway in the picklist below to visit the related compliance webpage.

Payment gateway vs payment processor

Business Continuation Commitment

We are committed to ensuring uninterrupted payment processing for our customers. Our business continuity strategy includes redundant systems, secure data backups, and proactive risk management to minimize disruption.

Resources/FAQ

PCI DSS Certification and Compliance

Yes! Chargent is compliant with PCI DSS version 4.0.1. See the Certificates section above to request our PCI DSS Attestation of Compliance (AOC).

Visit the Certificates section above to request Chargent’s PCI DSS Attestation of Compliance (AOC).

PCI DSS compliance is validated annually.

While Chargent makes security, compliance, and transparency its goal, the responsibility is shared between our customers and us. Ensure you assess compliance for your specific use case, maintain best practices for staff access and training, review Salesforce security settings, and verify the security of other third-party tools.

Data Handling and Security

When using tokenization, Chargent doesn’t store credit card information in Salesforce, including the Card Security Code (CSC or CVC). Additionally, features like Payment Request and Take Payment let your customers make payments without a representative’s involvement.

In Transit: Chargent products are native to Salesforce; therefore, all data is transmitted directly from your Salesforce org to your payment gateway using Transport Security Layer (TLS).

At Rest: Chargent does not store sensitive cardholder data in Salesforce by default; instead, when supported by your gateway provider, a token is stored. Customers interested in Platform Encryption, Salesforce’s solution for data protection at rest, should visit Does Chargent support Salesforce Shield?

Yes! Chargent products offer the option to tokenize payments, provided it is available through your payment gateway. See Understanding Tokenization for more information.

Chargent products are native to Salesforce; therefore, all of Salesforce’s security features apply to Chargent. Further, our products are designed to utilize tokenization, ensuring sensitive cardholder information is never stored in Salesforce. Learn more by visiting Security and PCI Compliance.

Stored in Salesforce

  • Tokens

  • Non-sensitive Payment Information
    (Name, Address, Email, etc.)

Not Stored in Salesforce

  • Credit Card/Bank Account Number

  • Card Security Code (CSC or CVC)

When using tokenization. See Understanding Tokenization.