I'm using WooCommerce Authorize.net AIM Gateway in WP 4.0.1
it doesn’t tell specifically what the error is. Instead it gives you a generic “An error occurred…” error and the user doesn’t know for sure what is wrong and what to re-enter.
OR
An error occurred, please try again or try an alternate form of payment
But not telling the actual cause of error.
We have contacted WooCommerce and the vendor SkyVerge and asked about this. SkyVerge said they are working on a new version that does a better job with this. But, those changes are at least a month away.
So I want to grab the response code that Authorize.net returns and show the proper message to end users.
Like here Authorize.net is returning.
Related
I have recently started working on nop commerce 4.2 version.
I have added FedEx plugin for the shipping. refer the following link
https://www.nopcommerce.com/shipping-plugin-for-fedex
while calling the rate service I am getting "Rating is temporarily unavailable, please try again later." error
My App Rate service URL is https://wsbeta.fedex.com:443/web-services/rate
Please help me with a solution.
Thanks in advance.
First, you need to figure out if the response comes from FedEx or generated by the plugin. You need to intercept the communications between the plugin and FedEx. One of the recording proxies should help (f.ex. Fiddler).
Then review is request and response trying to figure out who's wrong. Wrong credentials? Request data? Or maybe the FexEx service is truly down and nobody mans it due to the COVID.
Been struggling with this for hours.
This is a asp.net core 3.0 app.
It emails an activation link.
I then pick up that email in my inbox and click on it.
This link is:
https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.myserver.com%2FAccount%2FActivate%3Fpin%3DwDiC3S&data=02%7C01%7C%7C8311079d8b314d288f7a08d77e73c924%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637116908072496731&sdata=y80XhRTBI%2FOJq6UrN8Yw%2B3nWDjrb96IprWR2IKIouVU%3D&reserved=0
It then emails me a confirmation message 9#by calling that view). But it does this twice.
What is weird is that if I copy and past this url from 1 browser to another I just receive the expected 1 confirmation email.
The only difference I can see is that the safelink stuff add si removed from copying and pasting that link. ie:
https://www.myserver.com/Account/Activate?pin=wDiC3S
I do not know how to debug this?
I have just come across this situation. It has taken me a few days to track down. I have a link within an outlook message and I wrote code to make sure it was not called twice. This code was activated the first time I called it. Eventually I realised that the email client must be calling it twice. I'm going to have to write a work around.
I'm glad I found it. It was driving me mad!
I would consider this to be an outlook bug.
I had a similar problem a while back that seemed to be tied to the email client pre-fetching and visiting the link. You may want to try a different email provider and client as part of your debugging efforts.
Here is a related question on the topic -
How to stop e-mail clients from visiting links in e-mail automatically?
I have this issue couple of days already. With trial and error i just found out the solution with my own testing, you just need to set-up the SMTP configuration with your outlook account.
Using PHPMailer
I have this configuration before
$trans = Swift_SmtpTransport::newInstance()
->setHost("xxxxxxxxxxx.mail.protection.outlook.com")
->setPort(25);
I changed to
$trans = Swift_SmtpTransport::newInstance('smtp.office365.com', 587, 'tls')
->setUsername('xxxxx#xxxxxxx')
->setPassword('xxxxxxxxxxxx');
Now, it's working properly. I think ATP aka SafeLink Protection Feature will work only if the email address(sender) is not verified within your organization.
I am using LinkedIn API to share my contents on the company page. Since last 3-4 days, I am getting an error.
"LinkedIn::Errors::InformLinkedInError: LinkedIn had an internal
error. Please let them know in the forum. (500): Internal Server
Error"
I have not done any code change that shall break my application.
How do I report this error to LinkedIn? What details are required to be shared?
If I were you I'd prepare the shortest code that triggers the problem: just the bare minimum that is needed to replicate it. Send it to them just as if it was a MCVE here on StackOverflow.
Imagine you are the LinkedIn developer solving this problem: how would you like to receive this error report? Ideally if it was some short piece of code that you could run locally and observe what exactly is being sent to the API. (Of course the code has to actually trigger the problem!)
I have a simple checkout form and I'm using Authorize.net's DPM (Direct Post Method) and I keep getting this error message:
An error occurred while trying to report this transaction to the merchant. An e-mail has been sent to the merchant informing them of the error. The following is the result of the attempt to charge your credit card.
This transaction has been approved.
It is advisable for you to contact the merchant to verify that you will receive the product or service.
Any ideas on what might have caused this error? Authroize.net's support had 0 helpful information and they don't store failed API responses.
thanks!
This error occurs when Authorize.Net is trying to contact your server and is unsuccessful. The transaction is approved but they cannot send the user back to your website like you want them to.
Their article Relay Response Basics and Troubleshooting covers this issue in great detail.
we have several PDF report products. We create PayPal buy now buttons for each, and we use PayPal IPN to email the PDF reports upon successful payment. We've been having ongoing issues where some orders just don't seem to get processed by our IPN web service, which is just an ASP.NET aspx page, and uses the standard Request["paypal_key"] parameter processing.
I started doing some digging and seemed to find that the IPN web service is not able to process orders where the product name as configured in the PayPal button contains the ampersand character, or the copyright symbol...possibly others, but that's just what I've observed so far.
PayPal's merchant services logs the IPN messages sent when transactions take place. I looked at the log today for an IPN that we should have received and processed. Here is the IPN, edited for confidentiality:
mc_gross=99.00&protection_eligibility=Ineligible&payer_id=FZKLXR5FF6LMN&tax=0.00&payment_date=08:01:23
Apr 20, 2011
PDT&payment_status=Completed&charset=windows-1252&first_name=Shan&mc_fee=3.17¬ify_version=3.1&custom=&payer_status=unverified&business=email#email.com&quantity=1&verify_sign=AtiSwnZrh-0NXJaYKeFJ5mXp3NePA7jXOzMIt6S.rapcfeP2iL3He53H&payer_email=email#email.com&contact_phone=555-555-5555&txn_id=36P12783M6206263T&payment_type=instant&btn_id=29294177&last_name=Plourde&receiver_email=email#email.com&payment_fee=3.17&shipping_discount=0.00&insurance_amount=0.00&receiver_id=STR4XMP3MUHLS&txn_type=web_accept&item_name=2010
Product Name With & Character
Report©&discount=0.00&mc_currency=USD&item_number=85&residence_country=US&receipt_id=4921-6005-8542-0925&handling_amount=0.00&shipping_method=Default&transaction_subject=2010
Product Name With & Character
Report©&payment_gross=99.00&shipping=0.00&ipn_track_id=b9bQ70Jiv82s3HRqBqLfpw
After doing some testing, I was able to consistently reproduce that the IPN notification process succeeds if the PayPal button is created without the ampersand or copyright symbols. I also called PayPal and they confirmed that they don't encode product names, they just send them over the wire as-is.
We're just using standard ASP.NET request processing to get the IPN values:
Request["receiver_email"]
Request["item_number"]
I'm wondering if anyone else has experienced this issue? I'm thinking that our only resolution is to recreate all of our PayPal buttons, and specify product names that contain no ampersands or special characters. I'm not sure if it would be possible to properly parse IPN notifications otherwise. But would be curious to hear about other's experiences, and possible ideas to parse the IPN messages so that we could continue to allow ampersand characters etc.
Thanks
Shan
UrlEncode your product names, or anything with an ampersand/copyright symbols.
To follow up on this question...the only solution that I was able to come up with was to remove ampersand characters from our product names. It seems that the copyright symbol was also causing IPN processing issues. So we keep our product names within PayPal free of special symbols now.
I wish we didn't have to do this, i.e. that all of our product names specified with PayPal buttons could have any encoding. But, it's a solution.
Try setting the IPN encoding as described here (step 5):
http://support.getdpd.com/entries/167722-paypal-account-setup-troubleshooting