Set a Credit Card Window

A Credit Card Window limits how long after an Invoice is issued a Customer can pay it by credit card. Once the window closes, card options disappear and the Customer has to use another method. Used as an early-pay incentive, it pulls payments forward and keeps card fees off Invoices that linger.

Important: Unlike the Credit Card Threshold, the window is not set per currency. One value governs every currency on the site.

How the window works

The window is a single site-wide setting, measured in days after Invoice issuance, and applies to remittance payments only, meaning payments made manually through the Admin UI or public Invoice pages. Setting one requires the permission described as manages product catalog, settings, and integrations.

When a Credit Card Window is configured:

1. Credit card payments are permitted only within the set number of days from the invoice issue date.
2. After the window expires:
   • Credit card payment methods are blocked in:
     • Admin UI invoice payment pages
     • Public invoice pages
   • API payment attempts using a credit card return an error saying the payment method is unavailable because of the window restriction.
3. The window is evaluated based on the invoice issue date, not the due date or terms.
4. The window is calculated based on full calendar days, not exact 24-hour periods. For example, if a credit card window is set to 1 day, the window extends until the end of the following calendar day (11:59 PM).

If no window is configured, the credit card window restriction does not apply.

Configuration

Credit Card Windows are configured:

• From the Invoicing Settings page.
• As a single site-wide integer value, not per currency or per payment gateway.
• As the number of days after invoice issuance that credit card payments are accepted.

Validation Rules

The window's enforcement follows these rules:

• Validation is enforced only for remittance payments.
• Invoices with collection_method = remittance are always subject to the window.
• Invoices under a subscription with automatic collection inherit that collection method, so the window never applies to them, regardless of how the payment is submitted.
• Enforcement happens at the payment attempt. If the payment date falls beyond the configured window, the credit card option is blocked.
• No payment_failure event is emitted, because validation runs before processing.
• The minimum value accepted for the setting is 1 day.

Examples

These examples show how the window applies against an invoice's issue date:

• Accepted case: A customer receives a Net 30 invoice on March 1. Your credit card window is set to 5 days. They pay by credit card on March 4, within the window, so the payment is accepted.
• Accepted case: A customer receives a Net 30 invoice on March 1 at 3:00 PM. Your credit card window is set to 1 day. The customer pays by credit card on March 2 at 11:00 PM. This payment is accepted because the window runs until the end of March 2, even though more than 24 hours have elapsed since the invoice was issued.
• Blocked case: A customer receives the same invoice but attempts to pay by credit card on March 12. Since this is outside the 5-day window, the credit card option is unavailable.

Best practices

Keep these practices in mind when setting a Credit Card Window:

• Set windows short enough to encourage early payment but long enough to be achievable for customers.
• Communicate the availability of credit card payments during the early period as part of your invoicing process.
• Consider combining Credit Card Window with Credit Card Threshold for full control over both timing and transaction size.
• Regularly review window settings to ensure alignment with your AR and cash flow goals.

Related information

To cap the Invoice amount payable by card, see Set a Credit Card Threshold.

For the full set of Site settings this sits among, see Understand Advanced Billing Site Settings.