Number masking hides the phone numbers of the two people on a call. It does not take card payments and does not remove card data from a conversation. Edesy makes no PCI DSS compliance claim. If card details could be spoken on a masked call, keep recording off for that number and take payment through a separate PCI-compliant channel. This page is general information, not legal advice.
Number masking at a glance
Agents and customers see the virtual number, not each other's personal mobile.
Recording is a per-number setting. Turn it off for numbers where card details might be read out.
Where you do record, audio is kept in encrypted cloud storage and opened through signed links.
Workspace roles (owner, admin, member) and revocable API keys limit who can reach call logs and recordings.
Every call is logged with status, duration and cost, so you can audit calls without keeping recordings.
Event webhooks are HMAC-SHA256 signed so you can verify them on your server.
Send customers to a payment link or gateway instead of asking for card numbers on a masked call.
Disable recording on numbers used for payment conversations, since Edesy recordings cannot be paused mid-call.
Ask your QSA or acquirer how voice calls fit your PCI DSS scope. Edesy does not provide a PCI attestation.
Invite only the staff who need call logs, and rotate API keys if someone leaves.
Get started on the self-serve portal. Rs 1.50 per minute plus number rental. New accounts get a Rs 20 welcome credit; no card needed to sign up.