Well, understand that the interrelationship between the three is needed to resolve the issue, but iDevAffiliate would likely have to identify where they insert themselves into the ZC payment flow (notifiers, files changed, files added, etc.) in order to identify what portion of the issue is "caused" by ZC: ie. perhaps a trigger point is bypassed or their code expects something to happen that doesn't, etc...
That type of information would make it easier to also insert trigger_error type commands to log information that is available at certain points (provided the associated code isn't encrypted) and give iDevAffiliate more information about what is going on so that they can properly integrate with PayPal and ZC.
Bookmarks