I'm new to php and magento, I'm using the Braintree sandbox environment and everytime I go through the checkout at the point of submitting order I get a pop-up with this error -
There was an error capturing the transaction.
(Transaction declined: Credit card number is required.
CVV is required.)
Websites - http://www.coronafactory.com http://www.tvbedfactory.com
Though they were working before it seems to be effecting both sites, I have checked and cannot find any plugins that would conflict with this plugin, I was told by Braintree "it seems that the Braintree.js widget is being initialized, but the resulting object is never being used." "the file app/design/frontend/base/default/template/braintree/review_js.phtml not being included in your checkout form. This file has the javascript responsible for encrypting the form values and giving them the proper name."
I have put in debugging code 'alert('hello');' in the file with no luck, it seems to not be looking at that file at all.
Braintree dev here. In the event anyone else runs across this problem, here's what happened.
A Magento theme had introduced some errors in checkout.xml that prevented the form from rendering correctly. This in turn prevented the Braintree encryption javascript from triggering properly.
For any problems with a Braintree integration, don't hesitate to reach out to Braintree's Support Team for help.
Related
I have been following this page in the documentation to create a PayPal checkout integration for the purpose of allowing visitors to a site to make donations: https://developer.paypal.com/docs/checkout/integrate/#6-verify-the-transaction. It seems that the more simple donations buttons cannot be used, as it is a requirement that donations are saved to a database table.
I have so far implemented all of the integration up to some of part 6, which verifies the transaction on the server. The code provided on the page (I am using PHP) is not clear and all of the examples of server side validation that I can find refer to purchases, which do not apply to donations. However, even without this, in sandbox mode the integration appears to work. Would this also work in live mode without server validation (and there is no concern of a third-party editing "prices", as this is a donation, so why not let them pay whatever they like?)? If server validation is necessary, what resources are there that exaplain/demonstrate how to do server-side validation of transactions for simple payments (e.g. donations) that do not involve purchases?
Thank you for reading.
Per your own requirements, you want it to call your server after capture, so that it saves a record of the transaction in your server. Everything else is optional, and as you mention may not be needed for any purpose.
I have a custom website with a custom shopping cart built in. I am using the Paypal API Standard Payments method to send the shopping cart information over to Paypal & then returning on a return URL to my order_process.php page. Once it returns to my website, the code updates information in our database to sign members up for events, give them a membership etc.
Everything was working fine until Paypal flagged our account due to the high increase in payments coming in within a short period of time.
I spoke with a supervisor over at Paypal & they lifted the flag from our account.
We did not change anything on our end but now the site is not working properly anymore. It sends the information over to Paypal, takes the payment successfully & comes back to our site.
Once it gets to the line in code
$result = execute_payment($_SESSION["payment_id"], $_GET["PayerID"]);
It crashes with an error: "Method PayPal\Api\Sale::getTransactionFee() does not exist"
I've spoken to Paypal numerous times and they keep saying they will call me back with no return phone calls. I've extensively Googled this error and cannot find anything on this topic. I'm at a lost of what to try next and this is causing a lot of disruption because we are processing a high amount of transactions. I switched the site over to a development domain and tried on Sandbox mode and am still receiving the same error message.
Any help at all will be greatly appreciated.
Our site has just started displaying this behaviour too, I don't understand what is going on. It was working perfectly this time last week.
Maybe there is a new version of the PayPal PHP SDK I need to download!?!?
Help!
-- UPDATE: found this on the PHP SDK wiki: "Seeing this error: 'Method PayPal\Api\Sale::getTransactionFee() does not exist' in paypal/vendor/paypal/rest-api-sdk-php/lib/PayPal/Common/PPReflectionUtil.php:73, Please upgrade the SDK to latest version v1.2.1."
See https://github.com/paypal/PayPal-PHP-SDK/wiki
I've downloaded the new SDK and am integrating it now. Will update when done ...
-- Another Update: Updated our test site to use version 1.2.1 of PHP SDK, and everything works fine against the sandbox. Not sure which language/SDK you're using, but might be worth an update?
I just spoke with an engineer over at Paypal. Apparently they updated some of their code and are aware of this issue. They are currently working on a fix to the problem.
I am integrating "FCMBwebpay" payment gateway api with php magento. I have integrated it with form and added required parameters. Now when i click on "Pay" button, parameters send to the FCMBwebpay site. Then after selecting "Visa/Mesterio" card and adding test card number
Card no: 4111110000000211
cvv: 123
Exp. date: 05/17
When I submit it, then it's redirect to blank page and getting error
Prefix not found! For PAN:4111110000000211"
Here is a screenshot of the error:
Please help me to solve this error.
Thanks in advance
Magneto has a fixed list of BIN numbers that it knows about. That list is a production list that does not contain manufacturer and issuer test numbers.
Your test number will NOT be validated by Magneto because it has no knowledge of it.
I don't know a great deal about Magneto, but I would take a guess that if you dig into the documentation for it, there will be a way of adding that BIN prefix into the system so that it does recognize it, and allow you to test things correctly.
I have integrated CCAvenue to my website done in php Yii framework .The transaction works perfectly in 95% cases but sometimes I'm getting an error like this.I have searched in google and ccavenue docs, but didn't find any clue.Please help me.
Error Code: -1
Error Description:Null+Pointer+Exception%21%21%21
Well am not so well versed with the scripting errors but I encountered this issue while making payment on one of the portals. Here is my observations on it.
While attempting to make payment using 'Master card', the error was frequent.
I tried adjusting the strings (like commas, space etc) in all the information I had filled but to no avail.
Hence I changed the credit card from Master card to VISA card and this change of card led to successful processing.
I wonder if this is in any relevance, with your query. But I assure you the error is same as yours.
I have confirmed that it's the problem with CCAvenue. There is nothing to do in our end.
I'm putting sagepay into a PHP powered site.
So far I've had no trouble integrating the Form into the site, their docs are great compared to paypal (mutter mutter)
However I noticed in the dev guide for form integration, they say you can't rely on sagepay sending the customer back every time as they could close the browser, or navigate somewhere else etc.
At the same time, I don't want to move everything out of the user's cart and into an order before I know it's been confirmed / payed for - otherwise if they cancel or the transaction fails somehow on sagepay's end, their cart will be wiped out when they come back, making retrying the transaction a pain for the user, and I will have a duff order polluting my database.
So what I want to know is if there is a way to get sagepay to send a request to the site when something happens with a payment, similar to paypal's Instant Payment Notifications?
EDIT:
Or are they only saying it's patchy because they can't garuantee it, but it works enough of the time to practically rely on it?
Sagepay (AKA Protx) form integration redirects the user automatically once the transaction has completed.
For small sites, i advise my clients to always check the sagepay transaction logs (on the sagepay site) before sending out any goods.
You should be logging the order before they go to Sagepay. Then changing it's "status" to paid when they get redirected back to your site. This gives you a bit more of a paper trail to pick up any possible issues.
If you want a more robust solution. Try Sagepay direct integration. It has more requirements and is harder to integrate but on bigger projects (where you can't manually check orders) it's usually required. Mainly because users can stay on-site without having to go off to Sagepay to make payments.