Updated October 2026 for Custom Contact Forms 7.19 (free) and Custom Contact Forms Pro 1.5
Custom Contact Forms Documentation
Custom Contact Forms builds forms the WordPress way, and connects them to Mailchimp, Zapier and the rest of your tools for free. The Pro add-on turns those forms into payment forms, signed agreements, surveys and multi-step flows, without a full e-commerce stack.
Contents
- Getting Started
- The Integrations Page
- Email Marketing
- Webhooks (Zapier, Make, n8n)
- Spam Protection
- Payments Setup (Stripe)
- PayPal
- Product & Pricing Fields
- Total & Coupons
- Taking a Payment
- Conditional Logic
- Multi-Step Forms
- Signature Field
- Consent / Terms Field
- Survey & Rating Fields
- Address Autocomplete
- SMS Confirmations (Twilio)
- Form Templates
- PDF Receipts & Exports
- Entries, Dashboard & Weekly Summary
- Email Notifications & Receipts
- Headless Forms (Developers)
- Troubleshooting & FAQ
Sections marked Pro need Custom Contact Forms Pro. Everything else is in the free plugin.
1. Getting Started
Install the free Custom Contact Forms plugin from WordPress.org. For Pro, upload and activate Custom Contact Forms Pro (Plugins → Add New → Upload Plugin) using the zip from your purchase receipt email or the My Downloads page of your account. Pro requires the free plugin to be active. Pro 1.5 needs Custom Contact Forms 7.18 or newer, so when you update one, update the other.
Clicking Forms in the admin menu opens the Forms dashboard. From there:
- Forms → Templates creates a ready-made form in one click. Pro payment templates arrive fully assembled, including the payment field.
- Forms → Forms and Submissions lets you build from scratch or edit an existing form.
- Forms → Integrations is where you connect Mailchimp, spam protection and, with Pro, payments and other services.
Always test on a staging or test site before updating a live site, and purge any page cache after updating so visitors receive the latest scripts.
2. The Integrations Page
Forms → Integrations shows every integration as a card, marked Free or Pro, with its status (Connected, On, Off). Filter by category or by Free, Pro and Connected.
- Settings or Set up opens a panel for that service’s keys and options.
- Pro modules (Stripe, PayPal, Twilio SMS, Address Autocomplete) have an on/off switch. Turning one on opens its settings.
- Recent problems, at the bottom of the page, lists anything that failed, such as a deleted Mailchimp audience or a webhook URL that stopped responding, with the form and the reason.
3. Email Marketing
Add people who fill in a form to your email list. Mailchimp is free. Pro adds MailerLite, Brevo, Kit, ActiveCampaign and MailPoet.
Step 1: connect the service. On Forms → Integrations, open the service’s card and add your key:
| Service | Where to get the key | Adds people to |
|---|---|---|
| Mailchimp (free) | Mailchimp: Profile → Extras → API keys | An audience |
| MailerLite (Pro) | Integrations → API, generate a token | A group |
| Brevo (Pro) | SMTP & API → API keys, create a key | A list |
| Kit (Pro) | Settings → Developer, add a V4 API key | A Kit form |
| ActiveCampaign (Pro) | Settings → Developer, copy the API URL and API key | A list |
| MailPoet (Pro) | No key needed. Uses the MailPoet plugin on the same site | A list |
Step 2: choose a list for each form. Edit the form, open Form Settings, and under Email Marketing pick the service and the audience, group or list. Each form can use a different one. Then choose:
- Double opt-in: send a confirmation email first (recommended) or add people straight away. For MailerLite and MailPoet, this follows the confirmation setting in your account.
- Only add people who tick: to ask permission, add a Checkboxes field such as “Send me updates” and choose it here. Leave it unset to add everyone.
The form’s first Email field and first Name field are used. If someone isn’t added, the reason appears under Recent problems on the Integrations page.
MailPoet: people who unsubscribed from your MailPoet emails earlier, or whose address bounced, are never added back from a form. MailPoet’s own settings decide whether it sends a confirmation email, welcome emails and its new subscriber notice.
4. Webhooks (Zapier, Make, n8n)
Send each new entry to another service the moment it arrives. Edit the form, open Form Settings, and paste up to five URLs (one per line) under Webhooks.
Each entry is sent as JSON with the form name, the entry date and page, and every field’s label and value. Uploaded files and signatures are sent as links.
Click Send a test to send sample data. Tools like Zapier need a sample before you can map fields. Failed deliveries are listed under Recent problems on the Integrations page.
5. Spam Protection
Every form has built-in protection with nothing to set up: a hidden honeypot field, a time trap, IP rate limiting, disposable email blocking and an optional keyword blacklist. Blocked attempts are counted on the Forms dashboard.
For more, turn on one of these on Forms → Integrations:
- Cloudflare Turnstile or hCaptcha: add your site key and secret key (both free from their dashboards) and turn it on. Every form shows the check. If a visitor fails it, it resets and asks them to try again.
- Google reCAPTCHA: add a reCAPTCHA field to individual forms in the form builder.
- Akismet: if the Akismet plugin is set up on your site, turn on Akismet checks. Entries Akismet flags go to Forms → Spam instead of your entries list, and send no email. Choose Not spam to move one back, which also tells Akismet it made a mistake. Spam is deleted automatically after 30 days.
6. Payments Setup (Stripe) Pro
Payments run on Stripe. A free Stripe account is all you need. The plugin adds no transaction fees of its own; you pay only Stripe’s standard processing fees. One-time setup:
- Turn on Stripe Payments. On Forms → Integrations, switch on the Stripe Payments card. Its settings open.
- Add your API keys. In the Stripe Dashboard, open Developers → API keys. Copy the test and live publishable and secret keys into the settings, and choose your currency.
- Use test mode first. With Mode set to Test, use card number
4242 4242 4242 4242(any future expiry, any CVC) to place test orders, and4000 0000 0000 0002to test declined payments. Switch Mode to Live when you’re ready to accept real money. - Webhook signing secret. The settings panel shows the webhook address to add in Stripe and the event to send. Paste the signing secret Stripe gives you.
- Turn on customer receipts. In Stripe: Settings → Emails → enable “Successful payments.” The plugin passes each buyer’s email address to Stripe, and Stripe sends its receipt automatically. (Stripe only sends these in live mode by default.)
- Enable Apple Pay (optional). Apple Pay requires registering your domain once: Stripe Dashboard → Settings → Payment methods → Apple Pay → Add domain. Google Pay and Link need no registration.
Supported payment methods: cards, Apple Pay, Google Pay and Link. These all complete on the page. Delayed and redirect-based methods (bank debits, buy-now-pay-later) are intentionally not offered, because they can’t safely complete an on-page form.
7. PayPal Pro
- Turn on PayPal on Forms → Integrations. Its settings open.
- Add your app credentials. In the PayPal Developer Dashboard, create an app and copy its Client ID and Secret. There are separate sandbox and live credentials.
- Start in Sandbox. Run a full payment through with a sandbox buyer account before switching Mode to Live.
- Add a PayPal field to a form that already has a Product and a Total.
The buyer approves the payment in a PayPal popup without leaving your page, and the form submits once the payment completes. The amount is always recalculated on your server from the products on the form, and the entry is only saved once PayPal confirms a completed payment for that exact amount.
If PayPal holds a payment (for example, status Pending) or the amount doesn’t match the form total, you get an email and the problem is listed under Recent problems on the Integrations page.
Stripe and PayPal can both be turned on, but each form should use one: add either the PayPal field or the Stripe Card field, not both.
8. Product & Pricing Fields Pro
The Product field is how a form charges money. It has three pricing modes:
| Mode | What it does | Typical use |
|---|---|---|
| Single product | One item, one set price | Deposits, fees, merchandise |
| Multiple options | A dropdown where each choice carries its own price | Ticket tiers, donation levels, packages |
| Customer chooses amount | The visitor types the amount | Donations, invoice payments, tips |
Additional product settings:
- Quantity: let buyers order more than one, with optional minimum and maximum quantities.
- Minimum amount: for customer-chosen pricing, enforce a floor (for example $5). Enforced in the browser and again on the server, so it can’t be bypassed. Stripe’s own minimum charge is $0.50.
- Image & description: show a thumbnail and short description beside the product.
A form can contain any number of product fields (main items, add-ons, fee covers), and they all sum into the Total.
9. Total & Coupons Pro
The Total field displays a live order total that updates as visitors pick options, change quantities or reveal conditional products. The Coupon field accepts discount codes (percentage or fixed amount) that you define in the plugin’s coupon settings; the discount applies to the total instantly.
10. Taking a Payment Pro
Add the Stripe Card field (or the PayPal field) to any form with products. With Stripe, visitors see Stripe’s payment interface, with card entry and Apple Pay, Google Pay or Link where available, right in the form. The submit button becomes a payment button (“Pay $25.00”) that tracks the live total.
How a payment flows: the visitor submits, the plugin recomputes the total on the server (conditional visibility, quantities, coupons and minimums included), the payment is charged for that verified amount, and only then is the submission saved and marked PAID. A failed or abandoned payment never creates an order; a saved order always has a verified payment behind it.
On multi-step forms, place the payment on the final step (the templates model this).
11. Conditional Logic
Any field can be shown or hidden based on how the visitor answers other fields. Open the field’s settings → Conditional Logic, and build rules like:
- Show “Custom Amount” if “Donation Amount” is “Other”
- Show “Processing Fee Cover” if “Cover fees?” is “Yes”
- Show “What should we improve?” if “Recommend us?” is “No”
Comparisons: is, is not, greater than, less than, contains, combined with any or all. With checkboxes, every ticked box counts, so a rule like Show “Gift message” if “Extras” is “Gift wrap” stays true when other boxes are ticked too.
Fields hidden by conditional logic, on their own or inside a hidden section, are skipped when the form is checked and aren’t saved with the entry. A required field only has to be filled in when the visitor can see it.
With Pro, product fields work as rule sources too: a dropdown-priced product matches on the selected option’s label, and a customer-amount product matches on the number (enabling rules like “show X when the donation is greater than 100”). A priced field hidden by conditional logic is never charged, enforced in the browser and re-verified on the server.
12. Multi-Step Forms Pro
Drop a Page Break wherever a new step should start. Visitors get a progress indicator, Next/Previous navigation and per-step validation: required fields block advancing until completed. Required fields hidden by conditional logic are skipped. Use Section Break fields to add titled dividers within or across steps.
13. Signature Field
The Signature field is free. Visitors sign with a mouse, finger or stylus, and a Clear button lets them start over. Each signature is saved as an image with the submission, shown when you view the entry, and included in the notification email. Deleting the submission deletes the signature image too.
Mark the field Required to make signing mandatory. It works on phones and tablets, and the page won’t scroll while someone is signing.
With Pro, signatures appear as real ink in PDF receipts and submission PDFs.
14. Consent / Terms Field Pro
Present terms in a scrollable box with an agreement checkbox beneath. Built for proof:
- The saved value records which version of the terms was agreed to, for example
Agreed (terms 8d8723a1). - The full terms text is snapshotted with the submission, permanently. Edit your terms next month and every old entry still shows exactly what that person agreed to.
Pair it with a Signature field for waivers and contracts. The agreement templates arrive with both.
15. Survey & Rating Fields Pro
Survey builds a Likert-style grid: your questions down the side, an answer scale across the top. New Survey fields come pre-filled with the standard 5-point scale (Strongly disagree to Strongly agree); add questions and choices with the + and × controls. Answers save in readable form: Easy to get started: Agree; Support was responsive: Neutral.
Rating is a quick star rating (1 to 5) for single-question feedback. The number of stars is saved with the entry, so you can average it in a spreadsheet.
Slider lets visitors pick a number on a scale you set, with the current value shown beside it.
16. Address Autocomplete Pro
Every Address field on your forms gets a search box above it. Picking a suggestion fills in the street, city, state and ZIP below, all still editable by hand.
- In your own Google Cloud project, create an API key and enable two APIs on it: Maps JavaScript API and Places API (New).
- Restrict the key to your own website domain in Google Cloud. The key is visible in your page source, and an unrestricted key can be used by anyone and billed to you.
- On Forms → Integrations, switch on Address Autocomplete, paste the key and press Test key. It tells you exactly what is missing, if anything.
- Optional: limit suggestions to certain countries (two-letter codes such as
USorUS, CA) and change the search box label.
17. SMS Confirmations (Twilio) Pro
Text people a confirmation the moment they submit or pay, through your own Twilio account.
- On Forms → Integrations, switch on Twilio SMS.
- Add your Twilio Account SID and Auth Token (there are test and live versions) and the Twilio number to send from, for example
+16025551234. - Write the message. Use
{field_slug}to include an answer from the form, plus{site_name}and{form_title}. Keep it under 160 characters to stay a single text. - Choose the consent checkbox (strongly recommended, see below), the default country code (1 for US and Canada, 44 for the UK), and whether to text only after a successful payment.
Before you go live:
- Get consent. Texting people who did not agree to it is illegal in the US under the TCPA. Add a checkbox saying what you will send, keep it unticked by default, and choose it in the settings. No text is sent unless it is ticked.
- US senders must register for A2P 10DLC in the Twilio Console. Unregistered messages to US numbers get filtered out by the carriers.
- Twilio trial accounts can only text verified numbers. Add your own phone to the verified list before testing.
Twilio charges per message. If a text fails, the reason is saved on the submission and the form still works normally.
18. Form Templates
The free plugin includes five templates: Contact, Quote Request, Newsletter, Event Registration and Feedback. Pro adds 13 more, each a complete working form with the payment field included where relevant:
- Donation Form
- Product Order Form
- Paid Event Registration
- Service Booking Deposit
- Invoice Payment
- Tip Jar
- Course Signup
- Fundraiser with Fee Cover
- Liability Waiver
- Photo / Media Release
- Service Agreement + Deposit
- Rental Agreement
- Customer Satisfaction Survey Pro
Agreement templates include starter legal text with [Organization Name]-style placeholders. Replace those with your details before publishing, and have your own counsel review anything legally significant.
19. PDF Receipts & Exports Pro
- Automatic receipts: paid submissions attach a PDF receipt to the form’s notification emails, with the amount, a PAID stamp, the payment reference and the submitted details.
- Download any submission: open a submission’s detail view and click Download PDF. Signatures appear as actual ink, and paid orders include the payment box.
PDF generation uses your server’s standard PHP image libraries (present on all major WordPress hosts). If a signature image can’t be rendered on an unusual server, the PDF still generates with a note in its place.
20. Entries, Dashboard & Weekly Summary
- Every entry is saved in your WordPress database, so nothing is lost if a notification email goes astray. Export entries to CSV from the form, or import them under Forms → Import CSV.
- The Forms dashboard shows entries, form views, conversion rate and blocked spam for the last 7, 30 or 90 days or any custom range, with a chart and a per-form table. Only daily totals are stored, in your own database. Nothing about visitors is recorded.
- The weekly summary email arrives every Monday morning with the past week’s entries, views and blocked spam. Weeks with no activity are skipped. Change who receives it, or turn it off, under Forms → Settings → Weekly Summary, or with the link at the bottom of the email.
- With Pro, paid entries get a green PAID badge, and the detail view shows the amount, consent versions and the payment reference (for Stripe, searchable in your Stripe Dashboard).
21. Email Notifications & Receipts
Form notifications are configured per form in Form Settings → Notifications, with custom recipients, subject, from name, reply-to and body. For payment forms (Pro):
- You (the merchant) get the normal notification, sent only after payment is verified, with order details and the payment reference included, plus the PDF receipt attached.
- The buyer gets Stripe’s receipt automatically (see Payments Setup). You can also send them a form notification by adding a notification addressed to the form’s email field.
If emails aren’t arriving, use the email diagnostics on Forms → Settings to send a test email and view delivery failures.
22. Headless Forms (Developers)
Prefer your own markup? The free plugin exposes a REST endpoint that runs the full pipeline (validation, anti-spam, storage, notifications) against any frontend you build:
POST /wp-json/ccf/v1/submit
form_id, form_nonce (action "ccf_form"), ccf_field_{slug}...
Returns JSON: HTTP 200 with success, or 400 with per-field field_errors. Payment and multi-step features require the standard rendered form.
23. Troubleshooting & FAQ
The form is missing recent changes or shows old payment options. Your page cache is serving old scripts. Purge your caching plugin or CDN after every plugin update, and test in a private window to confirm.
Someone wasn’t added to my Mailchimp (or other) list. Check Recent problems at the bottom of Forms → Integrations for the reason. Also check whether the form uses “Only add people who tick” and the person left the box unticked, and whether double opt-in is waiting for them to confirm by email.
My webhook isn’t firing. Use Send a test in the form’s settings, then check Recent problems on the Integrations page. The receiving service must accept POST requests with a JSON body.
A real message ended up in spam. Open Forms → Spam and choose Not spam. The entry moves to its form’s entries and Akismet learns from the correction.
Apple Pay doesn’t appear on iPhones. Register your domain in Stripe (Settings → Payment methods → Apple Pay). It also only appears in Safari on devices with a card in Apple Wallet.
“Minimum is X” when submitting. The customer-chosen amount is below the minimum you set on that product, or below Stripe’s $0.50 floor.
A conditional product isn’t charging. That’s by design if the field is hidden: hidden priced fields never charge. Check the field’s rules if it should be visible.
A PayPal payment shows as Pending. PayPal is holding it. You’ll get an email about it, and it’s listed under Recent problems. Check the payment in your PayPal account before fulfilling the order.
Payment succeeded in Stripe but I want to find the order. Every submission stores the payment reference (pi_...). Search it in Stripe, or match the payment’s amount and time to the submissions list.
Address suggestions don’t appear. Open the Address Autocomplete settings and press Test key. The usual causes are a missing API (both Maps JavaScript API and Places API (New) must be enabled) or a website restriction that doesn’t include your domain.
SMS confirmations aren’t arriving. Check the reason saved on the submission. Common causes: the consent box wasn’t ticked, a Twilio trial account texting an unverified number, or US messages blocked because A2P 10DLC registration isn’t finished.
A form won’t submit because of a field the visitor can’t see. Update to Custom Contact Forms 7.19.1 or newer. Fields hidden by conditional logic are now skipped when the form is checked.
A required signature or consent isn’t blocking submission. Confirm the field is marked Required in its settings, and hard-refresh the form page (cache again).
Still stuck? Contact support.