The job Use Worth knowing
Take cards on your own checkout page Accept.js in the browser, then createTransactionRequest from your server Accept.js swaps the card for a one-time nonce (opaqueData) that's valid for 15 minutes. Your server never sees the card number. Authorize.net describes this as an SAQ A-EP setup.
Keep card entry off your site entirely Accept Hosted Your server requests a token, then redirects to or embeds Authorize.net's own payment form. Less control over the look of the page.
Charge returning customers without storing cards Customer Profiles (Accept Customer) Authorize.net stores the payment method and gives you profile IDs to charge later.
Bill the same amount on a schedule Automated Recurring Billing (ARB) Authorize.net runs the schedule. Your system still needs to hear when a payment in it fails.
React when a charge, refund or void happens Webhooks Notifications carry part of the transaction. Call getTransactionDetails for the full record.
Reconcile what actually settled Transaction Reporting: getSettledBatchList, then getTransactionList per batch Settlement is batch by batch, so this is the report that should match the deposit, not the day's approvals.