Prefer to watch? See the short video Connecting a Payment Processor.
A processor is the company that actually takes the money: Stripe, Square, PayPal and more. You set one up once, in one place, and then use it anywhere on your website: donations, a form that asks for a payment, or your bookstore.
You will find it under Payments → Processors.
Connecting one
Click Connect processor, give it a name, choose the company you have an account with under Provider, and fill in the credentials it asks for. Then click Save changes. Each processor is shown on its own card, with its own logo, showing what it is used for and whether it needs attention, so the list reads at a glance.
Intuit QuickBooks connects a little differently from the others. Enter the Client ID and Client secret from your Intuit app and click Save changes; until then the page reminds you to "Save this processor first, then connect it to QuickBooks." Then open it again, click Connect to QuickBooks, sign in to QuickBooks and approve the connection.
Authorize.Net asks for three things: your API Login ID, your Transaction Key, and your Public Client Key. The first two are what authorize the charge. The third is what allows the card to be turned into a token in the shopper's own browser, so the card number never reaches your website at all, and without it a card cannot be taken. You generate it in your Authorize.Net account under Account → Security Settings → Manage Public Client Key, and their own instructions are here. The Public Client Key is public by design, and is meant to appear in a web page. Your Transaction Key is not, and should never be sent by email.
The company itself is fixed once a processor has been saved, because its credentials, its charges and its refunds all belong to that company. To move to a different one, set up a new processor.
If you do not have an account with any of them yet, open one with the company first. We cannot create a merchant account on your church's behalf: it is a financial relationship between your church and them, and it requires your own bank details and legal information.
Testing before you take real money
Every processor has a Mode: Live or Sandbox. Sandbox is the test account the company gives you, where a gift or an order can be put all the way through with a test card and no money moves.
One processor holds both sets of credentials. You do not set up a second Square for testing. Enter your live keys and your sandbox keys in the same processor and switch between them with Mode. Whichever set you are not using is kept rather than overwritten, so you can move back and forth as often as you like without fetching credentials again.
The page tells you which set you are looking at, in green for live and amber for sandbox, so a processor left in the wrong mode is visible before you leave the screen.
A test payment is recorded but never counted. It is listed with a sandbox label so you can find your own tests, and it is left out of your income totals and out of campaign progress bars. A test gift cannot inflate a thermometer on your website.
If a payment is ever recorded under the wrong one, you can correct it from the transaction itself under Payments → Transactions.
When you have finished testing, set Mode back to Live. A processor left in sandbox will not take real money.
What each one can do
They are not interchangeable. This is worth reading before you choose, because it decides what your website will be able to do:
| Processor | Donations | Store | Recurring giving | Confirms the payment |
|---|---|---|---|---|
| Stripe | Yes | Yes | Yes | Yes |
| PayPal | Yes | Yes | Yes | Yes |
| Square | Yes | Yes | Yes | Yes |
| Authorize.Net | Yes | Yes | Yes | Yes |
| Intuit QuickBooks | Yes | Yes | No | Yes |
| Tithe.ly | Yes | No | Yes | No |
"Confirms the payment" is the column most people overlook. It means the processor can tell your website, independently, that the money genuinely moved. Where it cannot (Tithe.ly), a gift is recorded as reported rather than as confirmed, and your website has to take the giver's word for it.
Tithe.ly is the other exception in the recurring column. It can take a regular gift, but the arrangement is held by Tithe.ly rather than by your website, so it is managed in their system and does not appear under Payments: Subscriptions.
Add the notification address (Webhook address)
Your website only finds out that money arrived, without anyone sitting at a screen, if the processor has been told where to send word. That matters most for a repeating gift, which the processor charges on its own schedule.
Stripe needs it for every payment, not only repeating gifts: without it, a Stripe payment cannot be confirmed. For PayPal, Square and Authorize.Net it is needed only if you take repeating gifts.
Each of these processors shows a Webhook address on its settings page. Copy it into that company's own dashboard, following the note underneath the box, which names the events to subscribe to. Stripe then gives you a signing secret to paste into Webhook signing secret on the same page. Authorize.Net also needs a Signature key, which you generate in your Authorize.Net account and paste into the same page: it is how your website can tell that a message claiming a gift was collected genuinely came from them.
Until this is done, a repeating gift is still set up correctly and the donor is still charged on time, but the payments it collects will not appear in your transactions and will not move a progress meter. With Stripe, no payment is confirmed until it is done.
If your website has not yet moved to its own domain, the box says so and names the permanent address to use instead. Register that one. The temporary address stops working on the day the site moves, and notifications sent to it are simply lost.
You can use more than one
A church is not limited to one processor, and many will want two: one that takes recurring giving, another that handles the bookstore. Under What it is used for on each processor, switch on Store checkout, Donations and forms, or both, and choose whether it is the Default for the store or the Default for donations (the Use for store and Use for donations buttons on its card do the same). The rest of the website then knows which to reach for without your having to choose every time.
Card details never touch your website
When somebody pays, their card details go from their browser straight to the processor. They do not pass through your church's website, and they are never stored on it. Site Manager receives back only a token, a reference the processor will honor, along with the last four digits for your records.
This is how every processor in the list works, and it is what lets a repeating gift be charged again next month without your website ever having held the card.
Taking a payment straight from a bank account
Authorize.Net can also take a payment directly from a checking or savings account, by eCheck, rather than from a card. On a large gift this usually leaves the church noticeably more of it, because bank transfer fees do not rise with the amount the way card fees do.
It is off until you switch it on, because eCheck.Net is a separate service you apply for through Authorize.Net rather than something every Authorize.Net account already has. Apply with them first, then turn it on from your processor's settings page.
Once it is on, a bank account is offered alongside the card in three places: on a donate section, on any form that asks for a payment, and on the link a donor follows to replace details on a repeating gift. It can be used for one-time and repeating gifts alike.
Bank details are handled exactly as card details are. The account and routing numbers go from the giver's browser straight to Authorize.Net and are turned into a token there. No bank number ever reaches your website.
When something is wrong, it says so
- A credential that has lapsed is named, along with what has expired, rather than reported as an unreadable setting.
- An address already collecting elsewhere: if you enter a receiving address that legacy donate sections on your site are already using, you are told. That is usually what you intended, but it is worth knowing before you save rather than after.
- A store that cannot charge tells you which processor is at fault and why, instead of failing at the checkout.
Three gateways have been retired
Clover, PayPal Payflow and PayPal Website Payments Pro are no longer supported. All three were long since retired by the companies themselves. If your store used one, we will have been in touch to move you across.
See Also: