Docs

Payment Verification 

This is a Private Beta Release and is available only to users of Chargebee Hosted Pages using the In-App Checkout layout. To enable Verification Controls for your test  and live sites , please contact Chargebee Support .

Verification Controls provide a centralized way to manage payment flows within Chargebee, independent of any payment gateway. They help optimize your payment workflow by allowing you to filter out specific card payment methods that may not be ideal for recurring transactions or reject high-cost card types before they reach the payment gateway. By enforcing these verifications at the Chargebee level, you can prevent unnecessary processing costs.

Since this feature operates at Chargebee and is gateway-agnostic, it takes priority over any overlapping rules (such as smart routing rules) set at the gateway level for Chargebee checkout flows.

Benefits of using Verification Controls for your business 

This feature helps optimize revenue by reducing transaction failures, minimizing processing costs, and improving overall payment efficiency. Here???s how:

  1. Block Cards Based on Funding Type
    Preventing certain funding types, such as prepaid cards, from being used for billing can reduce transaction failures and unnecessary processing fees for your customers. This ensures a higher success rate for recurring payments and improves revenue stability.
  2. Decline Cards Based on Brand
    Restricting specific card brands can help lower transaction fees and reduce financial losses. Some card brands may have higher chargeback rates, leading to increased costs and operational inefficiencies. By blocking them, you can optimize payment processing and reduce disputes.
  3. Restrict Cards Issued from Specific Countries
    Blocking cards from certain countries helps prevent fraud, ensures compliance with legal requirements, and reduces cross-border transaction costs. This is particularly useful for businesses that need to adhere to regional regulations or minimize risks associated with high-fraud regions.

Supported Payment method 

  • Card payment method
Information

Currently, this feature supports card-based payments. We plan to expand more supported payment methods in future.

Supported variables for controlling verification 

The following are the variables supported for controlling verification for your payments:

  • Card Type
  • Card Brand
  • Card Issuing Country

Looking out for other variables?

Please raise a request for them here . We will consider them in our next iteration.

Limitations 

While Verification Controls provide significant benefits, there are some current limitations:

  • Limited to Card Payments: Verification Controls currently apply only to card payment method, and the outcome is a declined transaction during checkout.
  • Limited Availability and Future Expansion: This feature is currently supported only for In-App Checkout  within Chargebee Hosted Pages. Support for Full-Page Checkout  and other forms of Checkout is in progress and will be available in future updates.

Configuring Verification Controls in Chargebee 

Verification Controls enable you to create rules that determine which payments to decline or take other actions on. To get to the Verification page, follow these steps:

  1. Log into the Chargebee app .
  2. Go to Settings > Configure Chargebee > Payment Gateways.
  3. Click Manage Rules under Verification.

Creating a Verification Rule 

Once you???ve reached the Verification page, it???s time to create a verification rule. Creating a verification rule allows you to tailor your verification strategy based on your business needs. Verification Controls enable you to define multiple conditions within a single rule to achieve the desired outcome.

For example, a composite rule could be:
"~If the card brand is AMEX and the card issuing country is Cura??ao, then decline the payment~."

This flexibility helps you enforce specific payment policies, reduce costs, and minimize risks effectively.

Follow these steps to create a new verification rule:

  1. Go to the Verification page and

  2. Click Create Rule.

  3. Configure the Rule on the Create Rule page:

    • Enter a Rule Name.
    • Add the required conditions, such as Card Type, Card Brand, or Card Issuing Country.
    • The actionable outcome for the selected conditions is currently defaulted to Decline Payment.
  4. Verify the rule settings and click Publish to activate the rule.

Note
  • Multi-Selection for Filters: You can select multiple options for all supported filters. These selections function as an OR operator, meaning the rule will apply if any of the selected conditions are met.
    Example: If the Card Type is set to Prepaid and Debit, the rule will trigger if the card is either Prepaid, Debit, or both, resulting in a declined payment.
  • Composite Rules with Multiple Conditions: When multiple conditions are configured within a single rule, they function as an AND operator, meaning all conditions must be met for the rule to apply.
    Example: If the Card Type is set to Prepaid and the Card Brand is AMEX, the rule will only be enforced if both conditions match during evaluation.

The verification home page will reflect the published rules.

Note

While evaluating rules, If none of the rules match, then no action will be taken and the customer will move to the next step in the checkout process

Managing rules 

You can update, delete, disable, and sort the rules for Verification Control using the following operations:

  • View Rule Details: Click on the Rule ID to view the details of a configured rule.

  • Edit, Enable, Disable, or Delete Rules: Click the ellipsis icon next to a rule to perform these actions as needed.

  • Set Priority Order: When multiple rules overlap, the rule with the highest priority is executed first. To adjust priorities, click the hamburger icon next to a rule, drag it to the desired position, and publish the changes.

Need Help?
If you have any questions or need assistance with Verification Controls, please reach out to Chargebee Support .

Was this article helpful?
Loading…