Integration · Payments and finance
AI agents for PhonePe Payment Gateway
Create PhonePe checkout payments (a page where the customer pays by UPI, card or net banking), check an order's status, refund a payment and track the refund, with PhonePe PG's Standard Checkout v2 API.
- Actions
- 4
- Read
- 2
- Write
- 2
Actions
What your agents can do in PhonePe Payment Gateway
4 actions. Each one is a tool your agents can call and a step your workflows can run.
Read 2
Look things up. Nothing changes.
Get an order's status
Reads a payment by your order ID: state (PENDING, COMPLETED or FAILED), amount, expireAt and paymentDetails, each attempt with its transactionId, paymentMode.
Get a refund's status
Reads a refund by your refund ID: state (PENDING, COMPLETED or FAILED), amount, the original order ID, PhonePe's refundId, the time.
Write 2
Create, change or send.
Create a checkout payment
Creates a PhonePe checkout for an amount in paise (at least 100, that is 1 rupee) under your own unique order ID, with the page to send the customer back to.
Refund a paymentDeletes data
Refunds all or part of a completed payment, by your order ID, in paise (at least 100), under your own unique refund ID.
A person can approve first
Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything. Actions that delete data ask first by default.
Connection
How it connects
Connect it once in the console, then give it to the agents and workflows that need it.
Enter the sign-in details PhonePe Payment Gateway gives you for its API.
What you enter
- Client ID
- Client Secret
Settings
- Environment
- Client version
Kept safe
- Credentials are stored encrypted with your organization's own keys.
- They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
- Calls go only to the tool's own servers.
Ideas
Ideas to start with
Starting points made only from the actions above. Mix them with any other tool your agents can use.
- 01
Ask about your PhonePe Payment Gateway data
Ask a question in plain words. The agent can get an order's status or get a refund's status in PhonePe Payment Gateway, then answers with what it found.
- 02
Let an agent update PhonePe Payment Gateway
Have the agent create a checkout payment or refund a payment in PhonePe Payment Gateway as part of a larger task. Turn on approval and a person signs off on each change first.
- 03
Share what it finds in Slack
Give one agent PhonePe Payment Gateway and Slack: it can get an order's status in PhonePe Payment Gateway and post a summary to a Slack channel in the same run.
FAQ
PhonePe Payment Gateway and MyDeepAgents
Can MyDeepAgents connect to PhonePe Payment Gateway?
Yes. The PhonePe Payment Gateway connector has 4 actions: 2 read and 2 make changes. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect PhonePe Payment Gateway?
Enter the sign-in details PhonePe Payment Gateway gives you for its API. You'll need: Client ID and Client Secret. The connection also asks for: Environment and Client version. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.
Can an agent change data in PhonePe Payment Gateway without asking?
Only if you let it. Each of the 2 actions that change data can be set to wait for a person's approval before it runs, and the one that deletes data asks first by default.
Can I use PhonePe Payment Gateway in workflows as well as agents?
Yes. Every PhonePe Payment Gateway action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put PhonePe Payment Gateway to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.