Take an in-store card payment on a Verifone terminal, get back a token, and use it later to take the balance online, by phone, or through any other Paytia channel — without the customer ever re-entering their card. Refund across any channel, full audit trail, PCI DSS Level 1 end to end.
Secure, tokenized, cross-channel
Your associate starts the payment from whatever tool they're already in — browser-based CRM, iPad sales app, or any system that calls the Paytia API. Paytia sends the request to the connected Verifone terminal.
The customer inserts, taps, or uses their mobile wallet on the terminal. The Verifone device handles card capture and authorization. Card data never touches your systems.
Paytia returns a tokenized reference for the card. Use that token later to take the balance online or by phone, issue a refund, or capture a follow-up deposit — all without bringing the customer back into the store.
The same token flows through the whole customer lifecycle — deposit, follow-up, refund. Your team stops chasing payment details and starts closing tickets.
The customer pays a deposit on the Verifone terminal in your store. They insert or tap the card, the terminal authorizes the payment.
Paytia returns a token that represents the card. Your CRM gets a webhook confirming the payment and storing the token against the customer record. Card details never pass through your staff or your systems at any point.
Days or weeks later, the balance is due. Maybe it's the final payment on install day. Maybe it's the next installment. Your team takes the payment using the stored token, from the CRM or iPad, without needing the customer or their card.
No terminal interaction. No phone call to read out a card. No payment link to chase. The token authorizes the follow-up against whichever acquirer Paytia's connected to.
Returns, part-refunds, adjustments — handled from whichever channel makes sense. A payment taken at the terminal can be refunded from the CRM. A phone or online payment can be refunded to the card on file from the same dashboard.
By default refunds go back to the original card (card-network rule). Where your acquirer permits an alternative destination — for example if the original card has expired — Paytia supports that flow with the right approvals in place.
A Verifone-connected terminal setup isn't new. What is new is the rest of the lifecycle — the token, the refunds, the cross-channel reuse — sitting on top of it without you having to stitch it together yourself.
Works with your existing Verifone POS estate. No new hardware required unless you want it — Paytia connects to the terminals your acquirer already provisioned.
Every in-store transaction returns a token that can be used across Paytia channels. Take a deposit at the terminal, take the balance by phone. One card, one customer, one record.
Refund any Paytia-processed payment from a single interface — POS, online, phone, chat, all visible in the same dashboard. No juggling separate refund tools.
Your in-store terminal may sit behind one acquirer and your online gateway behind another. Paytia's token layer works across both — the follow-up uses the gateway you choose, not the one locked to the terminal.
Card data is captured by the terminal directly and never enters your environment. For most customers that drops the in-store channel from SAQ D (329 controls) to SAQ A (22).
Every state change — authorized, settled, refunded, failed — fires a webhook back to your CRM. Your records stay current without anyone having to refresh a dashboard.
Card data is captured on the Verifone terminal and goes straight to Paytia's PCI DSSLevel 1 environment. It doesn't pass through your CRM, your staff, or your servers.
The terminal returns a non-reversible token in place of the card number. Tokens can be stored in your CRM safely — they're useless to an attacker and out of PCI scope.
All data between the terminal, Paytia, and your systems is encrypted in transit with TLS 1.2+ and at rest with AES-256. Standard, verifiable, no novel cryptography.
Paytia is independently audited against PCI DSS Level 1 every year. The in-person channel is covered under the same certification as our phone and online products.
Webhook payloads are signed so your CRM can verify they came from Paytia and haven't been tampered with. Replay protection built in.
Paytia supports US data handling requirements for healthcare (HIPAA BAAs where applicable), state-level privacy (CCPA, NY SHIELD), and federal frameworks relevant to your sector.
Every action — who triggered what, which terminal, which token, which acquirer, which outcome — is logged and exportable. Same trail regardless of the channel.
In-person payments with token reuse are most useful where the sale doesn't complete in one visit. Deposits now, balance later.
Furniture, kitchens, bathrooms, flooring, custom orders. The customer pays in-store, the work happens later, the balance is due on completion.
Hotels, restaurants, event venues where a deposit is taken at booking or check-in, and the final bill is settled later — ideally without the customer waiting to re-swipe at checkout.
Legal retainers, elective healthcare, private education, consulting engagements where payment is staged across milestones or months.
Verifone terminals day one. Paytia connects to your Verifone POS over the standard terminal integration path, so any Verifone device your acquirer provisions should work. Ingenico, PAX, and other vendors aren't supported at this stage.
Yes. The token returned from the in-store transaction can be used to process a follow-up payment through any acquirer Paytia is connected to — useful if your online gateway is different from the one sitting behind your Verifone terminal.
Take the balance through any of Paytia's other channels — phone, payment link, web chat — and capture the new card there. The original token stays with the deposit record; a new token handles the balance. Nothing's forcibly tied together.
The token is still valid technically — it's a reference, not a commitment — but we'd recommend holding further payments against it until the dispute is resolved. Paytia flags tokens with active disputes in the dashboard.
Tokens don't expire automatically. Card expiration dates do — so if the underlying card expires before you reuse the token, the follow-up payment will fail and you'll need a fresh card. Paytia returns expiration metadata with the token so you can schedule around it.
Card data is captured by the Verifone terminal directly — it never enters your CRM, your staff's laptops, or your servers. Paytia only holds the token, which is non-sensitive. For most customers the in-store channel drops from SAQ D to SAQ A, the same way our phone and online products do.
By default yes — card network rules require refunds to the original payment method. Where your acquirer permits alternative refund destinations (for example, if the original card has expired), Paytia supports that flow with the right approvals in place.
Yes. The Paytia in-person flow is triggered from whatever web-based app your team uses — a browser-based CRM, an iPad sales tool, or your own internal app through our API. The terminal receives the request, the customer taps, and the result comes back via webhook.
The terminal handles card authorization independently, so a network drop between the terminal and Paytia doesn't invalidate a payment that already authorized. Paytia reconciles state on reconnect and fires the webhook when things settle. Status is visible in the dashboard throughout.
Depends on your CRM and whether you're using a new Verifone terminal or adapting an existing one. A typical integration is 4-8 weeks from kickoff to first live transaction — most of the time goes into defining payment triggers inside your CRM rather than on the Paytia side.
Used by British American Tobacco · Howard Kennedy · CITB · Clinical Partners · Trinity Hall College
Since 2016
Building secure payments
PCI DSS Level 1
Highest certification
99.99%
Platform uptime
£40M+
Transactions processed
Book a free demo to see the deposit-to-balance-to-refund flow end to end on your own systems.
Trusted by law firms, insurers, healthcare providers and regulated businesses worldwide. Learn more about Paytia