ProxyPay, part of the Paytia SecureFlow platform, takes a different approach to secure phone payments. Instead of rebuilding your payment flow around our API, ProxyPay sits invisibly inside your existing payment integration. Your system keeps driving the payment, talks to the same gateway it always has, and we slot in the real card data we captured securely over the phone — mid-flight — then get out of the way. The customer journey doesn't change, your gateway integration doesn't change, and card data never enters your business at any layer.
How it works with ProxyPay
Customer keys their card on the call
Paytia captures the keypad entries directly. The masking means the agent hears nothing and the call recording captures nothing.
Your system sends its usual request
When your application is ready to take payment, it sends its normal API request — except the card fields carry secure placeholder values and the request is addressed to ProxyPay instead of the gateway.
ProxyPay swaps in the real card data
We substitute the real card data for the placeholders and forward the request to whichever gateway you were already using.
The gateway responds as normal
The processor sees an ordinary payment from the same customer of record as always. Your error handling, webhook listeners and reconciliation carry on unchanged.
0
Changes to your payment code
1
Config field to repoint
0
Card data in your systems
PCI L1
Certified platform
A customer on a live call keys their card on their phone's keypad. We capture the keystrokes directly, and DTMF masking suppresses the tones so neither the agent nor the recording picks anything up. Then your own system takes the payment the way it always has.
Customer keys their card on the call
Paytia captures the keypad entries directly. The masking means the agent hears nothing and the call recording captures nothing.
Your system sends its usual request
When your application is ready to take payment, it sends its normal API request — except the card fields carry secure placeholder values and the request is addressed to ProxyPay instead of the gateway.
ProxyPay swaps in the real card data
We substitute the real card data for the placeholders and forward the request to whichever gateway you were already using.
The gateway responds as normal
The processor sees an ordinary payment from the same customer of record as always. Your error handling, webhook listeners and reconciliation carry on unchanged.
ProxyPay does what the name says — it proxies your payment request, swapping secure placeholders for real card data in transit. Your system stays in the driver's seat.
DTMF masking captures the card over the live call so the agent, the CRM, the contact-centre platform and the recording never receive it.
You keep the gateway or processor you already use, including bespoke and specialty integrations. The processor sees an ordinary payment.
Change the destination URL, swap the card fields for placeholders, and point the request at ProxyPay. No re-engineering of payment plumbing, retry logic or reconciliation.
We built ProxyPay for a contact centre whose sales platform talked to a specialty processor through a custom integration — exactly the kind of bespoke plumbing that makes traditional descope projects slow.
You never have the card data, so there's nothing to protect, audit or redact — without the multi-month rebuild that secure phone payments usually demand.
Most approaches — including our own earlier products — have the provider's API drive the payment, which means rebuilding your payment plumbing around it. ProxyPay flips that: your existing system keeps driving, and we sit in the middle just long enough to swap secure placeholders for the card data we captured by phone.
Very little. You change the destination URL in a config field, swap the card fields in your request for secure placeholders, and point it at ProxyPay. Your payment-handling code, error handling, webhooks and reconciliation stay as they are.
No. ProxyPay substitutes the real card data and forwards the request to the gateway you already use. The processor sees an ordinary payment from the same customer of record as always.
On the live call. The customer keys their card on their phone's keypad, we capture the keystrokes directly, and DTMF masking suppresses the tones so the agent and the recording pick up nothing.
Any business taking card-not-present payments that wants to descope its existing systems without rebuilding them — especially contact centres with bespoke or specialty payment integrations that would be expensive to re-engineer.
Use another tool too? See all our integrations.
Build fully branded checkout pages with custom fields and payment rules — point and click, no developer needed, PCI DSS Level 1 behind it.
Learn moreIVCallers pay on their own by keypad or speech, 24/7, with no agent in the path. Card data bypasses your systems entirely.
Learn moreCoTake payments inside an AI agent's conversation — by phone or chat — with card data captured outside the model's context, logs and recordings.
Learn morePaCard-free payments on a phone call. The customer authorises in their banking app and the money moves straight into your account — no card, no PCI scope.
Learn moreBook a demo. We'll walk through your current integration and show where ProxyPay slots in — usually a config change, not a project.
Trusted by law firms, insurers, healthcare providers and regulated businesses worldwide. Learn more about Paytia