"Live" PayPal app w/webhook / REST API & JS SDK causes IPN msgs delivered to IPN handler?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I implemented PayPal app w/webhook using REST API and JS SDK for my customer which has "gone live".
The customer also has a legacy IPN handler registered w/PayPal, still in use, especially for prior made subscriptions.
Purchases/Subscriptions made in the live "new app" via REST API/JS SDK unfortunately also cause IPN messages to be delivered to the legacy IPN handler (with types of 'cart' or 'recurring_payment' ).
Ideally, I don't want new sales via REST/JS SDK to generate IPN messages to the legacy IPN handler, as it will cause confusion as to what is a new purchase and what is a legacy purchase. I can track new sales via webhook, so why is PayPal generating IPN message for the new API???
Is there a way to prevent delivery of these "new API" sales as IPN messages to the legacy IPN handler?

Haven't Found your Answer?
It happens. Hit the "Login to Ask the community" button to create a question for the PayPal community.
- Webhook resend button throws 500 error in REST APIs
- indicating that merchants cannot deliver goods to this address, please choose another address in REST APIs
- I am not receiving the six-digit code required for login via sandbox in REST APIs
- PayPal Instant Payment Notification Warnings in NVP/SOAP APIs