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 PCI DSS level does UC PAYD achieve?

UC PAYD is certified PCI DSS Level 1, the highest level of certification. It removes your call centre from PCI scope entirely for phone payments.

Can UC PAYD handle refunds?

UC PAYD processes the initial payment. Refunds are handled through your payment gateway as normal.

Secure Payments

UC PAYD

PCI-DSS compliant payment gateway for phone-based card transactions. Accept card payments over the phone without the agent seeing or hearing the customer's card details.

Get in Touch 1300 049 211

Compliance Risk

The Problem It Solves

When customers pay over the phone, the agent hears the card number. That conversation may be recorded. Both put your business inside PCI DSS scope — audits, compliance obligations, and cost. UC PAYD removes the issue at its source.

Process

How It Works

The agent handles the call as normal. At payment time, the agent activates UC PAYD. The customer enters card details via their phone keypad. DTMF tones are masked in real time. The agent stays on the line but cannot see or hear the card number. Payment is processed through your existing gateway.

Integration

Platform Compatibility

UC PAYD works across PCONNECT voice platforms and integrates with your existing payment infrastructure.

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

Benefits

Why It Matters

PCI Compliance

Remove your call centre from scope for phone payments, avoiding full PCI certification costs

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

Why Switch

Agents Hearing Card Numbers vs UC PAYD Masked Payments

See what changes when you stop exposing agents to cardholder data and remove your call centre from PCI scope.

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

Call centre removed from PCI DSS scope for phone payments entirely

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

Payment Flow

How a UC PAYD Payment Works

A step-by-step view of the secure payment process from the agent and customer perspective.

Step 1

Call Starts

The agent handles the call as normal — discussing the order, service, or account query with the customer.

Step 2

Agent Activates PAYD

When the customer is ready to pay, the agent clicks a button to activate UC PAYD within the call.

Step 3

Customer Enters Card

The customer enters their card number, expiry date, and CVV using their phone keypad. The agent stays on the line.

Step 4

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 5

Payment Processed

Card details are sent securely to your payment gateway (Stripe, Windcave, eWAY) for authorisation. The agent sees approval or decline status.

Step 6

Confirmation

The agent confirms the payment result to the customer and continues the call. No card data was exposed at any point.