Voice payments
Send a secure payment link while the customer is on the call.
Your agent answers the question, finds the order and confirms the amount. It then sends a secure payment link while the caller is still on the line. The customer completes payment on your provider's page.
A secure link, mid-call. Your provider handles the card.
The agent never asks for card details out loud. The payment happens on your own provider's page, which our team connects during the build.
- 1
Confirm
The agent states what the payment is for and the amount, and the caller agrees.
- 2
Send
A payment link from your provider goes to the caller by WhatsApp, during the call.
- 3
Pay
The caller pays on their phone while the agent stays on the line for any questions.
- 4
Close
Your payment system records the result, and the call summary goes to your team as usual.
Pilot
Keypad entry. For when a link will not do.
Some callers cannot open a link. For those teams we offer card entry on the phone keypad as a pilot. It is off by default, and we switch it on for one agent at a time, after the whole flow is tested end to end with your processor.
Never spoken aloud
The caller types the card on the keypad. The agent never asks for digits out loud and never reads them back.
Kept from the AI model
Digits are collected by the gateway, not passed to the model. The conversation learns only the result, and after an approval the last four digits.
Straight to your processor
The card is held in memory only for the authorization, sent to your processor, then wiped. A real card number is never stored in our cloud.
Checked before it is sent
Length and checksum rules catch most typing mistakes. Press star to start again and hash to finish.
Patient with the caller
The entry timer waits while the agent is speaking, and typing counts as the caller being there, so nobody is asked if they are still on the line.
Out of logs and transcripts
Typed digits never go into logs, transcripts or the model. A number read aloud is ordinary speech on the call, which is why the agent never asks for one.
One payment step. Many kinds of call.
Tell us what customers pay for and which provider you use. We map the payment step into the call, along with what happens after an approval or a decline.
Map your payment flow- Invoices and balancesSettle what is owed while the caller has the bill in front of them.
- DepositsSecure an appointment or reservation before it goes in the calendar.
- Phone ordersFinish the order on the same call that started it.
- RenewalsMemberships and subscriptions renewed without a second call.
Questions from payment and security teams.
Does the agent ever see the card number?
With a payment link, no: the card is entered on your provider's page. With keypad entry, the digits are collected by the gateway and sent to your processor; the AI model receives only the result and, after an approval, the last four digits.
Are the keypad tones on the call recording?
Today, yes: the tones are part of the call audio. If your policy requires them excluded, use the payment link, or switch recording off for that agent. Recording and transcripts are separate switches.
Which payment providers can you connect?
Payment links work with any provider that can create one through its API; our team connects it during the build. Keypad entry needs a direct processor connection, which we build and test with you before anything is switched on.
Does the caller have to leave the call?
No. The link arrives during the call and the agent stays on the line. With keypad entry, the caller types the card and the conversation continues as soon as the result comes back.
Which call should your agent take first?
Tell us which requests your team handles most often. We'll suggest a practical place to start.