Integration

Authorize.Net integration

Authorize.Net payment gateway by Visa. Process credit card and ACH transactions, manage stored Customer Information Manager (CIM) profiles, run Automated Recurring Billing (ARB) subscriptions, and pull settlement/transaction reports. All operations POST to a single endpoint (/xml/v1/request.api) with a JSON request body whose root key is the operation name (e.g. createTransactionRequest, createCustomerProfileRequest, ARBCreateSubscriptionRequest). Every request body MUST include a top-level merchantAuthentication object with two fields: name (API Login ID, max 25 chars) and transactionKey (Transaction Key, max 16 chars). LiveContext exposes these two values as a 'custom' credential (api_login_id + transaction_key); the workflow author is responsible for populating the merchantAuthentication object in each call by referencing the stored credential - the platform's standard header/query/url_variable injection cannot reach a nested body wrapper. Production base URL is https://api.authorize.net; sandbox is https://apitest.authorize.net (toggle via merchant credentials, no separate API).

Connect Authorize.Net How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Authorize.Net.Built from the 20 Authorize.Net tools below, on the connection you add once.

Common Authorize.Net use cases

plan change
new card add
dunning report
SaaS subscription
ecommerce checkout
ship-and-bill flow
render card on file
batch reconciliation
update customer email
card on file selection

What you can do with Authorize.Net

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Transaction, 7 operations

auth_capture_transactionAuth capture transactionPOSTAuthorize and capture a credit card payment in one call.
auth_only_transactionAuth only transactionPOSTAuthorize a card without capturing - funds are held for up to 30 days.
get_transaction_detailsGet transaction detailsPOSTRetrieve the full record of a single transaction by ID.
get_transaction_listGet transaction listPOSTList transactions inside a settled batch.
prior_auth_capture_transactionPrior auth capture transactionPOSTCapture funds from a prior authorize-only transaction.
refund_transactionRefund transactionPOSTRefund a settled transaction (full or partial).
void_transactionVoid transactionPOSTCancel an unsettled transaction before it settles.

Subscription, 5 operations

cancel_arb_subscriptionCancel arb subscriptionPOSTCancel an active ARB subscription permanently.
create_arb_subscriptionCreate arb subscriptionPOSTCreate an ARB subscription billed on a fixed schedule.
get_arb_subscriptionGet arb subscriptionPOSTRetrieve an ARB subscription by ID.
get_arb_subscription_listGet arb subscription listPOSTList ARB subscriptions filtered by status.
update_arb_subscriptionUpdate arb subscriptionPOSTUpdate an ARB subscription's amount, schedule, or payment method.

Customer profile, 4 operations

create_customer_profileCreate customer profilePOSTCreate a CIM profile to store a customer's payment data securely.
delete_customer_profileDelete customer profilePOSTPermanently delete a CIM profile.
get_customer_profileGet customer profilePOSTFetch a CIM profile with its payment methods and addresses.
update_customer_profileUpdate customer profilePOSTUpdate a CIM profile's top-level fields.

Payment profile, 3 operations

create_customer_payment_profileCreate customer payment profilePOSTAttach a payment method to a CIM profile.
get_customer_payment_profileGet customer payment profilePOSTRetrieve a stored payment method by ID.
validate_customer_payment_profileValidate customer payment profilePOSTValidate a stored payment method without charging it.

Batch, 1 operation

get_settled_batch_listGet settled batch listPOSTList settled batches in a date range with totals.

Use Authorize.Net from Claude Code, Cursor or Codex

Connect Authorize.Net in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Authorize.Net operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Authorize.Net

Create your workspace
Sign up free. Nothing to install.
Connect Authorize.Net once
Add your Authorize.Net connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Authorize.Net integration FAQ

What can you do with the Authorize.Net integration?

LiveContext exposes 20 operations on Authorize.Net, covering transaction, subscription, customer profile and payment profile. Common uses include plan change, new card add and dunning report.