How payments work in CiviCRM
CiviCRM is open-source software that churches, nonprofits and associations run on their own hosting. It comes with payment processors built in, including Authorize.Net and others, and more are added through extensions. A payment processor is the company that moves card money from a donor to your bank.
Authorize.Net is built in and supports recurring gifts. CiviCRM does not store card numbers itself. They live with the processor, which matters if you want to move.
What a switch involves
- Finding out which processor your site uses today, and whether it is a built-in connection or an extension.
- Recurring gifts. Because CiviCRM does not store card numbers, saved recurring gifts sit with your current processor. Ask whether they can be moved, or donors may need to sign up again.
- Whether your site needs a developer to set up a new connection, which is more likely with an extension.
- Your contract end date and any early cancellation fee.
Questions merchants ask
Can a church or nonprofit use its own processor with CiviCRM?
Often, if it is one CiviCRM supports. We check which ones apply to your site before you change anything.
What happens to recurring donations if we change processors?
The saved cards sit with your current processor, not in CiviCRM. Ask that processor whether it can move them. If not, donors would need to set up their gift again.
Where do I see what we pay in card fees?
Open your monthly processing statement and add up every fee. Divide that total by your card sales for the month. The result is your effective rate, the real percentage you pay after every fee. Our free statement review walks you through it.
See what you pay, for free
A person reads your statement with you and tells you what each fee means and whether a different processor is even possible with CiviCRM. There is no pressure to switch.