Integration · Payments and finance
AI agents for Authorize.Net
Look up Authorize.Net card transactions, settled batches and the transactions in them, capture, refund or void transactions, and list or cancel recurring billing subscriptions, in production or the sandbox.
- Actions
- 10
- Read
- 6
- Write
- 4
Actions
What your agents can do in Authorize.Net
10 actions. Each one is a tool your agents can call and a step your workflows can run.
Read 6
Look things up. Nothing changes.
Get merchant details
Reads the merchant account's settings: name, whether it is in test mode, its processors, accepted card types and currencies, and the payment gateway ID.
Get a transaction
Reads one transaction by its transaction ID: type (authCapture, authOnly, refund …), transactionStatus.
List unsettled transactions
Lists transactions not yet settled (authorized, captured and waiting for the next settlement, or held for review), newest first unless asked otherwise.
List settled batches
Lists the settlement batches between two dates at most 31 days apart (the last 24 hours by default), each with batchId, settlementTimeUTC, settlementState and paymentMethod, and with statistics.
List batch transactions
Lists the transactions in one settled batch, newest first unless asked otherwise, each with transId, submitTimeUTC, transactionStatus, invoiceNumber, customer name, card type.
List recurring subscriptions
Lists Automated Recurring Billing subscriptions of one kind: active, inactive, expiring this month, or with a card expiring this month.
Write 4
Create, change or send.
Capture an authorized transaction
Captures a card transaction that was only authorized (authorizedPendingCapture), for its full amount or a lower one, so it settles in the next batch.
Refund a transactionDeletes data
Refunds all or part of a settled card transaction, within 180 days, to the same card: give the transaction ID, the amount and the card's last four digits (from Get a transaction).
Void a transactionDeletes data
Voids a transaction that has not settled yet (authorized, or captured and pending settlement), so it never charges the card.
Cancel a recurring subscriptionDeletes data
Cancels an Automated Recurring Billing subscription by its ID so it charges no more.
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 Authorize.Net gives you for its API.
What you enter
- API Login ID
- Transaction Key
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 Authorize.Net data
Ask a question in plain words. The agent can get merchant details, get a transaction or list unsettled transactions in Authorize.Net, then answers with what it found.
- 02
Let an agent update Authorize.Net
Have the agent refund a transaction or void a transaction in Authorize.Net 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 Authorize.Net and Slack: it can get merchant details in Authorize.Net and post a summary to a Slack channel in the same run.
FAQ
Authorize.Net and MyDeepAgents
Can MyDeepAgents connect to Authorize.Net?
Yes. The Authorize.Net connector has 10 actions: 6 read and 4 make changes. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect Authorize.Net?
Enter the sign-in details Authorize.Net gives you for its API. You'll need: API Login ID and Transaction Key. 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 Authorize.Net without asking?
Only if you let it. Each of the 4 actions that change data can be set to wait for a person's approval before it runs, and the 3 that delete data ask first by default.
Can I use Authorize.Net in workflows as well as agents?
Yes. Every Authorize.Net action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put Authorize.Net to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.