iATS Payments

iATS Payments is a payment layer, not event registration software. It is relevant for nonprofits that need donation, dues, and event payment processing integrated into existing fundraising systems, but buyers should scrutinize rates, reporting, support, and contract terms before committing.

Quote-based; G2 reports no vendor-provided public pricing
Visit iATS Payments →
Tool Nutrition Label
Founded 1999
Headquarters Vancouver, Canada; operates as iATS Payments by Deluxe
Company Size Part of Deluxe Corporation; iATS product headcount is not separately disclosed
Funding Owned by Deluxe Corporation
Pricing Model Nonprofit merchant processing and gateway pricing based on payment methods, geography, volume, and partner setup
Free Trial No public self-serve free trial found
Contract Merchant processing agreement and gateway terms
Attendee Capacity Payment-volume based, not attendee-based; vendor cites over 16,000 nonprofit clients
Mobile App Yes; iATS Payments mobile app is shown in G2 media
Offline Capability No
Data & Compliance Supports merchant accounts in Canada, United States, United Kingdom, and European Union; exact data-hosting terms require contract review
Expertise Level Intermediate
Event Types
Donation ProcessingFundraising EventsMembership DuesRecurring GivingAuction PaymentsNonprofit Registrations
Key Integrations
Credit cards (Native) ACH and Direct Debit (Native) Aura donation forms (Native) Virtual Terminal (Native) Salesforce (Native) Nonprofit technology marketplace (API)
Support Channels
Support portalPhoneEmailFAQTechnology partner support
Best For
  • + Nonprofits that need a dedicated payment processor for donations, dues, and event payments
  • + Organizations using nonprofit CRMs, auction tools, or fundraising platforms that already integrate with iATS
  • + Teams that need credit card, ACH/direct debit, recurring payment, fraud, and PCI support
  • + Canadian, US, UK, or EU nonprofits comparing nonprofit-oriented merchant accounts
Not For
  • Organizers looking for event pages, registration forms, check-in, or ticket scanning
  • Teams that want transparent self-serve pricing before talking to sales
  • Small events that can use Stripe, PayPal, or a ticketing platform payment stack
  • Organizations unwilling to manage merchant account underwriting and contract review
Key Capabilities
Process major credit cards for nonprofit donations and payments
Support ACH and direct debit for one-time and recurring payments where available
Use virtual terminal, Aura donation forms, reporting, refunds, tokenization, encryption, and fraud controls
Work with nonprofit CRMs, fundraising platforms, auction software, and partner integrations
Support international merchant accounts in Canada, the United States, the United Kingdom, and European Union
Use PCI-oriented tools and Level 1 PCI/DSS certification claims
Honest Limitations

No Event Front End

iATS handles payments; it does not manage ticket inventory, attendee questions, event websites, badges, or check-in.

Pricing Is Not Public

G2 says vendor pricing is not provided publicly, so exact rates require a quote and contract review.

Reporting Experience Needs Testing

Independent review themes include both useful payment processing and complaints about reporting or support.

Integration Fit Matters

The best iATS setup is usually through a nonprofit CRM or fundraising platform that already supports it well.

Merchant Terms Carry Risk

Chargebacks, ACH returns, settlement timing, reserves, and account holds should be reviewed before launch.

Pricing Breakdown
Plan Price Details
Merchant processing Quote-based Rates depend on payment methods, volume, geography, and nonprofit setup
Gateway and partner integrations Quote-based or partner-dependent Costs can depend on CRM, auction, form, or fundraising platform integration

Cost at Common Event Sizes

100
attendees
Payment-volume and method dependent
Usually not bought for one event alone
500
attendees
Payment-volume and method dependent
Model card versus ACH/direct debit mix
1000
attendees
Payment-volume and method dependent
Request effective-rate examples by transaction type

Hidden Costs to Watch

  • ! Card, ACH, direct debit, refund, chargeback, and return fees
  • ! Monthly gateway, statement, compliance, or partner fees if included in contract
  • ! Integration setup and testing with CRM or fundraising software
  • ! Staff time for reconciliation and reporting

iATS Payments is infrastructure. It can be valuable when a nonprofit already has a CRM, auction tool, or donation platform that needs a nonprofit-oriented payment processor behind it.

Do not evaluate it like event software. The important diligence is the merchant agreement: effective rates, ACH support, reporting, settlement timing, chargeback handling, integration quality, and support.

Comparing this with other event tools?

Get a shortlist of the best-fit options for your event workflow.

Compare My Options
Questions to Ask the Vendor
  1. 1
    What are the exact card, ACH/direct debit, refund, chargeback, monthly, compliance, and gateway fees?
  2. 2
    Which of our CRM, auction, event, and donation tools have certified or supported iATS integrations?
  3. 3
    What settlement timing, reserve policy, underwriting requirements, and account hold rules apply?
  4. 4
    Can reporting reconcile donations, event payments, recurring gifts, refunds, and fees by campaign?
  5. 5
    What support response times are included for payment failures or event-day issues?
How we research tools

We research each tool by reviewing official documentation, pricing pages, and user feedback from Trustpilot, G2, and Capterra. If something's out of date or inaccurate, use the link below to flag it.

Suggest a correction →