Home > Gateway Error > Gateway Error A Valid Amount Is Required

Gateway Error A Valid Amount Is Required

If you know the exact files causing your problem, you can peruse the diff files here and backport the fix from the newer version to the older version. Yeah I've tried running diffs. Or if you have TextPad (a programmer's text editor, you can open the new version file and the old version file side-by-side and run the diff tool to see if they I can't decipher what's a fix to this issue and what's an unrelated change. his comment is here

This was fixed by adding an additional line underneath the line we just corrected: $request->setXAmount($amount,2); In the app/code/core/Mage/Paygate/Model/Authorizenet.Gatewayerror:Avalidamountisrequired. to Gatewayerror:Thereferencedtransactiondoesnotmeetthecriteriaforissuingacredit. I http://www.tipsandtricks-hq.com/forum/topic/authorize-error-5-a-valid-amount-is-required

I'm in the same boat, and don't really want to/can't upgrade to 1.5 at the moment, but I do need to fix this issue. Signature ----- 1) For preserving thy future happiness, thou shalt back up thy HTTP doc directories and Magento database regularly. 2) For preserving thy sanity during module installs and moves, thou Or if you have TextPad (a programmer's text editor, you can open the new version file and the old version file side-by-side and run the diff tool to see if they For us, the problem was twofold.

chiefair - 09 January 2011 01:51 PMIf you know the exact files causing your problem, you can peruse the diff files here and backport the fix from the newer version to Am I just doing something wrong? With these two changes in place, credit memos are now working in Authorize.net. I'm on 1.4.2 also.

When viewing an invoice and click "Refund" button I get that exception message. Thanks for the response. I found this in the release notes for the next alpha version: Fixed ‘Gateway error: A valid amount is required’ appears during create Credit Memo for order, which uses Authorize.net http://www.magentocommerce.com/blog/comments/release-notes-magento-1500-alpha1-december-17-2010/ This is bump number 3.

So I changed the line to do a quick and dirty replace to strip out the non-numeric characters: $request->setXTransId(preg_replace(

But I can't / don't want to upgrade our live store to a preview release. More hints If you are using the "authorize and capture" at checkout option, then you only have one parent transaction, and so the problem does not manifest itself, which is why only some I have reverted to 1.4.2.0, thanks to backing up Signature Sincerely, James Niland Nila NOP Design NOP Design Free Software Support Forum Skip to content Advanced search Board index Can anybody update this?

I tried this fix, maybe I did it wrong? this content Authorize.net, of course, doesn't know what "-capture" means and really only wants the numeric identifier of the original authorization. This is bump number 2. The second problem was that the amount was not being sent in the request.

SO how do I fix this problem with credit memos without upgrading? Board index The team • Delete all board cookies • All times are UTC Powered by phpBB Forum Software © phpBB Group Unfortunately they've also made significant changes to Authorize.net in the preview version. http://meditationpc.com/gateway-error/gateway-error.php Bump 4 I'm there too.

They don't tell you how it was fixed. Blog Support Contact Search My Account Magento extensions and magento themes - best magento marketing extensions My Cart Magento extensions Order upload Custom Order Number The first problem was the $request->setXTransID($payment->getRefundTransactionId()) line.

Since we only authorize at checkout and do capture later, Magento stores the follow-on capture with a transaction ID in the format of "1234567890-capture".

I'm assuming it's something "strange" happening, because I don't see a TON of people having issues with this. So it's fixed in the next preview version. When I attempt to create a refund through the Invoice/Credit Memo I get "Gateway error: The credit card number is invalid." This is for a test order I just created.