Take card and bank payments, run subscriptions, and manage billing — right from your assistant, on your own Authorize.Net account.
Authorize.Net actions
Ask in plain language — Praxivara picks the right Authorize.Net action, runs it, and confirms anything sensitive first.
See the full detail of any transaction by its id
List every transaction in a settlement batch
Pull a customer's full payment history
Find payments still pending or held for review
List settled batches with totals for reconciliation
See charge, refund and decline totals for a batch
See your account details and what it supports
Create a saved customer to bill again later
See a saved customer and their payment methods
List every saved customer profile
Change a saved customer's details
Delete a saved customer and their stored methods
Turn a past sale into a reusable saved customer
Save a card or bank account to a customer for reuse
See a saved payment method (masked)
List a customer's saved cards and bank accounts
Delete a saved card or bank account
Take a card payment from a saved method or token
Bill a customer's saved card or bank on file
Authorize a card now and capture the funds later
Capture funds from an earlier authorization
Cancel a payment before it settles
Send money back to a customer for a settled sale
Push money to a card that isn't tied to a sale
Pull a payment straight from a customer's bank (ACH)
Send a payout to a customer's bank account (ACH)
Release a payment held for review so it can settle
Reject a payment that was held for review
Set up recurring billing on a card or bank on file
Change a subscription's amount, name or payment method
Stop a subscription's future charges
See a subscription's amount, schedule and status
Check whether a subscription is active
List your recurring subscriptions
Authorize.Net triggers
Events in Authorize.Net that can start an automation on their own — no clicks required once you set it up.
Fires when a card or eCheck (ACH) sale is APPROVED and captured on your Authorize.Net account.
Fires when a card authorization (hold) is placed without capture.
Fires when a prior authorization is captured (funds moved).
Fires when a refund (card or eCheck) is processed on your Authorize.Net account.
Fires when a transaction (card or eCheck) is voided before settlement.
Fires when a transaction is HELD by the Fraud Detection Suite (or a held eCheck) — it won't settle until approved.
Fires when a previously held transaction is approved and released to settle.
Fires when a held transaction is declined (voided) after review.
Fires when a saved (tokenized) payment method is created, updated or deleted (card or bank).
Fires when a saved customer profile is created, updated or deleted.
Fires when a recurring subscription (ARB) is created.
Fires when a recurring subscription (ARB) is updated.
Fires when a recurring subscription is suspended — usually a failed payment.
Fires when a recurring subscription charge FAILS.
Fires when a recurring subscription (or its card) is about to end.
Fires when a recurring subscription is cancelled, terminated or expired.
What you can ask in plain English
No menus, no automation builder to learn. Type it like you'd ask a capable assistant — Praxivara figures out the Authorize.Net steps and shows you exactly what it did.
Related integrations
Let Praxivara run Authorize.Net for you.
Connect it in seconds and hand over the busywork — with you approving anything that matters. Start your 7-day free trial today.