rtddev
Forum Replies Created
-
Forum: Plugins
In reply to: [PayPal for WooCommerce] REST API | 401 Unauthorized@angelleyesupport – one other thing I just learned.
PayPal is not enabling any new accounts with the ability to process credit card payments via the REST API.
Some older accounts are grandfathered into having the ability to use the REST API, but any newer accounts won’t be able to use the REST API.
They’ll have to use Websites Payment Pro, Payments Pro 2.0 (PayFlow), or Braintree.
If you use Braintree, then you don’t have the convenience of going to one single account to see both Credit Card & PayPal transactions.
I do recall reading something about the above limitation somewhere before, but PayPal Manager support just confirmed to me that the REST API is in a temporary holding pattern.
As such, instead of REST, we’re now using PayFlow within the plugin, and everything is working good so far.
Forum: Plugins
In reply to: [PayPal for WooCommerce] REST API | 401 Unauthorized@angelleyesupport – done! Thanks.
Forum: Plugins
In reply to: [PayPal for WooCommerce] REST API | 401 Unauthorized@angelleyesupport – Looks like we never signed up for PayPal Pro on this particular PayPal account.
Just signed-up, so I think we’ll be good to go once our application has been processed/approved.
I’m going to go ahead and mark this as resolved since it’s not related to the plugin.
Thanks for your timely response!
Forum: Plugins
In reply to: [PayPal for WooCommerce] REST API | 401 Unauthorized@angelleyesupport – Thanks Oliver.
I’ll give them a call, see what they say, and report back here in a bit.
Forum: Plugins
In reply to: [WooCommerce PaySimple Payment Gateway Integration] INTERNAL SERVER ERROR@rtaveira Sent 🙂
Forum: Plugins
In reply to: [WooCommerce PaySimple Payment Gateway Integration] INTERNAL SERVER ERROR@rtaveira If you’d like to buy a copy of the plugin we made, let me know.
It would be unsupported, but I can connect you with the our developer who can help you further develop it.
We migrated off of PaySimple, so we stopped development — though we were making some pretty good progress.
Let me know.
Forum: Plugins
In reply to: [PayPal for WooCommerce] Invalid Vendor AccountHi Oliver,
Thank you for the clarification.
We have been able to run a successful transaction via Payflow now, so it is possible & likely that we did not save the password information correctly.
It is strange that the API sent back an “invalid vendor” error response, but that would not be the first time I’ve seen odd things like that.
Next up is to confirm that tokenization is working, since that is our primary objective (to store payment information by way of the token).
As for that other post I was referring to, I was sent an email notification with that information that appeared to come from this thread.
Maybe the original author deleted it after they posted it. I’m not sure.
At this point, this particular issue is resolved, so I will mark this thread as such.
If we run into any issues with tokenization, I will open up a separate support thread related to that specifically.
Forum: Plugins
In reply to: [PayPal for WooCommerce] Invalid Vendor Account@angelleyesupport – I just saw another user post something similar related to this issue, but it is not showing up on this thread.
Here is what I received.
dalamar17 wrote:
I am having this same issue and cannot get it to work even with PayPal’s technical engineer. Very frustrated! Have tried creating new payflow accounts, verified all credentials and account status, etc.Forum: Plugins
In reply to: [PayPal for WooCommerce] Invalid Vendor AccountOk, will look into it, but what about the issue I reported wrt the User (Optional) field always getting populated?
That doesn’t seem right. It’s an optional field, and if we don’t enter anything in that field, it should be left blank, right?
Forum: Plugins
In reply to: [PayPal for WooCommerce] Unpaid order cancelled – time limit reached@walshie1987 If I’m not mistaken, that is a native WooCommerce setting.
It’s not likely related to this or any particular plugin.
Goto WooCommerce > Settings > Products > Inventory and remove any value that is present in the Hold Stock (minutes) field.
Normally that is set to 60 minutes (to reserve inventory). If an order is not paid, then WC will cancel the order and release the inventory for use.
If you remove the value from that field, it will disable the option and not auto-cancel unpaid orders.
With the above said, when you stated you “have just taken an order”, which kinda implies it was paid.
If it was paid, and there is a record of it, then the setting above is not the cause.
But, if you received an error stating “Unpaid Order Cancelled”, then I’m pretty sure that order was never actually paid and moved to Processing. So, the above setting change should fix the problem.
Forum: Plugins
In reply to: [PayPal for WooCommerce] PayPal REST API – Save Payment Method Not WorkingThanks Oliver!
Forum: Plugins
In reply to: [PayPal for WooCommerce] PayPal REST API – Save Payment Method Not WorkingThanks Oliver @angelleyesupport
Do you have any idea when it will be updated and released so I can put a reminder on my calendar?
Also, I’m not sure if this is related, or something different, but when I was testing using our Sandbox Credentials, we were getting Response Status 500.
I did 4-5 tests, and each time got the 500 error.
Then, I switched over to the Production Credentials and it worked as expected.
I know the requests were getting to PayPal Sandbox, because we saw the requests in the Sandbox dashboard, but it wasn’t clear why we were getting the 500 response.
This was the error:
[28-02-2018 02:47:08] PayPal\Core\PayPalHttpConnection: ERROR : Got Http response code 500 when accessing https://api.sandbox.paypal.com/v1/payments/payment. {"name":"INTERNAL_SERVICE_ERROR","message":"An internal service error occurred.","information_link":"https://developer.paypal.com/docs/api/payments/#errors","debug_id":"913cc9dd6919d"} [28-02-2018 02:47:08] PayPal\Core\PayPalHttpConnection: DEBUG :Any thoughts?
Forum: Plugins
In reply to: [WooCommerce PaySimple Payment Gateway Integration] INTERNAL SERVER ERROR@javib6 thanks.
We’ve decided to re-write the PaySimple plugin, and have already resolved the Internal Server error issue.
The problem with PayPal & Stripe, is their “simple” pricing is quite a bit more expensive than the current PaySimple pricing my colleagues are paying.
At higher volumes of payment processing, there’s a big difference between high 2% (and low 2% processing fees.
We’ve done some initial fully-loaded pricing comparisons, and even with the $45 monthly cost, it does look like the cost is less to use PaySimple. We’re looking deeper into the reports to confirm that is indeed the case.
We may be able to negotiate better pricing with Stripe of PayPal, but that will be our back-up plan.
At the moment, we have our PaySimple for WooCommerce plugin working in a v1.0 state, but we are quickly adding features to fully leverage the PaySimple API and have a more comprehensive feature set.
Forum: Plugins
In reply to: [WooCommerce PaySimple Payment Gateway Integration] INTERNAL SERVER ERROR@javib6 – So, if you haven’t heard back from them, did you ever find a way to correct the Internal Server error using their PaySimple plugin?
If not, did you find an alternate PaySimple WooCommerce plugin?
If not, did you go a different direction with your credit card processing provider?
2-3 weeks is a long time to not hear back from a business, and we just don’t have that long to figure out the problem.
For clarity, we had no issues testing on Sandbox — everything worked fine, and our test orders processed without any problems.
Once we enabled the credentials for Production, we got the Internal Server error.
I checked the PaySimple end points in the plugin itself, and they did not match the current API information from the PaySimple website. So, I did try changing the endpoints in the code, but that didn’t resolve the issue either.
We’re seeing the following error in our WooCommerce fatal errors log:
CRITICAL Uncaught Error: Call to a member function deepAll()
related to > woo-paysimple.php, line 513I’ve opened a support ticket on the company’s website in hopes that someone will get back to us quickly.
If that doesn’t happen, I may have to ask another plugin developer to see if they can help us debug the issue.
Forum: Plugins
In reply to: [WooCommerce PaySimple Payment Gateway Integration] INTERNAL SERVER ERROR@designguy @javib6 Did you get any resolution of this issue from @dots?
We’re having the same issue.