I have set up payment processing through Authorize.net (actually through a reseller) and I am able to successfully perform Test transactions. However, when I perform real transactions, I get a Rejected transaction. When I check the transaction in the authorize.net account I see "General Error (Request rejected by FDC Omaha - Wrong Merchant Type). I assume this is some sort of configuration problem between First Data and authorize.net or me. However, I have no way of telling exactly what the problem is. Authorize.net told me to contact my MSP and the reseller is saying there is nothing they can do to fix the problem (I find it hard to believe.) Is this a setting on my side that I can fix? Help!
You must contact your merchant account provider to fix this error. I've seen this error message several times with our customers at www.authnetscripts.com.
The error indicates a mis-configuration with the processor.
Thanks!
We got this error recently on one of our sites, so we followed the advice to call the merchant account provider.
We called and they told us that sometimes you can get this error because of the type of card (MasterCard, Visa, Discover, AmEx, etc.) that is being used. We tried a different type of card and it processed correctly.
Hopefully that helps someone else who runs into this same problem.
Related
I am trying to use a custom domain for a node.js app I'm hosting on heroku.
For that I am trying to use my card to verify my account, however I keep getting a general error message or I get "Error Unable to verify your card. Please try later or contact your financial institution for help."
I checked with my bank and they said the bank and Visa are allowing the transaction to go through. The charges even show as pending on my bank statement.
So I'm not sure what is preventing my account from getting verified.
Any suggestions would be helpful
To add my credit card to heroku, I supplied all details but when I tried to save details, it gave me this error:
Item could not be updated:
Gateway rejected: fraud
Please what do I do???...thanks
It should probably be an issue with the credit card, this error usually happens when the card is blocked. If you're sure your credit card works and the information you are providing is correct, the best thing to do is contacting Heroku support as only they are able to check what is really happening.
You may receive the error message Gateway Declined: Fraud if you have entered your card multiple times in close succession. This is a temporary lock-out from entering your card again, but will go away after a few hours.
I have recently converted a trial account into a paid starter package and, since I've been assigned a long number, my attempts to send messages via the HTTP API have failed with the following messages in the Message Reports console:
An error occurred while attempting to route the message
Routing error (status 9)
I have confirmed that my username, password, and api id are entered correctly and that the long number has been matched to the active API. I've tried the "Valid Sample Code" provided on the API management console, all with the same result. Below are a few failed message ids if that's helpful for anyone on the Clickatell team.
6d7868662782cfd7d1708996bca066b1
4f837467ed535521ef39d9d885f121f9
2be08f4663a3d9d7cf2e5b9e9cad2d5f
For what it's worth, my trial account worked fine and as expected, so I'm fairly certain that this is not (obvious) user error on my part. I also upgraded a few hours ago; I'm not sure if there is a wait period between account activation and functional service. Thanks for any help on this.
Have you tried setting mo=1 and using your long number as your sender id from=123456789?
make sure you dont add any programming symbols in the text message. i had an exclamation mark and it gave me a status 9 error.
http://api.clickatell.com/http/sendmsg?api_id=xxxx&user=xxxx&from=13055140341&mo=1&password=xxxx&to=xxxx&text=xxxx
For what it's worth, I encountered a very similar problem with the REST API. It also requires the undocumented "mo=1" and "from=[your long number]" fields to be included.
Also, in the FAQ, they have "MO=1" but in actuality, it has to be a lower-case.
From OP:
Clickatell support responded with the following advice that resolved my problem. I also changed the password on my API key during the process which seemed to be part of the issue.
http://api.clickatell.com/http/sendmsg?api_id=xxxx&user=xxxx&from=13055140341&mo=1&password=xxxx&to=xxxx&text=xxxx
"from" is your long number, and because I'm using 2 way messaging , mo=1 needed to be set also. It would have been helpful if this were in the exemplary code provided on the api info and help section, but alas, I had to go through support to get my answer. It took about 2 business days for the response, but they were helpful
I am using omnipay package for my payment method in authorized.
I have two site on the same server, one is a live site that runs ssl and one that is for testing purposes only and do not run ssl.
Now, i dont have problem on paying in our testing site which it runs within our expectation. But, it seems odd in our live site because after entering my billing information, it returns an error that says:
An error occurred while trying to report this transaction to the merchant. An e-mail has been sent to the merchant informing them of the error. The following is the result of the attempt to charge your credit card.
This transaction has been approved.
It is advisable for you to contact the merchant to verify that you will receive the product or service.
Where do u think the problem lies? I really need help on this. Thanks!
This means the relay response URL used by your application is not returning a successful response to Authorize.Net in time (5 seconds). As a result Authorize.Net is assuming the page is not functioning and displaying that message.
You either need to verify the URL is correct, not error-ing out, and responding within a few seconds.
Goal: Only have successful purchases show up on a customer's billing statement. I don't want declined authorizations showing up on their billing statement (as seen in an online banking system) as pending. A customer often will accidentally input an incorrect billing address, for example, followed by a correct one. Together, the two attempts, one successful and one not both show up on their billing statement as pending prior to settlement. This can scare the customer as it looks potentially like they will be charged twice.
Details: When I do an AUTH_CAPTURE (via ActiveMerchant's purchase) or an AUTH (via ActiveMerchant's authorize) which is declined and subsequently want to void that authorization (via ActiveMerchant's void) so as not to have it appear on a customer's billing statement as pending (even though it will settle out after a few days), the gateway can't find the transaction to void using the authorization code returned from the authorization or capture method calls on the gateway.
This is specific to the authorize.net AIM gateway.
Please advise.
Thanks!
If I understand your question correctly, I'm not sure there is a way to do what you want.
This is a limitation of the gateway / merchant account system.
I just stayed at a hotel this past weekend, and when I checked in I was warned that an 'authorization charge' would appear on my card and then go away. The hotel situation is similar to what you are dealing with, and I don't think there is a way around it. Gas stations do it, restaurants, hotels, etc.
It's so common that I wouldn't worry about customers being alarmed. You might put a statement on your payment form saying something about an authorization charge - I've done that in the past on projects.
And for the auth.net specifics - I'm pretty sure you cannot void an auth, thus the error you are getting. The auth code returned is used later on to capture the amount, if needed.