Skip to content
CMS Max Documentation

Rate Limiting

How to protect your site from abuse by limiting form submissions, testimonial submissions, and payment failures per IP address, and by refusing forms submitted too quickly

Overview

The Security tab under Settings > Site Configuration contains rate limiting controls that protect your site from automated abuse. These settings limit how many times a visitor from the same IP address can perform certain actions within a 24-hour period.

Limits are counted per IP address and apply to every visitor.

Finding Rate Limiting Settings

  1. In the admin sidebar, go to Settings > Site Configuration.
  2. Click the Security tab.
  3. The Rate Limiting section groups these settings together.

Available Settings

Form Submissions

Limits how many times a visitor can submit a standard public form per 24 hours. This includes contact forms, event signups, and any other public forms — except testimonial submissions, which are counted separately (see below).

Only a submission that passes the form's checks counts toward the limit. A visitor who leaves a required field empty or mistypes an email address can correct it and try again without using up an attempt. A visitor who has already reached the limit is turned away before the form is checked, and before a card is charged on a Stripe card form.

A check against stored data, such as the sign-up form's "email already registered" check, runs only after the other checks pass, and that attempt counts. This keeps visitors from using the form to find out which emails are registered.

Password-protected pages share this setting but count differently: every password attempt counts, right or wrong. Testimonial submissions follow the same rule as forms, with their own limit (see below).

  • Default: 3
  • Set to 0 to disable (unlimited submissions allowed).

Testimonial Submissions

Limits how many testimonials a visitor can submit per 24 hours. Testimonials use their own counter, separate from the Form Submissions limit, so you can allow more (or fewer) testimonials than other forms without changing the general form limit.

  • Default: 3
  • Set to 0 to disable (unlimited testimonial submissions allowed).
  • This setting only appears when the Testimonials plugin is installed and activated.

Payment Attempt Failures

Limits how many failed payment attempts are allowed before the visitor's IP is temporarily locked out. This protects against card-testing attacks where someone tries stolen card numbers on your payment forms.

  • Default: 3
  • Minimum: 1 (cannot be disabled)
  • Maximum: 6

This setting counts failures returned by the payment gateway (e.g., a declined card or a rejected bank account). Errors caught before the payment reaches the gateway — such as missing required form fields — do not count.

Note: This protection applies to server-processed gateways (Authorize.Net, CardPointe, and Paya/ACH). Stripe card declines are handled in the visitor's browser and never reach this lockout. Instead, one visitor's IP address can start at most 10 Stripe card payments in 24 hours across all of your forms. After that, they see "Too many requests. Please try again later or contact us." This limit is fixed and has no setting. Stripe's own Radar fraud protection also screens every Stripe card payment.

How the Payment Failure Lockout Works

When a visitor reaches the failure limit, their IP is temporarily locked out. The lockout duration increases with each repeated lockout:

Lockout # Wait Time
1st 15 minutes
2nd 30 minutes
3rd 4 hours
4th 8 hours
5th 16 hours
6th+ 24 hours (maximum)

A successful payment resets the failure counter — the visitor is not penalized for past failures.

Tip: If a legitimate customer is locked out, an admin can clear the lockout via the server. Contact your developer for assistance.

Form Spam Protection

The Form Spam Protection section on the same Security tab sets how quickly a public form can be submitted.

Minimum Time Before Submitting

Bots submit forms faster than people can. A public form submitted sooner than this many seconds after the page loads is refused: the visitor sees "Please wait a moment, then submit the form again." and nothing is saved until they submit again.

  • Default: 2 seconds
  • Range: 0 to 10 whole seconds
  • Set to 0 to turn this check off.

Keep it low. A visitor who only has to click Submit, for example on a form already filled in from a link, can be that quick. A refused submission doesn't count toward the Form Submissions limit. Every form also has a hidden spam field, which this setting doesn't change; see Spam Protection.