Integrations
Stripe
How your agents send Stripe payment links in a conversation and confirm the payment, without ever seeing card details.
When a customer is ready to pay, the agent sends them a payment link from your Stripe account, in the same conversation, and confirms when the payment has gone through. A deposit, a fee or an instalment is settled while the customer is still engaged, rather than after a follow-up call. The agent never sees or handles card details: the customer pays on a Stripe payment page, so card data stays with Stripe. The connection is configured during implementation with your Stripe account.
What the connection lets the agent do
| Action | What it means for you | Example |
|---|---|---|
| Create and send a payment link | The customer can pay in the conversation, for an amount taken from your own records | A deposit link for a desert tour, sent on WhatsApp while the guest is choosing dates |
| Confirm the payment | The agent reads the payment status and confirms to the customer, so nobody pays twice or chases a receipt | "Your deposit has been received. Your tour is confirmed" |
| Follow up on payments due | Reminders for instalments and overdue payments, each with a fresh link, configured during implementation | A reminder three days before an instalment is due |
| Pass payment problems to your team | A failed payment or a dispute about an amount goes to a person, with a brief | A customer who says they were charged the wrong amount |
The amount on every link is taken directly from your system record, not typed by the model.
How it connects
The agent connects through Stripe's standard API (application programming interface: the documented way other software exchanges data with it), using credentials your finance or IT administrators create in your Stripe account and can revoke at any time. The credentials are stored encrypted in your deployment, and every call travels over TLS (Transport Layer Security, the standard encryption for data in transit) version 1.2 or higher. The connection runs from your deployment in your chosen region.
Card numbers are never needed in the conversation. If a customer speaks or types one anyway, it is redacted (removed or masked) from the transcript. Stripe processes the payment under its own terms, as it does for your other online payments. See Personal information redaction.
Permissions
| Permission | Needed for | Default |
|---|---|---|
| Create payment links | Taking payment in the conversation | Only for the purposes and amounts your records define |
| Read payment status | Confirming a payment to the customer | Granted |
| Issue refunds | Returning money to a customer | Not requested. If you grant it, each refund waits for a person on your team to approve it |
| Read card details | Not needed | Not available: card data stays with Stripe |
The agent can only take actions your team has granted. Anything not granted cannot be invoked. Every link sent and every status read is logged in the audit trail. See Permissions.
In practice
Nakhla Travel, a tour operator in Dubai, takes deposits through Stripe.
- Karim asks on WhatsApp to book a desert tour for four on Friday.
- The agent checks availability, confirms the price from Nakhla's booking system and sends a Stripe payment link for the deposit.
- Karim pays on the Stripe page on his phone. The agent reads the payment status and confirms the booking in the same thread.
- His card details never enter the conversation, and the booking, the payment reference and the summary are written to Nakhla's records.
Related
- PaymentsIntegrations
- PermissionsIntegrations
- Personal information redactionSecurity and data protection
- How integrations workIntegrations
- Decision boundariesGovernance and control
Product names and logos are trademarks of their owners. Their mention shows systems Telonic connects to and does not imply partnership or endorsement.