Skip to content

HamStudy/AuthorizeNetNode

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

2 Commits
 
 
 
 

Repository files navigation

AuthorizeNet — Agentic Skill

An agentic development skill for integrating Authorize.net. Code examples use the Node.js/TypeScript authorizenet SDK, but the API behaviour, error codes, gotchas, and patterns are largely the same across all official Authorize.net SDKs — your agent can translate them to your language with reasonable accuracy.

What it covers

  • Tokenization — Accept.js and Accept Hosted (iframe) for keeping raw card numbers out of your code entirely
  • CIM — Storing customer payment profiles, charging stored cards, hosted profile management page
  • One-time charges — Auth+capture, auth-only, capture, void, refund, split tender
  • ARB — Automated recurring subscriptions, lifecycle management, failure handling
  • eCheck (ACH) — Bank account charges, returns, CIM storage
  • Reporting — Transaction lists, batch export, settlement reconciliation
  • Webhooks — Signature validation, event types, idempotency, delivery policy
  • Error handling — Two-level response check, fraud holds, settlement failures, field constraints
  • Go-live — Credential switchover, endpoint URLs, PCI checklist

Installation

Clone or copy the authorize-net/ directory into your project's .agents/skills/ folder:

your-project/
└── .agents/
    └── skills/
        └── authorize-net/   ← this directory from the repo
            ├── SKILL.md
            └── references/

Most agentic tools will detect it automatically; you may need to adjust the path for some types. When you ask about Authorize.net — charging cards, handling webhooks, setting up subscriptions, or anything else in the scope above — it will load the relevant reference files.

Design philosophy

The skill consistently steers toward integration patterns that avoid raw card numbers entirely. Authorize.net provides Accept.js, Accept Hosted, CIM stored profiles, and ARB subscriptions, which together cover most payment use cases without your code ever seeing a card number. The direct card API is documented but treated as a last resort.

Reference files

File Contents
references/accept-js.md Accept.js tokenization, Accept Hosted iframe, settings, postMessage
references/cim.md Customer profiles, payment profiles, hosted profile page, shipping addresses
references/charging.md Direct card API, transaction types, field constraints, MIT/stored credentials
references/arb.md Subscriptions, scheduling, update/cancel, failure handling
references/echeck.md ACH charges, refunds, return codes, post-settlement return flow
references/reporting.md Transaction lists, batch export, settlement reconciliation
references/webhooks.md Event types, signature validation, retry policy, limitations
references/errors.md Error codes, AVS/CVV codes, fraud holds, recovery patterns
references/testing.md Sandbox credentials, test cards, trigger values
references/go-live.md Production checklist, endpoint URLs, PCI scope

Requirements

  • Agentic development tool such as OpenCdode with skill support
  • Code examples use the authorizenet npm package; other language SDKs follow the same builder/controller pattern and the examples translate straightforwardly

License

MIT

About

Claude Code skill for Authorize.net payment processing integration

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors