Voice platforms
How to take payments with Retell voice agents
Retell makes it easy to ship a production voice agent. It does not make it easy for that agent to get paid. The moment a caller needs to hand over a card, you are either sending them a payment link and losing them, or exposing your entire pipeline to PCI DSS scope.
Maven closes that gap. Your Retell agent transfers the caller to Maven at payment time, Maven collects the card and charges your gateway, then hands the caller straight back. Integration is a webhook URL and a copied JSON schema, and most teams are live inside ten minutes.
The problem with cards on Retell calls
A spoken card number flows through Retell transcription, your LLM context, and your logs. Under PCI DSS, every one of those systems becomes cardholder data environment the moment a card passes through it. Scoping, auditing, and securing that is months of work that has nothing to do with your product.
Maven keeps your stack out of scope entirely by taking the caller off your agent for the sixty seconds that involve card data, and only those sixty seconds.
How Maven works with Retell
You paste a Maven webhook URL into Retell and copy Maven's JSON schemas into a custom function on your agent. When the conversation reaches payment, the agent calls that function and Retell transfers the caller to Maven.
Maven's payment agent collects the card by voice or keypad, validates it in real time, and charges your connected gateway. A signed webhook tells your backend the result, and the caller is transferred back to your Retell agent to wrap up.
Your gateway, your money
Maven is not a processor in the middle of your funds. Charges run through your own Stripe, Authorize.net, Braintree, J.P. Morgan, Fiserv, Shift4, NMI, Qualpay, or Clover account. Payouts, fees, and disputes stay exactly where they are today.
Setting it up
- 01
Create a Maven app and connect your gateway
Sign up, pick your gateway, paste credentials. Maven charges through your account on your behalf.
- 02
Paste the webhook URL into Retell
Maven gives you the URL. Retell sends call events to it so Maven can coordinate the handoff.
- 03
Copy the JSON schemas into a custom function
Maven provides ready-made function schemas. Your agent calls the function when the customer is ready to pay.
- 04
Maven collects the card mid-call
Voice or keypad entry, real-time validation, automatic retry on declines or missed digits. The charge runs through your gateway while the caller is still on the line.
- 05
The caller comes back, you get a webhook
A signed webhook confirms the result, and the caller returns to your Retell agent with the payment done.
Common questions
Does adding payments to Retell put me in PCI scope?
No. The card is collected by Maven, not your agent. Your Retell transcripts, prompts, and logs never contain card data, so your stack stays out of PCI DSS scope.
How long does the Retell integration take?
Most teams are live in under ten minutes: paste a webhook URL, copy the JSON schemas into a custom function, and connect a gateway.
What happens if the payment fails?
Maven has built-in retry logic. Declines, missed digits, and invalid numbers are handled conversationally and the caller is re-prompted instead of dropped.
Can I use my existing payment provider?
Yes. Maven charges through your own gateway account, and supports Stripe, Authorize.net, Braintree, J.P. Morgan, Fiserv, Shift4, NMI, Qualpay, and Clover, plus card forwarding to your own endpoint.
Add payments to your agent in minutes, not months
Connect your gateway, wire the handoff, and start collecting. Card data never touches your stack.