The gateway that fits your systems
Most payment gateways make you adapt your application to their schema. ProxyPay — the Paytia Proxy Gateway — works the other way round. You define exactly what data we post, where it goes and how it's structured, as a JSON payload you control completely. Wherever your payload needs card details, you drop in a variable like {{PAN}} or {{EXPDATE}}. We capture the customer's card securely over the phone, inject the real values at the moment of transmission, encrypt the payload if you want, and post it to your endpoint — a payment gateway, a CRM, an ERP, a donation platform or a bespoke API. Your application, your agents and your recordings never see a card number.
- You design the payload — we don't impose a schema
- Card data injected at runtime, never exposed to your systems
- Posts to any endpoint: gateways, CRMs, ERPs, bespoke APIs
- Outbound payload encryption: AES-256, RSA, BCRYPT or JWT
- Authenticated API calls to your receiving system, configured in the portal
- Included in supported Paytia packages — a config task, not a project
How it works with ProxyPay
Design your payload
Build the exact JSON structure your receiving system expects — order lines, contact details, campaign codes, whatever your process needs. Where the card data belongs, place variables like {{PAN}}, {{EXPDATE}}, {{CVV}} and {{CARDBRAND}}.
Customer keys their card on the call
Paytia captures the keypad entries directly on our PCI DSS Level 1 platform. The agent hears nothing, the recording captures nothing, and your agent sees the capture progress live in Agent Capture Assist.
We inject, encrypt and authenticate
At the point of transmission we replace your variables with the real card data, apply AES-256, RSA, BCRYPT or JWT encryption if configured, and authenticate against your endpoint using the credentials you set in the portal.
Your endpoint receives a complete payload
The finished request lands at your gateway, CRM, ERP or API exactly as you designed it. Your systems process it as normal — the card data existed on your side only as a placeholder.
100%
Your payload structure
4
Encryption options
0
Card data in your systems
PCI L1
Certified platform
How Paytia works with ProxyPay
A customer on a live call keys their card on their phone's keypad — DTMF masking keeps the digits off the agent and the recording, and your agent watches the capture progress in real time. Then the payload you designed does the rest.
- 1
Design your payload
Build the exact JSON structure your receiving system expects — order lines, contact details, campaign codes, whatever your process needs. Where the card data belongs, place variables like {{PAN}}, {{EXPDATE}}, {{CVV}} and {{CARDBRAND}}.
- 2
Customer keys their card on the call
Paytia captures the keypad entries directly on our PCI DSS Level 1 platform. The agent hears nothing, the recording captures nothing, and your agent sees the capture progress live in Agent Capture Assist.
- 3
We inject, encrypt and authenticate
At the point of transmission we replace your variables with the real card data, apply AES-256, RSA, BCRYPT or JWT encryption if configured, and authenticate against your endpoint using the credentials you set in the portal.
- 4
Your endpoint receives a complete payload
The finished request lands at your gateway, CRM, ERP or API exactly as you designed it. Your systems process it as normal — the card data existed on your side only as a placeholder.
Why teams choose ProxyPay with Paytia
A payload you control completely
The metadata structure is yours: field names, nesting, order data, contact records. We post what you define — not a fixed gateway schema you have to code around.
Runtime variable substitution
Drop {{PAN}}, {{EXPDATE}}, {{CVV}} or {{CARDBRAND}} anywhere in your JSON. The real values are injected only at the moment of secure transmission — never stored, displayed or passed through your environment.
More than payment gateways
Point it at a CRM, an ERP, a donation platform or a bespoke internal API. If your system takes an authenticated HTTP post, ProxyPay can feed it a complete transaction.
Encryption and authentication built in
Encrypt outbound payloads with AES-256, RSA, BCRYPT or JWT, and configure how we authenticate with your endpoint — OAuth token requests, custom headers, form or JSON bodies — all from the Paytia Administration Portal.
Live capture visibility for agents
Agent Capture Assist shows the card capture progressing in real time, so your agent stays in control of the call without ever seeing a digit.
Descope without the rebuild
Card data never enters your application, so there's nothing to protect, audit or redact. We built ProxyPay for a contact centre with a bespoke processor integration — the kind traditional descope projects re-engineer at great cost. Theirs didn't change.
ProxyPay + Paytia — common questions
How is ProxyPay different from a normal payment gateway?+
A normal gateway hands you a schema and your developers adapt to it. ProxyPay reverses that: you define the payload your systems already expect, mark where the card data goes with variables, and we fill in the real values at transmission. It's a gateway that fits your systems, not the other way round.
Can it post to systems other than a payment gateway?+
Yes — that's the point. CRMs, ERPs, donation platforms and bespoke APIs all work. One of our customers posts completed phone orders, card data included, straight into their Salesforce-based sales platform.
How is the payload secured in transit?+
Three layers. The card values are injected only at the point of transmission, the whole payload can be encrypted with AES-256, RSA, BCRYPT or JWT before it leaves Paytia, and the post is authenticated against your endpoint with credentials you configure in the portal.
Where does the card data get captured?+
On the live call. The customer keys their card on their phone's keypad, we capture the keystrokes directly on our PCI DSS Level 1 platform, and DTMF masking suppresses the tones so the agent and the recording pick up nothing. Agents follow the progress in Agent Capture Assist without seeing a digit.
What does setup involve?+
It's configuration, not development. The Proxy Gateway is included in supported Paytia packages (or available on request), and everything — your payload, your endpoint URL, authentication and encryption — is set up through the Paytia Administration Portal.
Use another tool too? See all our integrations.
Related integrations
Browse all integrationsWeb Checkout Builder
Build fully branded checkout pages with custom fields and payment rules — point and click, no developer needed, PCI DSS Level 1 behind it.
Learn moreIVIVR Self-Service Payments
Callers pay on their own by keypad or speech, 24/7, with no agent in the path. Card data bypasses your systems entirely.
Learn moreCoConversational & AI Payments
Take payments inside an AI agent's conversation — by phone or chat — with card data captured outside the model's context, logs and recordings.
Learn morePaPay by Bank
Card-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 moreGet a gateway that fits your systems
Book a demo and bring your payload spec. We'll show a live phone capture landing in your structure, at your endpoint, with your side never touching a card number.
Trusted by law firms, insurers, healthcare providers and regulated businesses worldwide. Learn more about Paytia