Credit Card Threshold

Maxio’s Credit Card Threshold feature allows SaaS businesses to control risk, manage large payment volumes, and reduce transaction fees by setting limits on the maximum amount payable via credit card. By restricting high-value remittance payments, you can avoid costly chargebacks, encourage lower-cost payment methods, and ensure compliance with internal financial controls.

Overview

Credit Card Thresholds are site-level, currency-specific limits that prevent credit card payments for Invoices that exceed a specified amount. This limit applies only to remittance payments—that is, payments made manually by users through the Admin UI or public Invoice pages.

Who Should Use This

Finance teams, billing managers, and risk officers at SaaS companies can use this feature to limit high-risk or high-fee transactions. This is particularly helpful when working with large Invoices or international Customers where payment methods and risk tolerances may vary.

Key Benefits

• Reduce risk of high-dollar credit card chargebacks.
• Encourage lower-fee payment methods for large Invoices.
• Avoid declined payments due to credit card limits.

How It Works

When a credit card threshold is configured:

• Credit card payments are permitted only if the Invoice’s due amount is less than or equal to the configured threshold.
• Credit card payment methods are blocked on:
  • Admin UI Invoice payment pages
  • Public Invoice pages
  • Public sign-up pages (if sign-up amount exceeds threshold)

If no threshold is set for a given currency, the credit card threshold restriction does not apply for that currency.

Configuration

Credit card thresholds are configured:

• Per currency, not per payment gateway
• From the Invoicing Settings page

If a currency is removed from your site, the threshold for that currency is also automatically removed.

Validation Rules

Validation is enforced only for remittance payments. This means:

• Invoices with collection method = remittance are always subject to the threshold.
• Invoices created under a Subscription with automatic collection method can still be paid manually using remittance, and would then be subject to the threshold.

Threshold enforcement occurs at the time of the payment attempt. If the Invoice’s due amount exceeds the threshold, credit card options will be blocked:

• The threshold comparison is based on the remaining due amount on the Invoice, not the original Invoice total.
• The option to use a credit card is blocked.
• No payment_failure event is emitted (validation happens before payment processing).

Warnings & Restrictions

• In the Admin UI, Subscription previews show a warning if the previewed amount exceeds the threshold and the collection method is remittance and the payment method is a credit card.

  “This Subscription exceeds the allowed threshold for credit card payments. Please update the payment method above or increase the credit card payment limit.”

• On public sign-up pages, users are blocked from selecting a credit card if the sign-up amount exceeds the configured threshold.

Example Use Cases

• Accepted case: A Customer has a $6,000 Invoice, and the USD credit card threshold is $5,000. The Customer pays $1,500 via ACH. The remaining due amount is now $4,500. The Customer can then pay the remainder using a credit card, since the due amount is under the threshold.
• Blocked case: A Customer tries to remit payment for a $6,000 Invoice, but the USD credit card threshold is $5,000. Credit card payment will be disabled.

Best Practices

• Set appropriate thresholds for high-risk or high-value currencies.
• Communicate alternative payment options (e.g., ACH, wire) for large Invoices.
• Regularly review and update thresholds to align with risk tolerance.