Integrations
Network International
How your agents send payment links from your Network International account in a conversation and confirm the payment, without ever seeing card details.
If your business takes online card payments through Network International, a payments company serving businesses across the Middle East and Africa, your agents can use it in the conversation. When a customer is ready to pay, the agent sends a payment link from your Network International account in the same conversation, and confirms when the payment has gone through. The agent never sees or handles card details: the customer pays on Network International's payment page, so card data stays with Network International. 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 registration fee link sent to a buyer who has just reserved a unit |
| Confirm the payment | The agent reads the payment status and confirms to the customer | "Your payment has been received and your reservation is secured" |
| Follow up on instalments | Reminders as each instalment on a payment plan falls due, each with a link, configured during implementation | A reminder that the next construction milestone payment is due on 15 October |
| Follow up on overdue payments | Polite, consistent follow-up with a link, within the contact rules you set, configured during implementation | A second reminder a week after a missed instalment |
| Pass payment problems to your team | A failed payment or a dispute about an amount goes to a person, with a brief | A buyer who asks to restructure a payment plan |
The amount on every link is taken directly from your system record, not typed by the model.
How it connects
The agent connects through Network International's standard API for online payments (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. Network International 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 Network International |
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
Sahel Crest Properties, a Dubai developer, collects instalments through Network International.
- A week before the next milestone payment, the agent sends Yousef a WhatsApp reminder with the amount and due date from the developer's system, and a payment link.
- Yousef asks whether he can pay half now and half next month. Changing a payment plan is outside the agent's permitted actions, so it hands the request to the collections team with a brief.
- The team agrees a split and issues the first amount. The agent sends Yousef the link.
- He pays on the payment page. The agent confirms receipt, and the payment reference is written to his record.
Related
- PaymentsIntegrations
- PermissionsIntegrations
- Personal information redactionSecurity and data protection
- PropertyIndustry 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.