Skip to content
English
  • There are no suggestions because the search field is empty.

Authorize.net Payments Declined in RM but Approved in Authorize.net V7

This applies to: RM, EFunds

We recently ran into an issue with a customer using Authorize.net where their credit card charges were being approved in Authorize.net but being reported as DECLINED in RMA and so the customer was indeed being charged but no payment was created in RMA.

The reason for this was that the Direct Response Delimiter - Default Field Separator was changed in the Authorize.net web portal.

The Direct Response Delimiter - Default Field Separator MUST be set to , (comma) or the transactions will fail.

Please see below instructions below for setting or verifying the Direct Response Delimiter - Default field Separator

1. Log into the web portal

2. Select the Direct Response link from the home page

 

3. Make sure the following settings are exactly as shown [ Delimited Response = No and Default Field Separator = ,(comma) ]