Integration · Payments and finance
AI agents for PayU
Check whether a PayU India payment succeeded by your transaction ID or PayU's ID, list the day's transactions, refund a payment, and track refunds, through PayU's merchant web services (key and salt).
- Actions
- 7
- Read
- 6
- Write
- 1
Actions
What your agents can do in PayU
7 actions. Each one is a tool your agents can call and a step your workflows can run.
Read 6
Look things up. Nothing changes.
Verify payments by transaction ID
Looks up one or more payments by your own transaction IDs (txnid), the reliable way to confirm a payment before shipping.
Check a payment by PayU ID
Reads one payment by PayU's ID (mihpayid) with every parameter PayU keeps: status, amount, mode, bank reference, customer details and error.
List transactions between two dates
Lists every transaction between two dates (inclusive), each with id (mihpayid), txnid, status.
Check a refund
Reads a refund by the request ID refund_payment returned: its status (queued, success, failure, in progress, requested), amount, mode, the bank's ARN and settlement details.
List a payment's refunds and captures
Lists everything done to one payment, by PayU's ID: captures, refunds and cancellations, each with its status, amount, request ID and bank ARN.
List refunds by transaction ID
Lists every refund attempt (successful and failed) on a payment, by your own transaction ID: amounts, statuses, request IDs and dates.
Write 1
Create, change or send.
Refund a paymentDeletes data
Refunds all or part of a captured payment (or cancels one that is only authorized), by PayU's ID, with your own unique refund reference.
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 PayU gives you for its API.
What you enter
- Merchant key
- Salt
Settings
- Environment
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 PayU data
Ask a question in plain words. The agent can verify payments by transaction ID, check a payment by PayU ID or list transactions between two dates in PayU, then answers with what it found.
- 02
Let an agent update PayU
Have the agent refund a payment in PayU 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 PayU and Slack: it can verify payments by transaction ID in PayU and post a summary to a Slack channel in the same run.
FAQ
PayU and MyDeepAgents
Can MyDeepAgents connect to PayU?
Yes. The PayU connector has 7 actions: 6 read and 1 makes changes. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect PayU?
Enter the sign-in details PayU gives you for its API. You'll need: Merchant key and Salt. The connection also asks for: Environment. 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 PayU without asking?
Only if you let it. Its one action that changes data can delete data, so it asks a person first by default.
Can I use PayU in workflows as well as agents?
Yes. Every PayU action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put PayU to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.