eWay: CBSUBS basket not found on payment

Hi

I am having the same issue - the return URL from eWay is
http://192.168.3.115:8995/journal/register/pluginclass?plugin=cbpaidsubscriptions&cbpgacctno=1&cbpbasket=13&result=success&cbpid=cbp54104d5e95e9c195505930
But the message I get is

Please contact site administrator to check error log.
No suitable basket found.

Any ideas why this is happening?
Andy

[MOD EDIT]: Please don't resurrect 2 year old topics. The topic you posted in is also about an issue with Ogone and not eWay. I've moved your reply to a new topic. Original topic as follows.

www.joomlapolis.com/forum/153-professional-member-support/180913-cbsubs-basket-not-found-on-payment?start=6

Review the History Log and see if there's an errors around the time of purchase. Also check Notifications to see if the IPN arrived, but maybe errored. The basket is present in your return URL so I've no idea why it would error that the basket doesn't exist unless the basket expired before the payment could complete.

So this is what i see in the History log...

eway: MerchantReference is missing in the transaction result: <TransactionResponse><AuthCode></AuthCode><ResponseCode></ResponseCode><ReturnAmount></ReturnAmount><TrxnNumber></TrxnNumber><TrxnStatus>false</TrxnStatus><TrxnResponseMessage></TrxnResponseMessage><MerchantOption1></MerchantOption1><MerchantOption2></MerchantOption2><MerchantOption3></MerchantOption3><MerchantReference></MerchantReference><MerchantInvoice></MerchantInvoice><ErrorMessage>Invalid Credentials</ErrorMessage></TransactionResponse> . Parsed result: Array of request: sandbox.uk.ewaypayments.com/Result/?CustomerID=xxxx&UserName=xxxx&AccessPaymentCode=2Avrwconm7bOjwPOFlYG29DTFix7XPxcIRPtmEugCLzBkXT9Tn : Please contact site administrator to check error log.

Please see the below topic regarding this exact issue.

www.joomlapolis.com/forum/277-cbsubs-gpl-support/225021-cbsubs-gpl-with-eway?limitstart=0

It's a problem on eWays end. For whatever reason they're reversing two of the parameters sent to them when they send their response. I've no idea why they haven't fixed it yet, but it makes no logical sense to do that. Anyway, the topic above has some proposals for quickfixes you can try.