Payments

Payments settings tell include GO which payment processor to use when you collect money from clients — credit card, ACH, or bank transfer. Enter credentials for either or both providers, then toggle Default on the one you want new payments to route through. The Pay button on invoices and payment links uses the default provider.

Two providers are supported: JustiFi (the default, fully integrated) and Global Payments. You can configure both — only the one marked Default is used for new charges.

Where to Find Payments Settings

From anywhere in include GO, click the Settings icon in the left sidebar. In the Settings sidebar that opens, under the Integrations & Data section, click Payments.

Navigation path: Dashboard → Settings → Integrations & Data → Payments

The Payments Settings Page

What you see on this screen

Each business unit has its own payment settings — changes here don't affect other business units.

Note: The Global Payments App ID and App Key are configured once at the application level (in .env), not per business unit. Only the Transaction Account ID is set here.

Using JustiFi

JustiFi is the default and easiest path — it's pre-integrated with include GO and designed around the accounting flow (invoices, payments, payouts, reconciliation).

Setting it up

1. Sign up for JustiFi and complete their merchant onboarding (underwriting, bank account, KYC). This happens outside include GO.

2. From your JustiFi dashboard, copy the Sub Account ID for this business unit. It looks like acc_ followed by a short string.

3. On the Payments page in include GO, paste the Sub Account ID into the JustiFi Sub Account ID field on the JustiFi card.

4. Toggle Default on the JustiFi card.

5. Click Save settings.

Once saved, the Pay button on AR invoices uses JustiFi to collect payment.

Using Global Payments

Pick Global Payments if you already have a Global Payments merchant account you want to use. Global Payments uses GP-API hosted card fields.

Setting it up

1. Make sure your administrator has set the Global Payments App ID and App Key in the application's .env file. These are application-wide credentials, not entered in this UI.

2. From the Global Payments developer portal, copy the Transaction Account ID for the app's transaction_processing account. It starts with TRA_.

3. On the Payments page, paste that value into the Transaction Account ID field on the Global Payments card.

4. Toggle Default on the Global Payments card.

5. Click Save settings.

Once saved, the Pay button on AR invoices uses Global Payments to collect payment.

How Payments Settings Connect to the Rest of the App

• AR Invoices — The Pay button on an invoice opens a form that charges the client through the default provider.

• Payment links — Emailed payment links route through the default provider.

• Cash & Credit ledger — Successful payments post to your bank account GL and are marked against the invoice.

• Reconciliation — Deposits and processor fees can be matched back to individual invoice payments.

Who Can Edit This Page?

Anyone with the Settings View permission can see the Payments page. Only users with the Settings Manage permission can change the provider, credentials, or default. By default this means Super Admin and Accountant.

Tips & Best Practices

• Use sandbox credentials in testing. JustiFi and Global Payments both provide test accounts. Run a few test charges before pointing real client invoices at production.

• One sub-account per business unit. If you run multiple business units in include GO, give each one its own JustiFi sub-account or Global Payments transaction account — don't share credentials across units.

• Rotate credentials if you suspect a leak. Generate a new Sub Account ID or Transaction Account ID in your processor's dashboard, paste it here, save.

• Don't paste credentials into chat or email. They're stored privately on the server and aren't exposed to the client portal — keep them that way outside the app too.

• Keep the provider's dashboard bookmarked. You'll visit it for disputes, chargebacks, payout timing, and reconciliation.

Common Questions

Which provider should I pick? JustiFi if you're starting fresh — it's pre-integrated and simpler. Global Payments if your business already has an account there.

Can I configure both providers? Yes. You can fill in credentials for both — but only the one marked Default is used for new payments. In-flight payments keep the provider they started with.

Can I switch the default later? Yes — toggle Default on the other card and save. The new provider takes over for any payment started after the save.

Do I need to configure a provider at all? Only if you want clients to pay online through include GO. If you only record payments that were collected outside the app (paper checks, external credit card terminals), you can skip Payments setup and record payments manually on invoices.

Where do I see processor fees? In the payment detail on the AR invoice, and in payout reports the processor sends. include GO records the gross amount and you'll reconcile fees when the payout hits your bank.

What if Pay is rejected? Most rejections are captured in the provider's dashboard (declined card, insufficient funds, etc.). The invoice stays Unpaid so the client can retry.

Is this the same as the QuickBooks payments integration? No — that's a separate thing. QuickBooks lives on the Integrations page (a sync to your accounting software). Payments here is the credit-card / ACH processor that collects money for invoices.

Where do the Global Payments App ID and App Key go? Those are application-level credentials set in .env by an administrator, not in this UI. Only the per-business-unit Transaction Account ID is entered on this page.

Related Topics

• AR Invoices — Where the Pay button appears

• Integrations — Accounting sync (separate from payment processing)

• Chart of Accounts — The accounts payments post to

• Roles & Permissions — Control who can edit Payments settings