The Card Terminal Problem at Scale
When you have five field agents, card terminals feel manageable. You buy five devices, hand them out, and everyone collects payments on-site. Simple enough.
When you have 20, 50, or 100 agents, the whole thing falls apart.
Start with the monthly cost. A card terminal with mobile connectivity runs £20 to £30 per month per device. At 50 agents, that's £1,000 to £1,500 a month just for the hardware rental. That's £12,000 to £18,000 a year before anyone has processed a single transaction.
Now add the operational headaches.
Devices break. Agents drop them, leave them in vans overnight in winter, spill coffee on them. A replacement takes days to arrive. During that time, your agent either can't collect payment on-site or has to tell the customer "we'll send an invoice." That invoice might take 30 days to get paid instead of getting the money on the spot.
Devices go missing. They end up in glove compartments, under seats, in toolboxes. When an agent leaves the company, getting the terminal back becomes a treasure hunt. You're still paying the monthly fee while it sits in someone's spare room.
Every terminal needs charging. That means every agent has to remember to charge their device overnight, keep a cable in their van, and actually do it. On a Monday morning after a busy weekend, you'll have agents turning up to jobs with dead terminals.
Then there's the signal problem. Card terminals rely on mobile data or Bluetooth paired with a phone. Try taking a payment in a basement, a lift shaft, a server room, or a rural farmhouse. The signal drops and the payment fails. Your agent is standing there with an apologetic face and a customer with a card in hand.
Finally, reconciliation. Every terminal generates its own transaction log. With 50 terminals across 50 agents, matching payments to jobs means pulling data from multiple sources and cross-referencing manually. Your accounts team spends hours on this every week.
Card terminals were built for shops with a fixed counter and a power socket. Strapping that model onto a mobile workforce of 50+ people is fighting against the design of the product.
How Payment Links Replace Card Terminals for Field Teams
The alternative is simpler than most operations managers expect.
Your field agent finishes a job. They open their phone, tap a button in your job management system (or a simple web app), and send the customer a payment link via SMS. The customer taps the link, sees a branded checkout page with the job details and amount, and pays with their card or Apple Pay/Google Pay.
Payment confirmed. Matched to the job. Done.
No hardware. No charging cables. No mobile signal dependency for the payment itself, because the customer completes the payment on their own phone using their own data or wifi connection. Your agent just needs enough signal to send a text message.
The payment is processed through your existing payment gateway. Shuttle works with 40+ PSPs, so you can bring a compatible provider and keep your existing merchant account, rates, and relationship. Nothing changes on the processing side. You just change how the payment gets collected.
At $49 per live instance per month for Shuttle's Links Checkout, the cost difference at scale is significant. But the real savings come from eliminating the operational overhead: no device management, no replacements, no charging logistics, and no manual reconciliation.
SMS payment links work best when:
The agent wants to send the payment request before arriving, so the customer can pay while the agent is still en route. Useful for call-out fees and deposits.
The job is done and the agent needs to move to the next appointment. Send the link and leave. The customer pays in their own time.
The customer isn't present. Think: landlords who aren't on-site for property maintenance, or office managers who've left for the day by the time an evening job finishes.
You want a paper trail. The SMS with the payment link serves as a record of the amount requested.
CRM and Job Management Integration
Payment collection gets dramatically better when it's wired into the system your agents already use to manage their jobs.
Here's what the workflow looks like when your field service management (FSM) or CRM system is connected:
Agent marks the job as complete in the app
System automatically generates a payment link for the quoted amount
Link is sent to the customer via SMS (automatically or with one tap from the agent)
Customer pays
Payment status updates in the job record
Accounts team sees paid/unpaid status across all jobs in real time
No manual data entry. No copying amounts between systems. No end-of-week reconciliation sessions.
Shuttle's API integrates with any system that supports webhooks or API calls. That covers the major field service platforms:
ServiceM8 and Jobber for trade businesses
Housecall Pro and ServiceTitan for home services
Method CRM and Salesforce for custom field service setups
Fergus for trade contractors in the UK and ANZ markets
If your FSM software supports Zapier or Make (formerly Integromat), you can connect it to Shuttle without writing any code. A typical Zapier workflow: when job status changes to "complete," create a payment link via Shuttle's API and send it to the customer's phone number from the job record.
For larger operations with in-house dev teams, Shuttle's REST API lets you build payment collection directly into your own workflows, dispatch systems, or custom field service apps. As a Payment Layer that sits between your software and your PSP, Shuttle handles the payment processing and multi-gateway routing, which limits your PCI scope, while your system handles the business logic.
Cost Comparison: Card Terminals vs Payment Links
Card Terminals | Payment Links (Shuttle) | |
|---|---|---|
Hardware cost | £0-100 per device upfront (depends on provider) | None. Agents use their existing phone |
Monthly fee | £20-30/month per terminal | $49 per live instance per month for Links Checkout |
Replacement cost | £50-100 per broken/lost device + downtime | N/A |
Charging/maintenance | Daily charging, cable management, firmware updates | None |
Signal dependency | Agent's terminal needs mobile data signal to process | Customer's own phone/wifi handles the connection |
Reconciliation | Manual. Pull data from each terminal separately | Automatic. Payments matched to jobs via API |
CRM/FSM integration | Limited. Most terminals don't talk to your job system | Full. API, webhooks, Zapier/Make support |
Scalability | Linear cost increase. 50 agents = 50 terminals + logistics | Add users with no hardware to ship |
Branding | Terminal shows your PSP's branding | Checkout page with your logo, message and custom domain |
The less obvious saving is admin time spent reconciling terminal payments to jobs. When payments auto-match to job records, most of that reconciliation work goes away.
What About Customers Who Want to Tap Their Card?
This is the most common objection, and it's worth addressing directly.
Some customers will ask "can I just tap my card?" when the agent is standing in front of them. It's a fair question. Contactless payments are familiar and fast.
Here's the reality: the vast majority of customers are perfectly happy tapping a payment link on their phone. They do it every day when they buy things online, pay parking, or split a restaurant bill. A branded checkout page with the job details, amount, and Apple Pay/Google Pay as a payment option is just as fast as tapping a card.
For the small percentage of customers who genuinely prefer card-tap over everything else, you don't need to equip every agent with a terminal. One or two backup terminals kept by team leads or in supervisor vehicles will cover the edge cases.
The question to ask is: does a small minority's preference justify your whole team carrying hardware?
Most operations managers, once they see the numbers, decide it doesn't.
Security and Compliance
Sending payment requests via SMS is actually more secure than handing a card terminal to a field agent.
With card terminals, the agent physically handles the customer's card. Even with chip-and-pin or contactless, the card leaves the customer's hand momentarily. That's a trust issue, particularly in a customer's home.
With payment links, the customer's card details never go anywhere near the agent's phone. The customer enters their payment information directly on a PCI DSS Level 1 compliant checkout page hosted by Shuttle. Card data is processed by your chosen PSP through Shuttle's secure infrastructure.
No card numbers are stored on the agent's device. No card numbers are stored in your CRM. No card numbers exist anywhere in your environment. The agent sees "paid" or "not paid" and nothing else.
Shuttle maintains PCI DSS Level 1 compliance, which is the highest level of payment security certification. This is the same standard required of the largest payment processors in the world. For your business, this limits your PCI scope across dozens of mobile devices in the field.
Frequently Asked Questions
What if the customer doesn't have a smartphone?
The payment link works in any web browser, including basic feature phones with internet access. For the rare customer without any internet-capable phone, your agent can take a phone payment through your office team, or you can send the payment link via email instead. In practice, most UK adults have a smartphone, so this situation is uncommon.
Can agents see if the customer has paid?
Yes. Payment status updates are available in real time through the Merchant Portal and via API callbacks to your CRM or job management system. Agents can check the status of any payment link they've sent. Managers get a dashboard view across the whole team.
What about deposits or part-payments?
Payment links can be configured for any amount. You can send a deposit link before the job starts and a balance link after completion. Both link back to the same job record. Some field service businesses use a three-stage approach: deposit on booking, progress payment at midpoint, final balance on completion.
Can I use my existing payment gateway?
Yes, if it's a compatible provider. Shuttle works with 40+ PSPs including Stripe, Worldpay, Adyen, Braintree, and most major UK and European payment providers. You keep your existing merchant account and processing rates. Shuttle sits between your software and your PSP, handling the payment link generation and checkout hosting, which limits your PCI scope.
How quickly can we get started?
It depends on your setup. Getting started involves connecting your payment gateway to Shuttle, configuring your branded checkout page, and setting up the integration with your CRM or FSM software, directly or through Zapier or Make.
Related Reading
Ready to replace card terminals across your field team? Talk to Shuttle about Links Checkout for your business.
