Paypal has not been sending payment notifications to merchants

Post by Procrastes » Fri, Aug 01, 2014, 6:21 PM UTC

thenduks wrote: post #25

You can make an API call to check the status of a transaction very easily. When my users are redirected back to my site (thanks page, or similar), I check if their transaction is completed, if not, I kick off an every-five-seconds check while asking the user to hold on while we talk with paypal. I will eventually fail after some number of checks of course, but this means PayPal can stop sending IPNs and everything wi…

Post by thenduks » Fri, Aug 01, 2014, 7:10 PM UTC

Procrastes wrote: post #71

thenduks wrote: post #25

You can make an API call to check the status of a transaction very easily. When my users are redirected back to my site (thanks page, or similar), I check if their transaction is completed, if not, I kick off an every-five-seconds check while asking the user to hold on while we talk with paypal. I will eventually fail after some number of checks of course, but this means PayPal can stop sending IPNs and everything wi…

That's very close to what I've always done. I have a notification to warn me if I have new failed sign-ups due to payment and keep Paypal responses to catch all sorts of problems. It's just good practice to expect things to fail sometimes. That's also why I have my status page hosted with a different provider and twitter status as a back-up for that. My favorite Paypal annoyance is that for split payments there's no…

    # ...

    def initialize
      @request = PaypalAdaptive::Request.new
    end
    
    # ...

    def verified_status( opts={} )
      begin
        opts.assert_keys! :first_name, :last_name, :paypal_account_email
        result = @request.get_verified_status(
          emailAddress: opts[:paypal_account_email],
          firstName: opts[:first_name],
          lastName: opts[:last_name],
          matchCriteria: 'NAME'
        )
        Rails.logger.debug "PAYPAL VERIFICATION: #{result.inspect}"
        return result.success? && result['accountStatus'] == 'VERIFIED'
      rescue
        return false
      end
    end

Post by anurag » Sat, Aug 02, 2014, 3:49 AM UTC

ejr wrote: post #32

BorisMelnik wrote: post #31

Earlier quoted context omitted.

ease of use is still kind of key for me. I pay a lot of people in Europe / Asia and if it weren't for paypal I'd literally have to make a trip to my supermarket Western Union twice a week.

Yes, exactly. When I tell people where they need to send funds, their first question is "do you have a PayPal account?" Western Union, Moneygram and such are all highly inconvenient for both parties. And services like Stripe aren't an option for me due to their restrictions on use as well https://stripe.com/us/prohibited_businesses My work covers multiple items on that list. Compare that to PayPal's https://www.paypa…

Post by yannk » Fri, Aug 08, 2014, 5:15 AM UTC

jcoby wrote: post #74

yannk wrote: post #66

Earlier quoted context omitted.

Here is my solution to the encoding issues, let me know if it works for you (assuming your environment let you access the body of the request without parsing it, or already knows how to parse it correctly). http://blog.cyberion.net/2014/08/parsing-paypal-ipn-requests...

Thanks, but that's a wholly separate issue from what I was talking about. When you have UTF8 data in the IPN, PayPal translates it to win1252 in the IPN. But it verifies the IPN against the original UTF8 data. The only way to fix it is to go into the profile and change the IPN format to use UTF8. There is no programmatic way to set the encoding for IPNs to be sent in and there are no workarounds that I am aware of. I…