Authorize.Net · Decline codes
What does Authorize.Net 250 “This transaction has been declined (blocked IP address)” mean?
Checked
Authorize.Net response reason code 250 means the transaction was submitted from a blocked IP address, so it was declined before reaching the bank. The block comes from your own Authorize.Net fraud settings. If the shopper is genuine, review the blocked address list in the Merchant Interface; if the address is tied to card testing, keep it blocked.
- Type
- Risk block (merchant setting)
- Who declined
- Your Authorize.Net fraud settings (IP blocking)
- Retry
- No, not from the same address.
- Shopper action
- Contact the store if you believe this is a mistake.
- Merchant action
- Check your blocked IP list; remove the address only if it belongs to a real customer.
What PlatformDTC does
PlatformDTC classes Authorize.Net code 250 as a fraud stop: the payment is never sent on to a backup processor, so an IP you blocked cannot slip through another route. On a subscription renewal the code is not retried: the subscription is held past due and the customer gets an email with a link to add a new card.
Why it happens
Authorize.Net checks the shopper's IP address against the addresses you have blocked. A match ends the transaction with code 250.
What the store can do
Look up the IP in your fraud settings. Shared networks (offices, mobile carriers, VPNs) can put a real customer behind an address you blocked for someone else.
For developers
errors[0].errorCode "250". The IP Authorize.Net checks is the customerIP you send in the transaction request, so pass the shopper's real IP, not your server's.
Frequently asked questions
- Why did Authorize.Net block this IP address (code 250)?
- Because the address is on your own blocked list in Authorize.Net's fraud tools.
- How do I unblock an IP for Authorize.Net code 250?
- Remove it from the blocked IP list in the Merchant Interface, after checking it is a genuine customer.
Sources
- Authorize.Net Response Code Tool (response reason codes) — Authorize.Net
- Authorize.Net response codes (JSON list behind the Response Code Tool) — Authorize.Net
Related
- 251 — A Fraud Detection Suite filter declined the payment, including the blocked-IP filter.
- 41 — Your own FraudScreen.Net threshold blocked the payment because its fraud score was too high.
- 252 — The payment was accepted but is held for your review by a fraud filter set to hold.
- 253 — The card was authorized, but a fraud filter is holding the payment for your review.
- 254 — You or your team declined the payment after reviewing a held transaction.
- 295 — The prepaid card only covered part of the amount; another payment is needed for the rest.
- 36 — The bank approved the card at checkout, but the payment failed when it was settled.