Online payments for RealGreen companies: portals, links, and processors

How do RealGreen companies take payments online? Through four layers: the Customer Assistant Websites portal, one-tap pay links sent by text or email, autopay on a stored card, and the processor underneath all of it. Which mix you run decides your AR, because every day between the invoice posting and the money arriving is a day you are financing your customers, and in our experience the biggest lever on that gap is not collections effort, it is payment friction. Get the stack right and the average invoice pays in days; leave it as mailed statements and a phone number, and you spend every fall doing archaeology on 60-day balances.

The four ways a customer can pay you

• Mail a check. Still real in this industry, still two weeks of float plus an envelope-opening job in your office.
• Call the office with a card. Convenient for the customer, expensive for you: a staff member keys the card, which drags your office into PCI scope and ties up a phone line to move money you were owed anyway.
• Log into the CAW portal. RealGreen's customer portal handles balances and payments and works well for the subset who enroll. The friction is the login: a password created two years ago is a real barrier for a $78 invoice.
• Tap a pay link, or do nothing because autopay ran. The modern layers, and where the rest of this post lives.

How does friction become AR days?

Walk one illustrative invoice through it, and plug in your own numbers. A mailed statement takes three days to arrive, sits on the counter for ten, and the check takes five more to come back and clear: 18 days if the customer is prompt, and prompt is not the mode. A pay link that arrives by text the evening the invoice posts, opening to a saved-card checkout, routinely gets paid the same week. Across 1,800 invoices a month averaging $92, pulling average days-to-pay from 24 down to 9 releases roughly $82,000 of cash from limbo at any given moment (1,800 × $92 × 15 ÷ 30 days). Same revenue, same customers: the only thing that changed is how many taps stood between them and paying you.

What is the CAW portal's role?

Keep it, brand it, and treat it as the self-serve home base rather than the whole strategy. The portal is where a customer checks history, sees programs, and manages their account, and portal payments are real payments. But adoption is the constraint: even well-run companies find that a minority of customers ever create the login. So the working pattern is portal for the enrolled, pay links for everyone else, with both writing back to the same customer balance. Pushing portal enrollment in the welcome series is worth doing; expecting it to solve AR alone is not. Measure adoption quarterly: portal logins per hundred active customers is the honest number, and it will humble you.

Why are pay links the workhorse?

A pay link is a URL that opens directly onto this customer, this balance, pay now: no login, no account creation, no typing an invoice number. Sent by text the day the invoice posts, it is the single highest-leverage payments upgrade available to a RealGreen company, and it slots into every rung of the collections ladder, from the friendly day-one notice to the 60-day sequence covered in our AR automation post. Two implementation details matter: links should be single-purpose and expire (a forwarded link should not expose an account), and payments must post back against the RealGreen balance automatically, because a pay link that creates manual reconciliation work has just moved the labor, not removed it. Neither detail requires anything exotic: we can connect RealGreen to pretty much any platform with an API, a Zapier connection, or a native connection, and payments are simply the lane where the wiring has to be real-time and careful. The full play is in the pay-by-text post.

The automation itself is simple. Trigger: an invoice posts in RealGreen and no autopay is on file. Action: a text that evening with the balance and a one-tap link, a polite nudge at day ten if unpaid, then a handoff to the AR ladder. Math: illustrative, plug in your own: if links move 30% of 1,200 monthly non-autopay invoices from chased to self-paid, at three minutes of office handling saved each, that is 18 staff hours a month returned, before you count the float on the cash itself.

Autopay is the endgame

Every payment method above still asks the customer to do something. Autopay retires the question: card on file, charged as invoices post, receipt by email. Companies that default new customers into autopay at signup and campaign the existing base toward it watch AR shrink into a rounding error, and there is a churn effect too, because a customer who never sees an invoice moment has one less annual prompt to reconsider you. Prepay is the cousin play: a customer who pays for the season up front removes AR from the picture entirely, and the prepay campaign playbook pairs naturally with card-on-file enrollment. The enrollment campaign, the incentives, and the honest objections are covered in the autopay adoption post; the short version is that new-customer default-on does more than any campaign to the legacy base.

Processors, rates, and PCI in plain English

Somebody moves the money, and they charge for it, so evaluate processors the way you would evaluate any subcontractor. Three practical notes. First, compare effective rate, total fees divided by total volume, rather than the headline number on the proposal, and ask for the complete fee schedule in writing: the small recurring line items are where proposals actually differ. Second, offer ACH bank draft alongside cards; it fits autopay well and many customers prefer it. Third, PCI compliance is mostly about what never touches you: hosted payment pages and stored tokens keep card numbers off your systems and your office out of the hard parts of scope, while keying cards over the phone puts them back in. The best processor decision is the one your office never thinks about again.

The takeaway: AR is not a personality trait of your customer base, it is an output of your payment stack. Portal for the enrolled, same-day pay links for everyone, autopay as the default destination, and a processor you chose on effective rate. Every tap you remove shows up as cash arriving sooner.

The rollout order

1. Measure your baseline this week: average days from invoice post to payment, and the share of customers on autopay. You cannot manage what you have not measured.
2. Turn on same-day pay links for newly posted invoices, by text where you have consent, email otherwise.
3. Flip new-customer onboarding to autopay-default with an opt-out, and add portal enrollment to the welcome sequence.
4. Run the autopay campaign to the existing base with a small, honest incentive.
5. Re-measure in 90 days and take the AR sequence off the office's plate entirely: that is what the automation layer is for.