A lot of small-business payments don't happen at a checkout page. They happen at the end of a phone call. A clinic wants a booking deposit. A cleaning company wants an advance before a deep clean. A repair shop has a customer who keeps meaning to settle last month's invoice.
None of these are hard. Someone opens Stripe, creates a payment link, and gets it to the customer. But it's still a manual step, and it usually happens after the call, when the customer has already moved on with their day. The link sits unread, and the booking that depended on it turns soft.
Aiva Chat's Stripe integration moves that step inside the call. When a caller agrees to pay, the assistant creates a Stripe payment link in your own account, for the right amount and in your currency, and texts it to them while they're still on the line. They pay on Stripe's secure page, and the money goes straight to you.
Before you switch it on, the two settings worth thinking hardest about are the maximum link amount and whether your number is registered for texting; both are covered in the setup steps.
What is the Aiva Chat Stripe integration?
The Aiva Chat Stripe integration lets your AI phone assistant text a caller a link to pay you during a live call. You connect a Stripe restricted key, which is a key that can only do the few things you allow, and set a currency and the largest amount a single link may be for.
During a call, when payment comes up and the amount is clear from the conversation, the assistant creates a payment link in your Stripe account with a short description, such as "Deposit for kitchen consultation." Aiva Chat texts it from your Twilio number to the number the caller is calling from. The assistant never reads the link aloud and never takes card details by voice.
It suits appointment-based and service businesses that already use Stripe: clinics, salons, cleaners, repair shops, consultants, tutors, and event businesses. It's most useful where deposits, advances, or overdue balances come up on the phone often enough that your team regularly ends calls with "I'll send you a link."
What it isn't matters too. The phone assistant doesn't read your Stripe history, issue refunds, change subscriptions, or sit in your website checkout. It creates links within limits you set, and that's all.
The same Stripe key also powers deposits on Aiva Chat's booking pages. A service can ask for a fixed or percentage deposit, which the customer pays through Stripe Checkout in your account while booking online, and you can set a cancellation policy that refunds deposits automatically when someone cancels in time. Your team can refund deposits from the dashboard. Deposits aren't taken by the AI on calls, though, so a link sent mid-call isn't recorded as the booking's deposit; mark the appointment as paid if you want the dashboard to show it.
How a payment link works mid-call
Here's what happens once Stripe is connected and the action is switched on.
Step 1: Payment comes up in the conversation
A caller books an appointment that needs a deposit, or calls to settle a balance, or asks "can I just pay now?" The assistant knows your payment policies from what you've written in AI Training, such as "Ask for a $50 deposit to confirm a first appointment."
Step 2: The assistant confirms the amount and purpose
Before sending anything, it checks what the payment is for and how much, so the customer isn't surprised by the amount on the page they open. If the amount is over your maximum or in another currency, it won't send a link and tells the caller a colleague will follow up.
Step 3: The link is created in your Stripe account
Aiva Chat creates a payment link in your account, for that amount, in your currency, with a short description. Nothing goes through an Aiva Chat account in between.
Step 4: The link is texted to the caller
The link goes by text to the number they're calling from, while the call continues. If their number is hidden, or they've opted out of texts by replying STOP, no link is sent and the assistant offers a follow-up instead.
Step 5: The customer pays and you see it in Stripe
The caller opens the link and pays on Stripe's hosted page. The payment appears in your Stripe Dashboard, and the call's actions log in Aiva Chat shows whether the link was sent.
Benefits of sending payment links during the call
Deposits get collected while the customer is committed
A payment agreed on the phone is the easiest one to lose. The customer says "yes, send it over," the call ends, and the link goes out an hour later, or tomorrow, or never. Sending it during the call means it arrives while the customer's attention is still on you, which makes the booking firmer.
Your team stops doing the follow-up step
Creating links by hand after each call is small work that adds up and gets forgotten on busy days. When the assistant handles it, the person who took the call doesn't need to remember anything.
Card details stay off the phone
Taking card numbers by voice creates risk: numbers written on notes, said aloud in a busy room, or captured in recordings. With links, the customer enters card details on Stripe's page. If a caller starts reading a number out anyway, the call is flagged in your logs so you can review it and delete the recording or transcript if needed.
The money goes straight to you
Because links are created with your own restricted key, payments land in your Stripe account like any other payment. There's no middleman balance, no payout delay from Aiva Chat, and no extra Aiva Chat fee.
You set firm limits
The currency and maximum amount you set are hard limits. A link over the maximum is never created. You also choose whether the action is Automatic or Never per assistant, and the full set of action controls is explained in approvals and autonomy.
The whole point is timing: the payment happens inside the same conversation where the customer agreed to it.
Stripe payment link use cases
Four phone payments that tend to slip through the cracks (invented examples, not customer stories):
The clinic booking deposit
Problem: A clinic asks new patients for a deposit to reduce no-shows, but the front desk sends links after calls, and some never get paid. How Aiva Chat handles it: The voice agent books the appointment, explains the deposit policy, confirms the amount, and texts the link before the call ends. Outcome: The deposit is often paid before the caller hangs up, and nobody had to remember a follow-up.
The cleaning company advance
Problem: A deep clean needs an advance before a crew is scheduled, and quotes vary by home size. How Aiva Chat handles it: Once the caller agrees to a quoted advance within your maximum, the assistant creates a link with a description like "Advance for deep clean, 3-bedroom," and texts it. Outcome: The job is confirmed in one call instead of three messages.
The customer settling a balance
Problem: A repair-shop customer calls to ask what they owe and wants to pay right away. How Aiva Chat handles it: If you've connected a custom action to your billing system, the assistant looks up the balance. Then it sends a link for that amount. Outcome: An overdue balance gets paid on the call instead of after another chasing email from your team.
The lost link
Problem: A customer says the link they were sent earlier never arrived or got buried. How Aiva Chat handles it: It confirms the amount and sends a fresh link while they're on the phone. Outcome: A small problem is solved in under a minute without a staff callback.
Payment links mid-call vs. manual links and phone card payments
| Taking cards by phone | Sending links by hand after the call | Aiva Chat mid-call payment link | |
|---|---|---|---|
| When the customer can pay | During the call | Whenever the link arrives | During the call |
| Card details spoken aloud | Yes | No | No |
| Staff effort per payment | High | Medium, and easy to forget | None once set up |
| Works after hours | Only if someone is there | Next working day | Yes, any hour the assistant answers |
| Handles disputes and refunds | Yes, a person decides | Yes | No, hands off to staff |
| Website chat | Not applicable | Possible | Not supported; use booking-page deposits |
Taking card numbers by phone gets payment immediately, but it puts card details in the open and needs a person on every call. Many businesses would rather avoid that risk altogether.
Sending links by hand is safe and flexible, and a person can handle unusual amounts or negotiate terms. Its weakness is timing. The link arrives late, if it arrives at all, and the customer's attention has moved on.
A mid-call link from the assistant combines the timing of a phone payment with the safety of a hosted page. It isn't the right tool for disputes or website chat; online payments belong on your booking page, and refunds on booking deposits are done from the dashboard. Stripe's own Payment Links documentation covers how links behave on Stripe's side, including receipts and refunds.
How to set up Stripe payment links in Aiva Chat
Stripe is optional and sits alongside Aiva Chat's six guided setup steps. Here's the full process.
Step 1: Decide when you take payment
Write down which situations call for a payment: deposits for first appointments, advances for certain jobs, balances. Decide the largest single amount you'd want sent without a person checking.
Step 2: Create a restricted key in Stripe
In your Stripe Dashboard, create a restricted key with write access to Payment Links, Prices, and Products. If you also want booking-page deposits, add Checkout Sessions (read and write), and add Refunds (write) to refund from Aiva Chat. Leave everything else off. A full secret key isn't accepted.
Step 3: Add the key to Aiva Chat
Open the Stripe payment links card in Aiva Chat's integrations, paste the key, set your currency and largest payment link amount, and save. Aiva Chat checks the key with Stripe before saving. Our Stripe payment links guide walks through each screen.
Step 4: Switch on the action and write the policy
On the assistant's Actions tab, make sure "Texting a payment link" is on and set its level. Then add your payment policy to AI Training, for example "Ask for a $50 deposit to confirm any first appointment."
Step 5: Make sure texting works
The link is a text from your Twilio number. In the US, that needs an approved A2P 10DLC registration first. Test that your number can send texts before relying on links.
Step 6: Test with a real call and review
Call your assistant, agree to a deposit, and confirm the link arrives and opens your Stripe page. Try an amount over your maximum to check it's refused. After launch, review the actions log on calls to see links sent and any failures.
Common mistakes with mid-call payment links
Not writing a clear payment policy
If AI Training doesn't say when payment is expected and how much, the assistant has nothing to base a link on. Write explicit rules, like the deposit amount for each service, so the amount is always clear from the conversation.
Setting the maximum too high or too low
A maximum far above your typical deposit removes a useful safety net. One below your real deposits means links are refused and customers wait for a callback. Set it just above the largest amount you'd normally collect by phone.
Forgetting texting registration
In the US, an unregistered number may not deliver business texts, so links silently fail to reach customers. Complete A2P 10DLC registration before turning links on, and test delivery to a couple of real phones.
Promising links in website chat
Links are phone-only. If your instructions tell chat visitors they'll get a payment link, they won't. Tell the assistant to point chat visitors to your booking page, where a deposit can be taken, or to pay at the appointment.
Letting the assistant handle disputes
A caller disputing a charge or asking for a refund needs a person. Set the handoff option for billing and refund questions so those calls transfer to your team rather than ending in a fresh link.
Best practices for Stripe payment links
- Use a restricted key with only the three required permissions. Never paste a full secret key.
- Write deposit amounts per service. Clear amounts mean clear links.
- Set a sensible maximum. Just above your largest normal phone payment.
- Register for US texting first. Links travel by SMS from your Twilio number.
- Transfer refunds and disputes to staff. Use the billing and refunds handoff trigger.
- Check the actions log weekly at first. It shows each link as Done or Failed.
- Pair it with your CRM. Connecting HubSpot logs the contact and call alongside the payment.
Conclusion
The payments most likely to slip are the ones agreed on the phone and sent later. The customer was ready, the call ended, and the link arrived after their attention had moved on.
If deposits or advances come up on your calls every week, mid-call links are one of the easiest wins in Aiva Chat to switch on, and they cost nothing extra beyond Stripe's normal fees. If payment rarely comes up by phone, or most of your customers book through website chat, where links aren't available, you can skip it.
The setting to get right is the maximum amount. Set it just above your largest normal phone payment, so the assistant can handle routine deposits on its own while anything bigger waits for a person. For the rest of what connects to Aiva Chat, the integrations page lists every option.
If your team regularly ends calls with "I'll send you a link," start by counting how many of those links got paid last month. That's the gap this closes.
Ready to collect payments during the call?
You can try Stripe payment links on your own calls before committing. Set up an assistant, add your payment policy, connect a Stripe restricted key, and call it to watch a link arrive.
Payment links aren't an add-on; they come with the plan you're already on. The only new costs are Stripe's processing fee on each payment and the text itself on your Twilio bill.
Start a 14-day trial (no card needed) and send yourself a $1 test link from a call, or book a demo if you want help drafting deposit rules for each service.
Posts from the people building Aiva Chat in Rajkot — how the product works, what we have learned building it, and guides for getting the most out of an AI receptionist.