iATS Payments is a nonprofit-focused processor, and Contact Form 7 is one of the most common ways WordPress sites collect money. This guide connects the two: credentials, configuration, testing and going live.
For background on iATS and the other integrations available, see the iATS gateway overview for WordPress.
Before you start
- An active iATS account with your gateway credentials issued.
- WordPress running Contact Form 7, on a current version.
- HTTPS across the whole site.
- The iATS gateway plugin for Contact Form 7.
Step 1: Install the plugin
Upload the ZIP under Plugins → Add New → Upload Plugin and activate it. An iATS section appears in your Contact Form 7 payment settings.
Step 2: Add your credentials
Paste the credentials from your iATS account into the plugin settings, keeping test and live values clearly separated. Leaving test credentials in place at launch is the most common reason a campaign appears to run but collects nothing.
Step 3: Configure a Contact Form 7 payment form
Name the payment method something supporters recognize. Plain wording such as “Credit or debit card” performs better than the processor name. If you are enabling bank debit as well, label it clearly so people can choose deliberately.
Decide whether to offer recurring alongside one-off amounts. Presenting a monthly option next to a single gift reliably raises the share of supporters who choose it, and recurring income is worth considerably more over time than the same amount given once.
Step 4: Test every path
Switch to test mode and work through a Contact Form 7 payment form as a supporter would:
- A successful payment completes and is recorded with the right amount.
- A declined card returns a readable message rather than a blank page.
- A recurring setup creates the schedule you expect, if you enabled it.
- Receipts reach both the supporter and your own inbox.
- Abandoning part-way leaves no half-finished record marked as paid.
Test a decline on purpose. Most complaints after launch are not about failed charges but about confusing messages when a card is refused.
Step 5: Go live
Swap in live credentials, turn test mode off, then make one small real payment yourself and refund it. That single transaction proves the whole chain, from a Contact Form 7 payment form through to money arriving in your account.
Refunds and failed payments
Issue refunds from inside WordPress where the plugin supports it, so your records and the gateway agree. Refunding only in the iATS portal leaves WordPress showing the original amount, and the discrepancy surfaces later during reconciliation.
For recurring payments, make sure failure notifications reach a person who will act on them. A lapsed monthly gift that nobody notices is a supporter quietly lost.
Troubleshooting
The method is missing. Check the plugin is active, the gateway enabled, and that currency or country rules are not excluding the transaction.
Everything declines in test mode. Usually live credentials pointed at the test endpoint, or the reverse.
Payment taken but record unpaid. The gateway response is not reaching WordPress. Check host firewalls and security plugins that filter incoming requests.
Other iATS integrations
Using more than one plugin? The iATS overview covers every available integration, including GiveWP, WooCommerce, Gravity Forms, Ninja Forms, Contact Form 7 and Easy Digital Downloads.
Get the plugin
The iATS Payment Gateway for Contact Form 7 is available from wpayo with updates and support included.
Getting more from the integration
Once payments are working, a few configuration choices in Contact Form 7 make a measurable difference.
Ask for less. Every additional field costs you completions. Collect what you genuinely need to process the payment and thank the person; everything else can be asked for later.
Suggest amounts. A short set of suggested figures with one preselected outperforms an empty box, because it removes a decision. Include an open field for people who want to give something else.
Say what happens next. A confirmation that explains when the payment will appear on a statement, and under what name, prevents a real share of disputes from people who simply do not recognize the entry.
Keeping it working
A payment integration is not a set-and-forget job. Update the gateway plugin promptly, since payment plugins track API changes and an outdated one can stop working when a provider retires an endpoint. Re-test after any major Contact Form 7 or WordPress update, because checkout is the one flow where a regression costs money immediately. And watch for failures rather than waiting for complaints: a sudden run of declines usually points at a credential or configuration problem, not at unlucky supporters.
Frequently asked questions
Can we take recurring payments through Contact Form 7?
Recurring support depends on both the gateway and what Contact Form 7 offers, in some cases via an additional extension. Confirm both before advertising a monthly option, because promising it and then not delivering costs more goodwill than not offering it.
What happens if our site goes down mid-payment?
A payment already authorized at the gateway stands even if your site cannot record it. This is why reconciling gateway records against Contact Form 7 matters: it catches the small number of transactions that completed on one side but not the other.
Can we run a second payment method alongside it?
Yes, and it is worth doing. Contact Form 7 can present several methods, so an outage or an account problem does not stop income entirely.
How long until money reaches our account?
Settlement timing is set by your merchant agreement rather than the plugin, and commonly runs a couple of business days. Fees are usually deducted before payout, so a deposit will not match the day takings exactly.
Leave a Reply