ConnectBooster / BNG Payments: see who's on autopay (read-only)

ConnectBooster is the payments and billing portal a lot of MSPs use to collect recurring payments from their customers. Under the hood it runs on the BNG payment gateway (part of the NMI family of gateways). This connector reads that gateway — read-only, once a day — and hangs a short payment picture off each matching Current company: whether they have a stored payment method, whether autopay is actually being charged, and when a stored card is about to expire. It is strictly read-only. Current can see the gateway, but it can never charge a card, issue a refund, or change a payment method — it can never move money.

Once a day, Current makes a small set of read-only calls to BNG and refreshes a short payment summary for each customer with a stored method. It pulls the list of stored payment methods and roughly the last 90 days of charge activity, rolls that up per customer, and matches each one to a Current company. There is no per-transaction ledger and no raw copy of the gateway's payment record — just the rolled-up picture below. Sync now on the tile runs the same pull on demand.

Every customer lands in one of three plain-English states. Current works these out from what it can see in the gateway — it never asks you to set them by hand.

Open any company in the CRM and, once its gateway record is matched, a Payments card appears in the right rail — just after Money & renewals. It shows the autopay state at a glance, the stored method ("Visa •• 4242 · exp 08/26", with the expiry turning red when it's within about 45 days), the most recent charge with its date and amount, and the last-90-days total. If a company has more than one stored method, the card leads with the live one and notes the rest.

A stored card that expires while autopay is running means a failed charge and an awkward email to the customer. Current heads that off: when a stored card is within about 45 days of expiring, it opens a to-do for that company's account manager (or, if there's no account manager, a member of sales leadership) and rings the notification bell for the account manager plus sales leadership. The to-do names the company and reminds whoever owns it to get the card updated in ConnectBooster before autopay fails. It never shows the card number — just the last four and the month. Companies your PSA has marked inactive are skipped entirely — no to-do, no bell — and if a company goes inactive after a card to-do was already created, that to-do is cleared automatically (it drops off the owner's list and their Microsoft To Do).

The gateway identifies each customer by a stored vault record. Current matches each vault record to one of your Current companies automatically by normalized name — lowercased, with punctuation and Inc/LLC/Ltd-style suffixes stripped — and links it only when exactly one company matches cleanly. Anything it can't match confidently is left for you to map by hand.

• ＋Unmatched vault records appear on the ConnectBooster tile's mapping panel — press Map to pick the right Current company.
• ＋A company-named record usually matches automatically; a person-named record usually needs one hand-map. Both are normal.
• ＋Unmapped records still sync — their state and cadence are stored — but the Payments card only appears on a company once its record is mapped to it.

The autopay picture is also a campaign audience, so you can send an enrollment nudge to exactly the right customers. In the campaign audience builder, the "Autopay (ConnectBooster)" filter lets you target customers who are Not enrolled (no stored method on file) or Dormant (a method on file but nothing charging) — or either gap together. Combine it with your other filters as usual; the live recipient count updates as you go. If the ConnectBooster integration isn't connected, the filter simply resolves to zero recipients rather than emailing everyone by mistake.

The key Current needs is created inside the BNG gateway portal (the payment-gateway login behind ConnectBooster — if you're unsure of the URL, ask your ConnectBooster or BNG contact). Make it a read-only key: Current only ever reads, so the key it holds should only be able to read.

1. 1
   1 · Sign in to the BNG gateway portal

   Log in as an administrator to the gateway portal that sits behind your ConnectBooster account. This is the payment-gateway admin, not the customer-facing ConnectBooster billing site.
2. 2
   2 · Open Security Keys

   Go to Options ▸ Security Options ▸ Security Keys. This is where the gateway lets you mint API keys for outside tools.
3. 3
   3 · Create a new read-only key

   Create a new Security Key and give it read-only (query) access — not a full-access key. Name it so a future admin knows what it is, e.g. "Current (read-only)". A read-only key is all Current uses, and it keeps the blast radius to zero.
4. 4
   4 · Copy the key

   Copy the key value now. If the portal only shows it once, keep it safe until you've pasted it into Current in the next step; if you lose it, delete it in the portal and create a fresh one.

1. 1
   Open the ConnectBooster / BNG Payments card

   In Current's left sidebar open Integrations (it sits under Admin, so Tenant Admins have the link) and find the ConnectBooster / BNG Payments card.
2. 2
   Paste the Security Key

   Paste the read-only key you copied from the gateway portal into the Security Key field.
3. 3
   Press Test connection

   Current makes one live read against BNG's Query API to prove the key works. On success the key is stored server-side only — service-role-locked, so the browser never sees it again — and the daily read-only sync takes over from there. A bad or read-blocked key is rejected on the spot with the real reason. You can also press Sync now on the tile any time you don't want to wait for the nightly run.

Every request Current makes goes to BNG's Query API — the read-only side of the gateway — and passes through a guard that permits only that one endpoint. The endpoints that charge a card, issue a refund, or change a payment method are simply not reachable from Current's code, even by a bug. The read-only Security Key you created reinforces the same limit from the gateway's side. So the worst case here is a stale read, never a wrong charge: Current can show you the payment picture, and it can never touch the money.

On the tile itself you'll see the last sync time, how many stored customers Current found, and how many are still waiting to be mapped — the same at-a-glance health as every other connector.