Payment Gateway Error

1 year 1 month ago #333066 by krileon
Replied by krileon on topic Payment Gateway Error
Have reviewed your install and went back 6 months worth of payments. Only this one has failed and did so in this way. It was a PDT, which means a redirect from PayPal back to your site. Based off the $transaction_info in the notification the API call to PayPal went haywire for whatever reason and PayPal returned an unexpected large chunk of HTML.

This seams like it was a temporary issue at PayPal. You've had several PDT and IPN notifications since then that were perfectly successful. Please let me know if and when this happens again as we might have to contact PayPal directly to see why their API endpoint failed like this. Specifically it was a call to their &cmd=_notify-synch that seamed to fail.


Kyle (Krileon)
Community Builder Team Member
Before posting on forums: Read FAQ thoroughly + Read our Documentation + Search the forums
CB links: Documentation - Localization - CB Quickstart - CB Paid Subscriptions - Add-Ons - Forge
--
If you are a Professional, Developer, or CB Paid Subscriptions subscriber and have a support issue please always post in your respective support forums for best results!
--
If I've missed your support post with a delay of 3 days or greater and are a Professional, Developer, or CBSubs subscriber please send me a private message with your thread and will reply when possible!
--
Please note I am available Monday - Friday from 8:00 AM CST to 4:00 PM CST. I am away on weekends (Saturday and Sunday) and if I've missed your post on or before a weekend after business hours please wait for the next following business day (Monday) and will get to your issue as soon as possible, thank you.
--
My role here is to provide guidance and assistance. I cannot provide custom code for each custom requirement. Please do not inquire me about custom development.
The following user(s) said Thank You: petekuhn

Please Log in to join the conversation.

Moderators: beatnantkrileon
Time to create page: 0.172 seconds

Facebook Twitter LinkedIn