Payhere
for LuumenAI
Easy payment links for accepting online payments
Operate Payhere from the same conversation as the hosts it runs on. Check jobs, queues, and interfaces without a second console; run diagnostic reports; and restart or update with the change previewed, approved, and logged.
The Payhere toolbox
13 tools: 8 read, 5 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet Current CompanyFetch company information for the currently authenticated user.
- ReadGet Current Company StatsFetch payment statistics for the last 30 days with comparison data from the preceding 30-day period (30-60 days ago).
- ReadGet UserFetch information on the currently authenticated user.
- ReadList CustomersList all customers from Payhere, ordered chronologically with most recent first.
- ReadList REST HooksList all active REST hooks subscriptions for the authenticated company.
- ReadList PaymentsList all payments ordered chronologically, most recent first.
- ReadList PlansList all plans in your PayHere account.
- ReadList subscriptionsList all subscriptions ordered chronologically by most recent payment first.
- WriteCreate HookSubscribe to a REST hook for receiving webhook events. Approval by default
- WriteCreate PlanCreate a new payment plan in PayHere. Approval by default
- WriteDelete HookRemove a REST hook listener subscription. Approval by default
- WriteUpdate Current CompanyUpdate the company information for the currently authenticated user. Approval by default
- WriteUpdate PlanUpdate an existing plan's configuration and settings. Approval by default
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — create hook, create plan, delete hook, update current company, and more — is shown as a plan and requires approval by default, including the 1 action classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Payhere — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
SAP BTPGateways, jobs, and subaccounts operated from one governed chat.
SalesforceRecords and integration jobs checked without a second console.
SAP S/4HANAJobs, queues, and records in SAP S/4HANA without a second console.
SAP SuccessFactorsJobs, queues, and records in SAP SuccessFactors without a second console.Put Payhere to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.