Integrations
Google Pay
How customers can pay with Google Pay when your agents send a payment link, through the payment provider you already use.
Customers who use Google Pay can pay with it when your agents send them a payment link. Google Pay is a digital wallet: it lets a customer pay with a card saved to their Google account or Android phone, without typing the card details. It appears as a payment option on the payment page of your payment provider, for customers whose device and browser support it. The agent works with your payment provider, such as Stripe, Network International or PayTabs, rather than connecting to Google Pay directly.
What it means for your customers
| Action | What it means for you | Example |
|---|---|---|
| Pay from the link in the conversation | A customer with Google Pay can pay in a couple of taps, without typing card details | A buyer opens a registration fee link from an SMS and pays with Google Pay on their Android phone |
| Confirm the payment | The agent reads the payment status from your provider and confirms to the customer, whichever way they paid | "Your payment has been received and your reservation is secured" |
| Follow up on payments due | Reminders for instalments and balances carry a link, and each link offers Google Pay where the device supports it. Configured during implementation | A reminder for the next instalment on a payment plan |
The amount on every link is taken directly from your system record, not typed by the model.
How it works
The agent asks your payment provider to create a payment link and sends that link in the conversation. When the customer opens it, your provider's payment page offers Google Pay alongside card payment, if Google Pay is enabled on your provider account and the customer's device and browser support it. The customer confirms the payment with Google Pay, and your provider processes it under its own terms.
The agent never sees or handles card details. Card data stays between the customer's wallet and your payment provider. Enabling Google Pay is a setting on your payment provider account, and your provider guides you through any set-up Google requires.
Permissions
Permissions sit with the connection to your payment provider. Google Pay needs nothing more from the agent.
| Permission | Needed for | Default |
|---|---|---|
| Create payment links with your provider | Sending a link the customer can pay with Google Pay | Only for the purposes and amounts your records define |
| Read payment status from your provider | Confirming a payment to the customer | Granted |
| Access to the customer's wallet or card | Not needed | Not available |
The agent can only take actions your team has granted. Anything not granted cannot be invoked. See Permissions.
In practice
Sahel Crest Properties, a Dubai developer, collects registration fees through its payment provider, with Google Pay enabled.
- Dana reserves a two-bedroom unit with the sales team, and the agent follows up the same evening on WhatsApp with the registration fee from the developer's system and a payment link.
- Dana opens the link on her Android phone and pays with Google Pay.
- The agent reads the payment status from the provider and confirms the payment in the same thread.
- The payment reference is written to her record in the developer's CRM (the system that holds its customer records), where the sales team sees it the next morning.
Related
- PaymentsIntegrations
- Network InternationalIntegrations · Payments
- StripeIntegrations · Payments
- PayTabsIntegrations · Payments
- PermissionsIntegrations
Product names and logos are trademarks of their owners. Their mention shows systems Telonic connects to and does not imply partnership or endorsement.