- Authorize.net flagged many of my customers’ transactions as “FDSPendingReview” and none of these transactions went through
- I see that a payment was declined but I want to know why
- I am trying to check out with a payment method on file but it keeps failing.
- I am getting a 1007 error when trying to check out and save my card
- I am not able to perform a refund
- I am trying to use a card reader but the card numbers are not reading right into the payment form
- I am using the ID Tech Augusta smart card reader, but it is not reading or communicating with CP Pay
- After processing a transaction, I get a "500 httpStatus" error. The charge went through but does not generate a receipt.
Troubleshooting Card Charges
Authorize.net flagged many of my customers’ transactions as “FDSPendingReview” and none of these transactions went through.
FDSPendingReview is a status sent by Authorize.net which means that the “Fraud Detection Settings” were triggered. Usually, Authorize.net will decline the transaction but then put the transaction in a pending state so that it can be reviewed. Authorize.net allows administrators to approve or decline these transactions. However, since CP Pay received a decline, if the transaction is approved, CP Pay will not be notified. Depending on your business needs, you may wish to decline these transactions and then notify your customers to try again.
FDSPendingReview transactions will show as an Unknown Merchant Error in CP Pay, which is a generic error for rare or infrequent error messages. To get further information about the exact cause of the FDSPendingReview status, inspect the raw data of the transaction in the activity log. You may see more information such as “FDSFilters: Transaction IP Velocity Filter,” which can tell you which of your settings caused the decline.
You may wish to review your fraud detection settings with Authorize.net and calibrate them toward your level of risk and impact to your business operations.
I see that a payment was declined, but I want to know why.
You may see a general decline or error in the CP Pay activity log, but you can also retrieve the full message by looking at the raw response. Click the View button for the activity/transaction for which you would like to see more information.
The raw transaction data shows you exactly what Authorize.net sent to CP Pay. Look for the errorCode and the errorText.
For additional information about the error, you can look up the error code in Authorize.net’s documentation.
I am trying to check out with a payment method on file but it keeps failing.
Double-check that you don't have CVV required in your payment form fields. When CP Pay stores payment methods for future use, a token is stored and not the card number or CVV. Storing the CVV is not PCI compliant. However, Authorize.net requires all fields to be sent when they are required in your settings. This causes charges against a saved payment method to fail. Un-requiring the field in your settings should allow the charge to go through.
Please note that the CVV is required on the form even though you do not require it in your settings. This is accomplished by setting a parameter when CP Pay talks to Authorize.net's Accept Suite.
I am getting a 1007 error when trying to check out and save my card.
This could be caused by many reasons. Log in to CP Pay and look at the raw response for the activity. This should give you more information. Also, note that a user can only save up to 10 payment methods with Authorize.net. You can look at CivicRec or Authorize.net’s Customer Information Manager to confirm this information.
I am not able to perform a refund.
This could be caused by several different issues. If you have any payment fields required, Authorize.net requires these to be provided when a refund is performed. You can confirm this by checking the activity log. If you see a Missing Form Fields message you will need to check your payment fields and un-require those fields. View the Authorize.net instructions.
You can confirm which fields need to be un-checked by looking at the raw data in CP Pay. You should see something like this.
The following fields are generally safe to require: first name, last name, address, city, state, zip, and phone.
Please note the CVV is required in the form without having to select it in your payment fields. If using payment methods on file, marking CVV as required will cause transactions to fail.
I cannot complete my payment because it says email, company, or another field is required but I don't see those fields.
Authorize.net allows you to control which fields are required in the hosted form and API. However, the accept suite hosted page only shows a fraction of these fields. In order to allow your customers to complete payment, you are limited to requiring only the following fields: billing name, billing address (country, zip, street address, city, and state), and phone number. You can update this in your Authorize.net settings under Payment Form.
I am trying to use a card reader but the card numbers are not reading right into the payment form.
The use of a card reader (such as a MagTek Sure Swipe) is not recommended with Authorize.net. You will want to switch to a different device. Find more information in the Gateway Hardware article.
I am using the ID Tech August smart card reader, but it is not reading or communicating with CP Pay.
The ID Tech Augusta will not work with CP Pay. See the Gateway Hardware article for more information.
After processing a transaction, I get a "500 httpStatus" error. The charge went through but does not generate a receipt.
This can be caused by several things. First, if you are trying to save the card when checking out with payment terminal, you need to make sure that permissions assigned to the user include "Manage CIM Profiles".
Second, check to make sure you have not payment fields required. Authorize.net requires that all required fields be sent on all API calls, even when it does not make sense (such as a card-present transaction) to collect this information. Authorize.net even states that un-requiring all fields can help correct transnational issues.
Third, double-check that you have the latest version of the CP Pay tray application. The latest version can be found here.
If the problem continues to persist, please reach out to Authorize.net and CivicPlus support for additional assistance.
Troubleshooting Setup Issues
If you received a code 87, you have not configured your Merchant Service Provider correctly. All transactions are processed as eCommerce. Please see Authorize.net’s documentation for more information.
Not Clicking Approved Causing Missing Transactions
If you do not click approve on this screen, then the information does not come back to CP Pay. The user will be charged but will not receive a receipt. Be sure to always click 'Ok' once you have the approval.