Skip to main content
The Card Payments function lets your agent collect a card payment during a call. When a caller is ready to pay, the agent texts them a secure Stripe payment link, waits while they pay on Stripe’s hosted page, and confirms on the call the moment the payment lands. Card details are entered only on Stripe’s page — they never pass through the call, transcript, or recording. Money settles directly to the merchant’s own Stripe account (each business connects its own account); Telzino is the platform and can optionally take a per‑transaction fee.
This is the Stripe direct‑charge payment tool (funds go to the merchant’s own connected account). It is distinct from the older Request Payment function, which uses Telzino Credit.

​
Prerequisites

Two things must be in place before an agent can take payments:
1

Onboard the merchant to Stripe

Each organization (merchant) connects its own Stripe account so funds go to the right business. Open an agent’s Payments tab and click Set up payments to complete Stripe’s embedded onboarding (no redirect — sensitive data goes straight to Stripe). When Stripe reports the account as active, charges are enabled.
2

Configure Twilio SMS on the agent

The payment link is delivered to the caller by SMS, so the agent needs Twilio configured (Account SID, Auth Token, From number) in its Integrations, plus the SMS function enabled. Without Twilio the agent has no way to deliver the link.

​
Enabling payments on an agent

Open the agent’s Payments tab. The Payment readiness checklist shows the two prerequisites. Once both are met (✅ Merchant onboarded, ✅ Twilio configured), the Enable payments toggle becomes available.
  1. Click Enable to add the payment function to the agent.
  2. Set the Success URL — where the caller is sent after paying (default https://telzino.com/). Configurable per agent.
The toggle stays disabled until both prerequisites are met, and if you later remove Twilio the agent automatically stops offering payments on calls.

​
How it works on a call

1

Caller signals intent

The agent starts a payment only on explicit caller intent, and verbally confirms the amount and purpose first.
2

Agent creates and texts a secure link

The agent creates a Stripe Checkout Session on the merchant’s account (the amount is validated server‑side against a safe range) and texts the hosted link to the caller — the message contains only the link.
3

Caller pays on Stripe

The caller taps the link and enters their card on Stripe’s page. No card data touches Telzino.
4

Agent confirms on the call

When the payment completes, the agent is notified in real time and confirms on the live call — never claiming success unless the payment is confirmed. If the caller needs more time, the agent lets them know the payment can still go through after the call and ends the call. Payments that complete after the call are reconciled automatically and appear in the transaction list.

​
When something goes wrong

The agent only confirms a payment once it’s actually settled — it never says “paid” on its own. Common cases:
  • Declined or failed card — the payment isn’t recorded as paid; the caller can retry from the same link (valid for 30 minutes).
  • Link expires — the Stripe Checkout link expires after 30 minutes; the agent can send a fresh one.
  • SMS can’t be delivered — if the text fails to send, the agent tells the caller so on the call rather than assuming they received the link.
  • Refunds — a refund issued from Stripe is reflected in the transaction list.

​
Where payments appear

  • Reseller support console (Telzino Dashboard → Account Settings → Payment Transactions): every payment across your merchants, with masked customer, amount, and status.
  • Merchant view: each merchant sees their own payments.
  • Refunds and payouts are managed in the merchant’s own Stripe (Express) dashboard — Telzino links to Stripe rather than handling money movement.

​
Use cases

  • Invoices: a caller pays an outstanding invoice during the call.
  • Deposits / booking fees: collect a deposit to confirm an appointment (great with the Schedule function).
  • Point‑of‑need sales: take payment for a product or service the caller is requesting.
While the platform is in Stripe test mode, use test card 4242 4242 4242 4242 with any future expiry and any CVC to try the flow end to end. Test vs. live mode is a platform‑wide setting managed by Telzino — it isn’t a per‑merchant toggle in the agent UI.