UC PAYD
PCI-compliant phone payments. Accept card payments over the phone without the agent seeing or hearing the customer's card details.
In short
UC PAYD is PCONNECT's add-on for businesses that take card payments over the phone. Customers enter card details using their keypad while the agent stays on the call, with payment tones masked from agents and recordings. It provides PCI-compliant phone payments alongside the business phone setup, with payment gateway compatibility checked during design.
Key facts
- Service
- PCI-compliant phone payments.
- Entry method
- Customer phone keypad
- Controls
- Masked payment tones
- Compatibility
- Confirm phone platform and payment gateway
Last updated
The Problem It Solves
How does UC PAYD work?
Which platforms work with UC PAYD?
- Compatible with UC XCEL, UC XPRESS, and Teams Calling
- Supports major payment gateways including Stripe, Windcave, and eWAY
- No changes to your merchant account or payment processor
- API integration available for custom workflows
- Works with call recording — card data is never captured
Why It Matters
PCI-Compliant Phone Payments
- PCI-compliant phone payments with DTMF masking
Recording Friendly
- Recordings no longer capture cardholder data — no need to pause or redact payment segments
No Gateway Changes
- Works with your existing payment gateway — no new infrastructure needed
Seamless Experience
- Customer stays on the same call — no IVR transfer or hang-up required
Reduced Risk
- Agents never see or hear card details — eliminates internal fraud risk from phone payments
Fast Deployment
- Cloud-based activation — no hardware to install, no lengthy implementation projects
Agents Hearing Card Numbers vs UC PAYD Masked Payments
Agents Hearing Card Numbers
- Agents hear and repeat card numbers during every phone payment
- Card details are captured in call recordings — PCI compliance risk
- Your call centre is in full PCI DSS scope — audits and certification costs
- Internal fraud risk from agents with access to card numbers
- Calls must be paused or recordings manually redacted during payments
- Customers uncomfortable reading card details aloud to a stranger
UC PAYD Masked Payments
- Agents never see or hear card numbers — DTMF tones masked in real time
- Recordings are clean — no cardholder data captured at any point
- Card payments taken over the phone with PCI-compliant phone payments
- Zero internal fraud risk — card data never passes through agents
- No need to pause recordings — payments are recording-safe by design
- Customers enter card details privately via keypad while agent stays on the line
How a UC PAYD Payment Works
- Step 01
Call Starts
The agent handles the call as normal — discussing the order, service, or account query with the customer.
- Step 02
Agent Activates PAYD
When the customer is ready to pay, the agent clicks a button to activate UC PAYD within the call.
- Step 03
Customer Enters Card
The customer enters their card number, expiry date, and CVV using their phone keypad. The agent stays on the line.
- Step 04
DTMF Tones Masked
Card digits are masked in real time — the agent hears flat tones instead of distinguishable DTMF. Recordings capture only masked audio.
- Step 05
Payment Processed
Card details are sent securely to your payment gateway (Stripe, Windcave, eWAY) for authorisation. The agent sees approval or decline status.
- Step 06
Confirmation
The agent confirms the payment result to the customer and continues the call. No card data was exposed at any point.
Frequently Asked Questions
Does the agent have to do anything special?
The agent simply activates UC PAYD at the point of payment. The rest is guided.
Can we still record the call?
Yes. Card tones are masked before recording — no compliance concern.
Do we need a new payment gateway?
No. UC PAYD works with your existing gateway if it supports e-commerce transactions.
Does the customer notice a difference?
The customer stays on the same call and enters card details by keypad — the agent is present throughout.
What does UC PAYD provide?
PCI-compliant phone payments. DTMF masking keeps card details hidden from agents and recordings.
Can UC PAYD handle refunds?
UC PAYD processes the initial payment. Refunds are handled through your payment gateway as normal.
Is UC PAYD the right fit?
Good fit if…
- Your team takes card payments by phone.
- Agents need to stay on the line during payment.
- You need payment tones masked from agents and recordings.
Consider something else if…
- Your requirement is recording and searching calls. Explore Call Recording.
- Your requirement is reporting on call activity. Explore Call Analytics.
Choose around your main requirement. Some services can be used together.
Related
Add-ons
Connect calling with payments, reporting and customer workflows.
eFAX
Electronic fax by email
Call Analytics
Tollring iCALL Suite dashboards
Call Recording
Dubber cloud call recording
SMS Gateway
Two-way business SMS
Compare All
Compare all Voice & UC options
UC XCEL
Cisco BroadWorks cloud PBX with Webex
XIMA
Cloud contact centre with AI analytics
Retail
Multi-location POS & payments
Industries
Voice, data, and mobile services for Australian businesses.
Locations
4 Australian offices: Gold Coast (head office), Newcastle & Central Coast, Sydney, Melbourne.
Gold Coast
Tourism, hospitality & construction
Central Coast
Newcastle & Hunter Valley
Sydney
Financial district & Western Sydney
Melbourne
CBD, Richmond & professional services
Call recording obligations in Australia
Before recording calls, establish the lawful basis, caller notice, access controls and retention policy for your circumstances. Requirements vary by jurisdiction and context. This is general information, not legal advice; obtain advice before enabling recording for sensitive conversations.
Cloud PBX Explained: Everything Australian Businesses Need to Know
Omnichannel Contact Centre: Why Voice Alone Isn't Enough
What Is UCaaS? Unified Communications as a Service Explained
Ready to Talk?
Contact PCONNECT to find out if UC PAYD is compatible with your voice platform and payment gateway.
