This topic contains 1 reply, has 2 voices. Last updated by Cristián Lávaque 3 years, 6 months ago.
Topic Author | Topic |
---|---|
Posted: Friday Jun 21st, 2013 at 6:53 pm #52347 | |
Hi guys! Sorry to bring this issue up again, I thought I had sorted it, but i obviously haven’t. I moved away from the generic tracking pixel a few months back and integrated the cURL for API notifications for my iDev install. Regular commissions are working fine, but an original recurring payment (that was first set up in the generic tracking pixel days) has gone through today and generated NO COMMISSION. I think I may no why, but I just need a bit of help. My current notification URL for payment notifications is this: No that is tracking: Sale amount Now looking at the original commission that was generated for this referral, I don’t see the user’s IP recorded, so I’m guessing that idev couldn’t match anything, thus no commission was created. The commission record in idev shows the sale amount, Order number which is the PayPal recurring PROFILE ID (NOT TRANSACTION ID), but no other tracking ID’s or IP address records. So for all OLD transactions, I am not going to get any future commissions generated unless I change the notification cUrl. I noticed in your KB article that you now give out a very long URL to use which looks like this: Now this has 3 options and one is called ‘subscriber ID’. Is that the PayPal recurring payment profile ID? If so, that’s what I will need to trigger future commissions. Can I use that URL as it is, with ALL 3 options for order number and does it make sense that only using my limited URL is my problem? Lastly the part that says profile=xxx at the start of the above URL – where do I get my own number for that part. I can’t find it in idev – am I supposed to replace the xxx? Hopefully this will finally iron out this last kink with recurring commissions on my install. Thanks guys, really appreciate it. Ross :) |