A caller phones your client's business. Your receptionist picks up, takes a message, books an appointment, maybe transfers the call. Professional, efficient, exactly what your client pays for.
Then the caller says: "Can I pay my invoice?"
And your answering service hits a wall.
The Payment Gap in Call Answering
There are roughly 6,000 contact centres in the UK employing 1.3 million people. A significant slice of that market is call answering services, from Moneypenny-scale operations with 1,000+ staff down to five-person teams handling overflow for local businesses.
Most of them can handle:
Message taking
Appointment scheduling
Call transfers and routing
Basic order processing
CRM updates
Lead qualification
What most of them can't do: take a payment.
Not because they don't want to. Because the infrastructure to do it securely (while handling calls for multiple clients, each with their own payment processor) doesn't exist in most answering service tech stacks.
The result: callers who are ready to pay get told "someone will call you back." Some do call back. Many don't. The client loses a conversion that was sitting right there.
Why It's Not as Simple as "Just Add Stripe"
The naive solution, "give agents a Stripe login", fails for three reasons:
1. PCI Compliance
The moment an agent hears a card number, your entire phone system is in PCI scope. Call recordings, agent workstations, network infrastructure, CRM: all of it needs to meet PCI DSS requirements. For a 10-person call answering service, the compliance cost is wildly disproportionate to the business size.
PCI DSS Level 1 certification costs hundreds of thousands. Even self-assessment (SAQ-D) is a substantial ongoing burden. Most answering services simply can't justify the cost.
2. Multiple Clients, Multiple PSPs
Your clients don't all use the same payment processor. Client A uses Stripe. Client B uses Worldpay. Client C processes through PayPal. Client D has a SagePay account.
Logging into each client's payment dashboard to process a transaction means:
Agents need credentials for multiple systems
Training multiplies with each new client
No unified view of what's been processed
Card data visible on screen = full PCI scope
A single mis-keyed payment goes to the wrong merchant
At 5 clients, this is awkward. At 20, it's unworkable.
3. Agent Trust and Fraud Risk
Call answering services have staff turnover. Agents handle hundreds of calls daily. Giving them access to card numbers, even verbally, creates a fraud vector. One rogue agent memorising card details can result in financial loss, regulatory action, and reputational damage that a small business can't survive.
The secure approach is to ensure agents never see or hear card data in the first place.
What "Adding Payments" Actually Looks Like
There are two practical approaches for a call answering service that wants to offer payment collection:
DTMF Capture During the Call
The agent stays on the line. When it's time to pay, the caller enters their card details via their phone keypad. The tones are captured in a PCI-certified environment, and the digits never reach the agent or the recording.
The agent sees a confirmation: "Payment of £85.00 approved, last four digits 7291."
The caller never left the conversation. The agent never heard a card number. The call recording is clean. The answering service's PCI scope is limited.
Payment Links via SMS
The agent sends a branded payment link to the caller's mobile during the call. "I've just sent you a link. You can pay on your phone while we chat." The caller completes payment on a hosted checkout page supporting cards, Apple Pay, Google Pay, and bank transfers.
This works especially well for callers who can't use a keypad (older handsets, VoIP softphones) or who prefer visual confirmation of the amount.
Both approaches can run through the same payment layer, and both route to the client's own compatible PSP, without the answering service touching card data.
The Business Case
Payment collection is a premium add-on. Answering services that can take payments charge more per call and differentiate from the dozens of competitors offering message-taking.
Consider:
Higher client retention. A client whose payment flows run through your service doesn't churn to save £50/month on answering fees. The switching cost is too high.
New client segments. Tradespeople, solicitors, medical practices, property managers: businesses that receive payment calls and currently lose conversions because the answering service can't process them.
Payment collection is one of the highest-value capabilities a service can add, and one of the least penetrated.
What to Look For
If you're a call answering service evaluating payment infrastructure:
Multi-PSP support. Your clients have different payment processors. The solution needs to route each client's payments through their own PSP, without you integrating with each one individually. Look for 30+ gateway support for voice through a single integration.
Limited PCI scope. Card data should never enter your environment. DTMF tones captured externally. Recordings clean. Agents see confirmation only. This heavily reduces your PCI scope. Merchants complete SAQ-A, the lightest PCI self-assessment; an answering service taking payments on behalf of its clients is almost certainly a service provider, and service providers complete SAQ-D. Everyone taking card payments has to be PCI compliant, and your acquirer confirms which form applies to you.
Per-transaction pricing. Avoid per-seat licensing. You want cost that scales with payment volume, not headcount. A month where your agents process 50 payments shouldn't cost the same as a month with 5,000.
Payment links as a fallback. Not every caller can use a keypad. SMS payment links, branded to the client, give you wider coverage.
White-label. The payment experience should carry your client's brand, or yours. Not a third-party vendor's logo that confuses the caller.
Fast setup. If the integration requires a six-month project, it's the wrong solution for a call answering business.
The Opportunity Is Now
PCI DSS v4.0.1 is raising the bar for everyone who handles payments. Businesses that used to accept the risk of verbal card capture are being told by their compliance teams, their insurers, and their enterprise clients that it's no longer acceptable.
That creates demand for answering services that can take payments securely. The services that can offer it will capture the clients that need it. The ones that can't will keep taking messages while the callers who wanted to pay go elsewhere.
Related Reading
PCI-Compliant Payments for Contact Centres: the complete guide to secure contact centre payment approaches
Payment Collection for BPOs: multi-client, multi-PSP payment collection for outsourcers
Secure Payment Collection for Debt Agencies: payments for the collections vertical
Want to add payment collection to your answering service?
Shuttle connects your voice flows to 30+ payment gateways with PCI DSS Level 1 compliance: DTMF capture through Twilio Pay, SMS payment links and white-label branding. Pricing is $49 per live instance per month, plus from $0.20 per transaction, falling with volume, billed through your Twilio account.
Book a Demo | See Voice Checkout