cancel
Showing results for 
Search instead for 
Did you mean: 

We welcome your ideas on how we can help improve our documentation and merchant integration services and features. We can't guarantee that ideas will be implemented but your ideas and kudos on ideas will give us valuable insights and feedback we can showcase to our product and developer teams.

By submitting an idea you agree to the PayPal Community Help Forum Agreement and specifically the sections pertaining to user submitted feedback and content.

Checkbox in IPN settings to ignore notify_url and ALWAYS use url specified in settings

0 Kudos

Checkbox in IPN settings to ignore notify_url and ALWAYS use url specified in settings

Problem:

Many merchants such as myself have multiple sales platforms.  When one of these uses the notify_url option to override the url specified in the paypal IPN settings, the IPN message does not reach our server but obviously goes direct to the thrid party sales platform.  This causes integration issues as far as local management of stock levels, automation of shipping labels etc...

 

Asking every sales platform to modify their systems to provide a work around is clearly not the best solution as it only takes one or two sales platforms to refuse, to make the solution unworkable.  However, a complete solution to the problem can be achieved if PayPal adopt the proposal below which I believe requires relatively little development effort.

 

Proposed Solution:

 

In the IPN settings add a checkbox labeled 'Disallow custom url' or something similar.

 

Default value - Unchecked

 

Action when unchecked - As present.  IPN message is sent to the url specified in IPN settings unless notify_url is specified in the payment transaction in which case this should be used instead.

 

Action when checked - IPN message is ALWAYS sent to the url specified in IPN settings.  If notify_url is specified in the payment transaction then this should be included in the IPN message as a key=value pair.  This will enable accurate forwarding by the specified listener to the third party listener specified in notify_url.

 

Regards

Mike

 

 

1 Comment
Moderator
Status changed to: Investigating

Hello @SixFingersMike


Thank you for your very detailed suggestion. I will pass this onto the development teams and will let you know the progress along the way. 

 

Christina