Fixed
Authorize.net credit card transaction statuses from gateway responses
10 months ago
Authorize.net credit card authorizations, captures, voids, and refunds now report approved or declined from the gateway transaction response, not only when the outer API call succeeds. Your transaction records and webhooks reflect what the gateway decided on each step.
- A declined gateway response no longer appears as an approved transaction when the API wrapper still returns success.
- Capture, void, and refund steps use the same response-code mapping as authorization, so status stays consistent across the payment lifecycle.