Notify url parmeter problem?

  • Resolved Begin

    (@bentalgad)


    7 years, 9 months ago

    I use a link to create a subscription.

    The link format is:
    https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=(the button's id)&custom=(some stuff i need)&notify_url=<?php echo site_url(); ?>/?AngellEYE_Paypal_Ipn_For_Wordpress&action=ipn_handler

    Now when i test it i get nothing (no actions fire) and when i check my ipn history i see that the ipn massage url is ending without the action parameter (https://mydomain.com/?AngellEYE_Paypal_Ipn_For_Wordpress).

    Could it be that PayPal is striping that paramater and that’s why my actions won’t fire?

    Thanks.

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Contributor angelleye

    (@angelleye)

    When using a hosted button you won’t be able to add the NotifyURL parameter to the button code directly. It would need to be added to the Advanced section of the button builder in PayPal. Alternatively, you can just set the IPN URL in the PayPal account profile and that would act as the default IPN handler for all buttons/ payment requests.

    Thread Starter Begin

    (@bentalgad)

    Thanks,

    But i am able to set the notify url with the link and it is working as i wrote beside the end parameter.

    I can’t use the second option you suggested because i have a lot of different sites. and the first suggestion also isn’t so comfortable for the same reason (i have 5 buttons that i use for 30 different sites which mean that if i have to set the notify url in the button it self it would require me to set 150 buttons).

    Isn’t there a way to make PayPal accept that parameter as part of the notify url parameter? or maybe make the ipn listener accept the IPN notifications without the parameter in the end?

    Plugin Contributor angelleye

    (@angelleye)

    When using a hosted button, most additional parameters you add to the form/URL would be ignored. I think “custom” will work from there if I remember correctly, and a few others. So it’s possible that notify_url could work here with a hosted button, but I think I tried it in the past and it didn’t.

    If you’ve had success with that elsewhere, then that means it works, and it should work here too. If that’s the case then I would say something about your output isn’t working the way you expect, or there could be an issue happening when the IPN functions are hit. If that’s the case you would be able to see that in the PayPal IPN History and/or your PHP error logs.

    If you aren’t seeing anything under the PayPal IPN history, though, then that means it’s not sending any IPN at all, and that would tell me that notify_url is getting ignored because it’s a hosted button.

    Thread Starter Begin

    (@bentalgad)

    If i have a button with a notify url set to “https://mydomain.com/?AngellEYE_Paypal_Ipn_For_Wordpress&#8221; will i see something under the PayPal IPN history when buying with that button?

    Plugin Contributor angelleye

    (@angelleye)

    If it’s not a hosted button then yes, you would see something under IPN history in PayPal. If it is a hosted button and you add notify_url then it might trigger and it might not. I haven’t specifically tested that in a while. If you don’t see anything under IPN history in that case, then no, it didn’t trigger.

    Thread Starter Begin

    (@bentalgad)

    If i will use the dynamic html button way (with no saved button) and set the notify_url to “https://mydomain.com/?AngellEYE_Paypal_Ipn_For_Wordpress&action=ipn_handler&#8221; will it work properly?

    Plugin Contributor angelleye

    (@angelleye)

    Yes, that should work just fine.

    Thread Starter Begin

    (@bentalgad)

    Ok, i will try that. i thought i can i avoid that little unsecure way, but guess i will have to use it. thanks.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Notify url parmeter problem?’ is closed to new replies.