Leaderboard

Blesta gives PayPal a unique URL to post each IPN notification to so that the payment can be correctly applied. The URL contains the company ID, along with the internal client ID. This allows payments to be applied correctly even when the same person may have multiple client accounts, even across multiple companies. The issue is one we've discussed internally in the past, and I believe there were limitations to being able to make this work without re-creating the subscription. I suspect it may be possible by creating a file that acts like a proxy, taking the IPN request, and determining the internal Client ID and company to apply it to. Proxying the response back to PayPal. I'll bring it up again on Monday. If you have information about what URL PayPal notifies on whmcs installations, it may be helpful. I would really like this to work out of the box, as it removes an obstacle for migration.

Normally it should work . You can test it and send feedback , is thier any bug i will correct it . Best regards .

It sounds like you may have the same issue as edunjoroge, where no connection could be established over the API because the servers were not able to negotiate which encryption algorithm to use. You could either add support for additional algorithms on your server, which the eNom server also supports (whatever they may be), or you could disable SSL with the sandbox entirely. The latter is the simplest work-around that edunjoroge used, but it means that all sandbox actions will be performed over HTTP, insecurely. It would be possible for listeners to view your sandbox credentials in plain-text. If you wanted to try disabling SSL altogether for the sandbox, update /components/modules/enom/apis/enom_api.php to change the sandbox URL protocol from https to http. i.e. change: const SANDBOX_URL = "https://resellertest.enom.com/interface.asp"; to: const SANDBOX_URL = "http://resellertest.enom.com/interface.asp";