Skip to content
SAVE4545% off every plan.See the offer

Integrations & Setup GuidesPayment Processor Setup

Payment Processor Setup

Connect Stripe, PayPal, Square, Wise, QuickBooks Payments and nine more processors, and see what each can take: invoices, bookings or store orders.

VideoHow to Use QuickBooks Payments With Your CRM (Step by Step)
On this page· 33

Overview#

AutomateNexus CRM takes payments through your own payment processor accounts, so the money goes straight to you. Stripe is the main processor: it takes card payments for invoices, checkouts, forms, bookings and the storefront, and it is the only processor a checkout or a form is paid through online. Beside it, twelve other processors can take payment for invoices, paid bookings and store orders (QuickBooks Payments and Lemon Squeezy never take an invoice's payment): PayPal, Square, Razorpay, Mollie, Adyen, Authorize.Net, Braintree, 2Checkout, Worldpay, Wise (bank transfers), QuickBooks Payments and Lemon Squeezy (digital store items only). This guide covers what each processor can take, how to connect it, how your keys are checked, how the default processor works, and how to test before going live. Connecting one processor takes about ten minutes.

What Each Processor Can Take#

  • Stripe: invoices, checkouts under Commerce → Checkouts, forms with a payment field, paid bookings and store orders.
  • PayPal, Square, Razorpay, Mollie, Adyen, Authorize.Net, Braintree, 2Checkout, Worldpay and Wise: invoices, paid bookings and store orders. Their cards say Takes payment for invoices, paid bookings and store orders once switched on.
  • QuickBooks Payments: paid bookings and store orders. Its card says Takes payment for paid bookings and store orders. It never takes an invoice's payment: your invoices already go to QuickBooks Online through the QuickBooks sync, and a second QuickBooks invoice would be owed twice there.
  • Lemon Squeezy: digital store items only, in US dollars. Its rules forbid services and physical goods, so it never takes a paid booking. Its card says Takes payment for digital store items, in US dollars.

An invoice opens your default processor when it takes invoices, otherwise Stripe, otherwise the first processor switched on that takes them. A card saved for automatic payments is always saved through Stripe. If only Lemon Squeezy or QuickBooks Payments is switched on, the page warns you that invoices cannot be paid online.

Before You Start#

  • An owner or admin role in your AutomateNexus CRM organization. Other team members can see what is connected but cannot change it; a save by anyone else is refused with Only an owner or admin of this organization can change its payment settings.
  • A verified account with each processor you want to use, with your business details completed (needed for live payments).
  • For QuickBooks Payments: QuickBooks Online connected to AutomateNexus CRM first, with online payments switched on in QuickBooks.

Where to Find Payment Settings#

  1. In the sidebar, under Administration, click Integrations.
  2. Choose Payments in the left menu of the Integrations page.

The Payments section holds the Stripe card, the Other processors heading with a card for each of the twelve other processors, and the Accounting heading with the QuickBooks Online card, which sends invoices, payments and credit notes to your books and brings payments recorded there back.

The same cards appear in two other places, and all three edit the same settings:

  • Finance → Payment Processors, on its Processors tab, alongside Analytics (revenue and transactions by processor), Sync and Security tabs.
  • Scheduling → Booking, on the Payments tab of the booking settings.

Stripe#

Connecting Stripe#

  1. Log in to your Stripe Dashboard and open Developers → API keys.
  2. Copy your Publishable key (it starts with pk_live_, or pk_test_ in test mode) and your Secret key (it starts with sk_live_ or sk_test_, or rk_ for a restricted key). Keep the secret key confidential.
  3. In AutomateNexus CRM, open Administration → Integrations → Payments and find the Stripe card.
  4. Paste your keys into Publishable Key and Secret Key. The secret key is stored server-side and never shown again; leave the field blank later to keep the saved key.
  5. Click Check the secret key. AutomateNexus CRM asks Stripe whether it accepts the key, and tells you whether it works in live or test mode.
  6. Click Save.

Setting Up the Stripe Webhook#

The webhook is how Stripe tells AutomateNexus CRM a payment arrived. It marks an invoice, a booking, a form payment or a storefront order paid, and puts a refund made in Stripe on the invoice it paid. Without it, no payment is recorded, and the card shows Finish setup.

  1. Once the secret key is saved, click Set up the webhook on the Stripe card. AutomateNexus CRM makes the webhook in your Stripe account and keeps its signing secret for you.
  2. When it is done, the card says payments are recorded as they arrive, whether or not the payer comes back to the page, and shows Connected.

If you prefer to add it yourself, open Or add the webhook by hand, copy the Webhook URL, and add it in Stripe under Developers → Webhooks with these events: checkout.session.completed, checkout.session.expired, payment_intent.succeeded, payment_intent.payment_failed and charge.refunded. Then paste the endpoint's signing secret (it starts with whsec_) into Webhook Secret and click Save.

If the card says the webhook in your Stripe account is switched off, or is not sent every event payments need, click Set up the webhook again to put it right.

Test Mode Keys for Checkouts#

Under Test mode keys (optional), you can add your Stripe Test publishable key and Test secret key beside the live ones. Checkouts use them for test purchases, paid with Stripe's test cards, so no money moves. Add both.

Stripe for Checkouts#

Checkouts under Commerce → Checkouts take payments on the same Stripe account, with their own payment notices from Stripe, so there is no webhook to copy for them. Once your secret key is saved, the Checkouts part of the Stripe card says whether Stripe is ready for them; click Set up Stripe for checkouts to have Stripe send those notices.

Connecting the Other Processors#

Every other processor is set up the same way:

  1. Under Other processors, open the processor's menu and choose Set up (or turn its switch on).
  2. Fill in the fields the processor asks for (listed below). Each field shows where to find the value in the processor's own screens. Secrets are encrypted when saved and are not shown again.
  3. If the form shows an address under Where [processor] sends its payment notices, copy it and add it in the processor's dashboard as the form says. This records a payment even when the payer does not come back to the page.
  4. Click Save and switch on.

Key Checks#

When you save, AutomateNexus CRM tries your keys with the processor before switching it on. If the processor refuses them, the form stays open and says why in plain words, with where to find the right key. For example: Mollie refused the API key. Copy it again from the Mollie Dashboard (Developers, API keys). This way a typo shows up on the form, not when a customer's checkout will not open.

What Each Processor Asks For#

  • PayPal: Client ID, Client Secret and Environment (sandbox or live), from the PayPal Developer Dashboard under Apps & Credentials. Use the pair from the same environment you choose. Add the notice address as a webhook in your PayPal app with the PAYMENT.CAPTURE.COMPLETED and CHECKOUT.ORDER.APPROVED events.
  • Square: Access token, Environment (sandbox or production) and Location ID (optional). Leave Location ID blank to take payments at your main location. Saving checks the token with Square, and the card then says which location and currency payments go to. Square takes a payment only in its location's currency (USD, CAD, GBP, EUR, AUD or JPY). For Square's notices, add a webhook subscription for payment.updated in the Square Developer Dashboard with the address shown.
  • Razorpay: Key ID and Key Secret, a pair generated together in the Razorpay Dashboard.
  • Mollie: API Key, which starts with live_ or test_.
  • Adyen: API Key, Merchant Account, Environment (test or live) and Live URL prefix. The prefix is only needed for live payments: find it in the Adyen Customer Area under Developers, API URLs.
  • Authorize.Net: API Login ID, Transaction Key, Signature Key (optional) and Environment (sandbox or production). The notice address is set up for you when you save, once the account has a Signature Key.
  • Braintree: Merchant ID, Public Key, Private Key, Merchant account (optional) and Environment. Leave Merchant account empty to use your default account; each merchant account takes one currency. Braintree needs no notice address: the payer types the card into Braintree's own fields on the pay page, and the payment is recorded the moment it is charged.
  • 2Checkout: Merchant Code, Secret Key, Buy-link Secret Word and Environment. ConvertPlus must be on for your account. Add the notice address in the 2Checkout Control Panel under Integrations, Webhooks & API, IPN settings, with SHA2 as the hash.
  • Worldpay: Username, Password, Merchant entity and Environment (test or live). Test and live have their own credentials. Switch on payment events for the notice address in the Worldpay Dashboard.
  • Lemon Squeezy: API Key, Store ID, Product variant ID and Environment. Make one product in Lemon Squeezy (for example "Store order") at any price and copy its variant ID: each order is charged at its own amount through it. The notice address is set up for you when you save.

Wise Bank Transfers#

With Wise, a customer pays a booking or store order by bank transfer to your Wise business account. They are shown your account details and a reference to use.

  1. In Wise, make an API token with full access in your business account (Settings, Integrations and tools, API tokens).
  2. Under Other processors, set up Wise with the API token and Environment. Add the Business profile ID only when the token reaches more than one business profile.
  3. Click Save and switch on. Wise's notices are set up for you, and transfers are also looked for every 30 minutes.

Where Wise shows the payer's reference for your account, each transfer is matched to its booking or order by itself. Where it does not (this depends on your account's country), you are told which booking or order a transfer looks like. Open the booking or order, which says Waiting for a Wise transfer with the reference …, and click Transfer received once you see the money in Wise.

QuickBooks Payments#

QuickBooks Payments has no keys of its own: it takes payment through your QuickBooks Online connection. Each paid booking or store order becomes an invoice in your QuickBooks, paid online by card or bank transfer. It is recorded in AutomateNexus CRM once paid, and an invoice let go unpaid is voided.

  1. Connect QuickBooks Online first, on the QuickBooks Online card under Accounting. Until then the QuickBooks Payments card says Connect QuickBooks below, under Accounting, first.
  2. In QuickBooks, make sure online payments are on (Settings, Account and settings, Payments).
  3. Under Other processors, choose Set up on QuickBooks Payments. There is nothing to type. Click Save and switch on.

Payments waiting on a QuickBooks invoice are checked every 15 minutes.

The Default Processor#

When more than one processor is switched on, open the menu of the one you want and choose Make default. Its card then shows Default. The default decides:

  • Which processor a paid booking opens.
  • Which processor a store order opens when its products name none.
  • Which processor an invoice opens, when your default takes invoices.

It never changes forms or checkouts, which are always paid through Stripe. When another processor is your default, the page says so: Invoices, paid bookings, and store orders whose products name no processor open [processor], your default. A card saved for automatic payments is saved through Stripe. When your default cannot take an invoice (QuickBooks Payments), the page says which processor invoices open instead.

With several processors switched on and none the default, the page warns that which one a paid booking opens is not settled. Click Make Stripe the default in the warning, or make another processor the default.

Choosing a Processor per Product#

A product can name its own processor. Open the product under Commerce → Products and pick one in Payment Processor, or keep Use Organization Default. Items that name different processors are checked out one at a time. To sell an item through Lemon Squeezy, switch on Delivered digitally on the product (a download, a course or a licence); an order of digital items only can be paid through Lemon Squeezy.

Switching Off and Disconnecting#

Turn a processor's switch off to stop using it while keeping its keys (its card then says Set up, switched off). To remove it, choose Disconnect in its menu and confirm. Its saved keys are removed and invoices, paid bookings and store orders stop opening it. Payments already taken through it are not touched.

Using Payments in AutomateNexus CRM#

Invoice Payments#

  1. Create an invoice under Finance → Invoices. There is no processor to choose on the invoice: it is paid through your default processor when that takes invoices, otherwise through Stripe.
  2. When the client opens the invoice, its Pay button opens the processor's payment page. With Braintree they type their card on the invoice page itself; with Wise the invoice page shows your account details, the amount and the reference to send.
  3. The payment is recorded on the invoice once the processor confirms it: from its notice, when you added the notice address, or when the client comes back to the invoice. The invoice is marked paid when its payments cover it.

Booking Payments#

Under Scheduling → Booking, the Payments tab of the booking settings shows the same processor cards and holds the payment rules for paid bookings, such as deposits, refunds and tax. A paid booking opens your default processor. See Schedule & Booking.

Store Orders, Checkouts and Forms#

Store orders are paid through the processor their products name, else your default. Checkouts under Commerce → Checkouts are paid through Stripe. A form can carry a payment field that sends the visitor to Stripe when the form is submitted; see Embedded Payments on Forms.

Testing Payments#

Stripe Test Mode#

  1. Save test keys (pk_test_ and sk_test_) on the Stripe card; the card shows Test mode. To keep your live keys in place and test checkouts only, add the test keys under Test mode keys (optional) instead.
  2. Use Stripe's test card numbers:
    • Successful payment: 4242 4242 4242 4242 (any future expiry, any CVC)
    • Declined payment: 4000 0000 0000 0002
    • Requires authentication: 4000 0025 0000 3155
    • Insufficient funds: 4000 0000 0000 9995
  3. Make a test payment through an invoice's Pay online link, a test booking or a test checkout.
  4. Check that the payment appears in your Stripe test dashboard and that the invoice or booking is updated in AutomateNexus CRM.

Testing Other Processors#

Most other processors have a test setting in Environment: sandbox for PayPal, Square, Authorize.Net, Braintree, 2Checkout, Wise and Lemon Squeezy, and test for Adyen and Worldpay. Mollie uses a test_ API key. Save the processor with test credentials, book a test appointment on a paid event type or place a test store order, pay with the processor's test account or card, and check the payment is recorded.

Switching to Live#

  1. On the Stripe card, replace the test keys with your live keys and click Save; the Test mode label disappears. Click Set up the webhook again if the card asks, since live and test webhooks are separate in Stripe.
  2. For other processors, choose Change credentials in the menu, switch Environment to live or production, enter live credentials and click Save and switch on. For Adyen, add the Live URL prefix.
  3. Make a small real payment to check everything works.

Tips#

Troubleshooting#

Payments Not Appearing in the CRM#

  • If the Stripe card says Finish setup, the webhook is not set up yet: click Set up the webhook.
  • In Stripe, open Developers → Webhooks and check the event delivery log for failed attempts.
  • For other processors, check that the notice address from the setup form is added in the processor's dashboard.
  • For Wise, a transfer without the payer's reference waits for you: open the booking or order and click Transfer received.

The Processor Will Not Save#

  • Read the message on the form: it names the field and where to find the right value. Check that the keys come from the same environment (sandbox or live) you chose.
  • Fill in … means a required field is empty.
  • For QuickBooks Payments, connect QuickBooks Online under Accounting first.

A Store Order Will Not Check Out#

  • These items are paid through different processors means the cart mixes products that name different processors. Check them out one at a time.
  • If an item's processor is switched off, switch it on under Payment processors, or choose another processor for the product.
  • Lemon Squeezy takes digital items only. Turn on Delivered digitally for the product, or choose another processor for it.

Invoices Cannot Be Paid Online#

  • If the page says a processor cannot take an invoice's payment, so invoices cannot be paid online, switch on Stripe or another processor that takes invoices. Lemon Squeezy and QuickBooks Payments never take an invoice's payment.

Test Payments Work but Live Payments Fail#

  • Confirm you switched from test to live keys and environments.
  • Check that your processor account is fully activated (business verification complete).
  • For Stripe, check that a live webhook is set up as well as the test one.

Was this page helpful?

Last updated