PayPal response hasn't required fields - AMT field is deprecated

[alexjhirdg4329]

This issue arises because Magento 1.9.3 expects the deprecated AMT field in the PayPal response, which is no longer provided by PayPal’s updated API. To resolve this, patch the _requiredResponseParams array in Nvp.php to remove or replace AMT with supported fields like PAYMENTINFO_0_AMT. Be sure to test all PayPal flows (sandbox and live) after applying the patch. Alternatively, consider upgrading to a newer Magento version or using an updated PayPal module. Always back up your site before making core code changes.

Regard,

Amber Menu

[idavidloso380f]

Thanks for sharing this—it's helpful to see the full trace and context. Looks like the deprecated AMT field might be causing validation to fail in `_validateResponse()`, especially if PayPal's API no longer returns it consistently. Adding logging there is a smart move—hopefully it sheds more light on what exactly is missing from the response. Kind of like checking your Chili’s menu order—if one item’s missing, the whole experience feels off.

[cuetykidsgbf06]

Having the same issue, did you find a solution?

[muhammadbi48d0]

The AMT field is deprecated in PayPal’s API. Make sure you are using  inside the  object instead. Update your integration to match to the PayPal’s latest API format.

[muhammadbi48d0]

Yeah  the AMT field being may be deprecated is causing issues. Meanwhile  taking a break to the  with FreeCine APK .

[apkdraingmbd9c]

It looks like you’re running into an issue with the PayPal API response. The AMT field has been deprecated in the newer versions of the PayPal API, which is why it isn’t being returned as expected. Instead, PayPal now provides updated fields for handling transaction amounts, usually under purchase_units → amount in the REST API response.

If your integration still relies on AMT, you’ll want to update your code to parse the new structure. You can find details in the official PayPal developer docs, but the key is to stop depending on legacy fields and switch to the newer schema.

For a real-world example, I’ve worked with projects like buggy rental dubai where modern payment gateways and API integrations needed adjustments after PayPal updated their response formats. Updating to the current fields solved the issue.

[wearverve234d3]

The AMT field was officially deprecated in PayPal’s newer API versions. Instead of relying on AMT, you should map your amount values using PAYMENTREQUEST_n_AMT or directly through the Orders API if you’ve migrated to the latest integration. Updating your request parameters should resolve the missing fields issue.