CBSUBS basket not found on payment

I'm currently testing the Ogone payment gateway and when I return from the Ogone server environment to the website upon completing a payment for one of the membership upgrades I get the following error:

"no suitable basket found" (or along those lines > I translated from Dutch here)

I do get confirmation by email from ogone that the payment has been successful (as the merchant), and also email confirmation from ogone of my order (as the client). All client and merchant information is present in those emails so that does get parsed to Ogone. Just on the return something goes awry for I also do not get the expected email confirmations from cbsubs (neither merchant nor client).

In the backend (cbsubs paid subscriptions) it does state in a new line that the just paid for subscription is replacing the prior (all good). The status however says "registered, unpaid" (not so good).

Please help!

I'm running CB 1.7 and CBSUBS 1.2.2 on a Joomla 1.5.23 install

Please edit your Ogone payment gateway and configure it to send all information possible back on payment. The defaults send too little information for CBSubs to pickup the basket from the return.

I'm attempting to do this but now get errors on the Ogone side of things like: "BackURL too long" and also not having enough space to fill in the necessary post URLs...

I've contacted their support to help me with that and will get back here when sorted and tested!

thanks

Was Ogone support able to assist with your issue? We'll be implementing short url api for a later release to help with long URL problems as well.

Thanks for the follow up. No, Ogone was not very helpful as their stated max chars turned out not to be flexible at all. Thank God I'm using a very short domain name and was able to shorten the url by changing the name of the subfolder the website is stored in.

However, in the tests everything is running fine now...

I can see the need for that API to shorten those URL's :S !

I can see the need for that API to shorten those URL's !

Yup, absolutely; with next release the short URL API will be present as we're hitting this wall more and more with each new gateway we develop. So it's an absolute must have. Also keep in mind the URL can be shortened as follows and will still work.

FROM:
TO:
Of course the live_site still needs to be in the URL, but basically you can remove "&format=raw" to free up some length.