Authorize.Net · Decline codes
What does Authorize.Net 124 “This processor does not accept recurring transactions” mean?
Checked
Authorize.Net response reason code 124, "This processor does not accept recurring transactions", means the processor behind your Authorize.Net account cannot process a transaction marked as recurring. Subscription renewals sent with the recurring flag fail until the processor supports it. Ask your merchant service provider whether recurring billing can be enabled.
- Type
- Error (merchant setup)
- Who declined
- Your processor
- Retry
- No, not on this processor setup.
- Shopper action
- Nothing; the store needs to fix this.
- Merchant action
- Ask your merchant service provider about recurring billing support.
What PlatformDTC does
PlatformDTC sends Authorize.Net subscription renewals flagged as recurring, merchant-initiated charges on the saved customer profile, so a processor that refuses recurring transactions would return code 124 on renewals.
Why it happens
Recurring transactions carry an indicator the processor must support. Some processor setups do not.
What the store can do
Contact your merchant service provider and ask for recurring billing to be enabled for your account.
For developers
errors[0].errorCode "124". Triggered by transactionSettings recurringBilling=true.
Frequently asked questions
- Why do renewals fail with Authorize.Net code 124?
- Your processor does not accept transactions flagged as recurring.
- Who can fix Authorize.Net code 124?
- Your merchant service provider.
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
- 17 — Your Authorize.Net gateway is not set up to accept this card brand.
- E00044 — Saved customer profiles (CIM) are not switched on for this account.
- 153 — The wallet payment data (such as Apple Pay) could not be processed as sent.
- 154 — Apple Pay is not switched on for this Authorize.Net account.
- 289 — Your processor will not run a $0 card check for this card brand.
- 19 — Authorize.Net did not get an answer from the card processor (a connection problem).
- 20 — Authorize.Net lost contact with the card processor before getting a response.
- 35 — Your merchant account was set up incorrectly at the processor.