After updating SSL certificates in 2016, my PHP integration of PayPal Standard has been working fine. I recently received a notice from PayPal saying, "Your integration is passing invalid or incorrect data to PayPal in one or more of your payment buttons. To ensure you can continue processing payments, please update your integration before January 18, 2017." The notice points to guidance that simply says to make sure your buttons comply with the Website Payment Integration Guide.
I can find nothing in my Pay Now button that sends data that does not meet the standards in PayPal's integration guide. I am unaware of any recent change made by PayPal that requires an "update."
Can anyone enlighten me or point me to a source of information on this January 18 "update."
Related
I recently added a plugin on my website which has a payment system.
This plugin asks for PayPal Client ID and Secret to test the payment system through sandbox.
As per the instructions, I created a business and a buyer account. To be sure, the business in US and buyer in India.
I used the plugin and reached the payment page, where I entered Buyer's credentials and logged in.
The next page, asked me to enter Credit card details and I added it.
When I pressed "Add" button to add credit card, nothing happened and the payment stuck.
Please help me with the issue.
This is a known issue as of today
Initial Notification: We are aware of an issue preventing merchants
from completing payments in the sandbox environment. When attempting a
payment, affected merchants are receiving the error: "Please add a
debit or credit card to complete your purchase." We are actively
working to resolve this issue.
The incident is on-going and currently there is no ETA for a fix.
https://www.paypal-status.com/incident/sandbox
UPDATE 16th August 2018
Issue has been fixed.
Since this week the forwarding to our site after payment does not work anymore in production mode, while it still works within the sandbox.
Actually we use PDT for the direct forwarding and IPN as backup. For some reason the payment is not finished fully. There seems no PDT or IPN connection to be established from PayPal since beginning of this week.
A payment from March 9th was successful, but all payments since March 11th are marked as successful on the PayPal page, but our site "does not know it", so customers don't get their accounts updated.
When trying to track the bug, I switched to the sandbox, but there everything works fine there.
Has PayPal changed something recently? (The design during payment process ist now, but I don't know since when...)
Thanks!
The biggest downfall with PDT is the message is only sent once, where as IPN is repeatedly sent until the server responds with the correct message. You can run both, but from my experience it is very uncommon (and I build eCommerce systems for a living). Recently a lot of my company's clients who run PayPal as their payment method have come to us with a similar problem (even more so with RBS WorldPay). And the solution has been to try the following:
Confirm that the IPN listener URL is still working and pointing to
the right site (some people try to use one PayPal account for
multiple sites, and change it to the 2nd site not thinking it will
stop IPN for the 1st site).
Make sure the latest version of the PayPal gateway is installed (if
on OpenCart / WooCommerce / Magento / etc...). The latest version
requires SHA-256.
Ensure the server has SHA-256 enabled, as above PayPal is now asking
users to make sure they have it for the hashing to work.
Ensure that an SSL certificate is installed. It is not yet a certain requirement, but in this day and age if you don't have one, you are not likely to get many orders. Also for some strange reason it has fixed IPN for some clients.
Hope this helps!
I've been using the PayPal's IPN system for over several years. I have a PHP script that's been processing online eCommerce payments on my web site without any issues.
Today I received the following email from PayPal:
Update your integration before 1/18/2017.
Effective 1/18/2017, your PayPal Payments Standard (also known as
Website Payments Standard or HTML buttons) integration will be
affected by updates we’re making to enhance the checkout process.
We’ve identified your integration as passing either invalid or
incorrect data to PayPal in one or more of your payment buttons. To
ensure your payments continue to process, you’ll need to update your
integration as soon as possible.
What’s Needed
Please check out these FAQs for more information on common integration
issues. Additional details can be found in our Developer documentation
here.
Here are some of the benefits you’ll receive with your updated
integration:
sales blah-blah...
As always, if you need help or have any questions, give us a call or
visit our Help Center.
Thank you for being a PayPal customer.
I checked my integration script and it is passing their "most common problems" from here.
So my question is, did anyone figure out how to test your IPN script with their new update to know what exactly has been identified as passing incorrect or invalid data to PayPal?
I am beginner with Paypal Recurring Payment.
I have created a recurring profile on Sandbox account. The period was of 4 days.
So the scenario was like, i have created profile on 25th Dec 2014 and the due date for first payment was 30th Dec 2014.
However on due date, paypal didn't charge the recurring amount to the profile.
I came across this issue around 3-4 times. I tried google as well but didn't get the solution.
Please advice.
Thanks
I had similar kind of issue when I first, started implementing the paypal recurring payment services on my oscommerce based website. It took completely 10-15 days to understand and fix this issue.
Ref: https://stackoverflow.com/questions/27166006/paypal-recurring-profile-not-charging-automatically
I would suggest you to check your code and ensure you are sending correct set of parameters while making call to CreateRecurringPaymentsProfile as the problem lies here itself.
**If you making initial payment, checkout for correct required params
**If you are charging one time payment and then creating recurring profile, then you need to checkout whole process.
Ref: http://www.makemypost.com/implement-recurring-payment-using-paypal-express-checkout/
At the below of the page you can get complete source code from google for implementing recurring payments.
Thanks
When I make SetExpressCheckout API call against PayPal live server I receive following error:
"You are not signed up to accept payment for digitally delivered goods."
The error indicates quite clearly that I should enable digital goods option from my business PayPal account. I found out that it should be possible to enable "Digital Goods with Express Checkout" on the My Business Setup page. However when I choose the option "Change" -> "Add new" I'm taken to page where the available options are displayed and when I choose "Digital Goods" I'm just taken back to My Business Setup page without any notifications and no visible changes. It seems that adding Digital Goods as an option is not working. What I noticed there was the text "Requires Sign-up" only in this Digital Goods item, which could be the missing part but I don't know what it actually means or where I should Sign-Up.
Anyone has any ideas how to solve this "You are not signed up to accept payment for digitally delivered goods." problem when using Express Checkout API?
I had this same issue when I took our update from NVP to SOAP live earlier this year.
Despite what their support/docs say, the option to enable digital downloads via PayPal's web interface has been broken for some time as you noted (was still broken as of May 28, 2014, almost 9 months after your question). I was not satisfied to remove the "Digital" tag from the API call, so I gave their tech support line a call.
After the support person agreed that the web interface was broken, they manually enabled digital goods for my merchant account from their end. They said they also finally logged the issue with the interface in their tracker, but if you still have issues with "Digital" just give them a call and they will activate it for you.
The solution was to not to use Digital tag in the SetExpressCheckout API call.