Integrations
PayTabs
How your agents send PayTabs payment links in a conversation and confirm the payment, without ever seeing card details.
If your business takes online payments through PayTabs, a payment gateway serving businesses in Saudi Arabia and across the region, your agents can use it in the conversation. When a customer is ready to pay, the agent sends a payment link from your PayTabs account and confirms when the payment has gone through. The agent never sees or handles card details: the customer pays on the PayTabs payment page, so card data stays with PayTabs. The connection is configured during implementation with your 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 link to pay the balance of a hotel stay before arrival |
| Confirm the payment | The agent reads the payment status and confirms to the customer | "Your payment has been received. We look forward to welcoming you on Thursday" |
| Follow up on payments due | Reminders for balances, instalments and overdue payments, each with a link, configured during implementation | A reminder two days before a balance 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 guest who says a deposit was taken twice |
The amount on every link is taken directly from your system record, not typed by the model.
How it connects
The agent connects through PayTabs's standard API (application programming interface: the documented way other software exchanges data with it), using credentials your finance or IT administrators issue for the integration 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. PayTabs 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 PayTabs |
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
Qamar Stays, a hotel group in Riyadh and Jeddah, takes pre-arrival payments through PayTabs.
- Two days before her stay, Reem calls to ask whether she can pay the balance now rather than at check-in.
- The agent confirms her booking, reads the balance from the reservation system and sends a PayTabs payment link by SMS while she is still on the call.
- Reem pays on the PayTabs page. The agent reads the payment status and confirms receipt before the call ends.
- The payment reference and a summary of the call are written to her reservation.
Related
- PaymentsIntegrations
- PermissionsIntegrations
- Personal information redactionSecurity and data protection
- Travel and hospitalityIndustry guides
- How integrations workIntegrations
Product names and logos are trademarks of their owners. Their mention shows systems Telonic connects to and does not imply partnership or endorsement.