Moneris Transaction Went Through But Not Showing in Payments

Yes it was just one user.

I will get our IT guys to look at the Raw Data and see what went wrong.

Okay we compared the successful payments against the SIGNERROR users and it looks like the only thing in the Raw Data that looks different is the 'response_order_id'. The ones that failed, had a -R01 number for example. The numbers go in sequential order so the next error had -R02.

Can you think of anything else we should look at?

Please contact Moneris and see if they can take a look at the payment on their end. It's possible the payment could be in a holdings state (like PayPal payments going into review).

If they've nothing to suggest please PM backend super administrator login credentials and will take a look. Note I'm just returning from 2 weeks vacation and have a lot of backlog to get through so will not be reviewing installs for about 2-3 days this week.

Hey Kyle,

I talked to Moneris and they said for the transactions that are "Error-Transaction Not Complete", they can't even see anything so it was a communication problem between CBSubs and Moneris. He said suggests that CBSubs call their 3rd Level Integration Support at 1-866-319-7450 with our merchant number and all the details. I will PM you with our backend details again.

All the IPNs you have with SIGNERROR have -r0# suffix applied to response_order_id. I've no idea where that's coming from, but it's causing the verify signature to fail because it's expecting it to be the basket id only.

The way the signatures work is the basket data is MD5 encoded, sent with the purchase, and sent back with the response data. The response data is then passed through the same MD5 encoding and the 2 signatures are compared. If they're not exactly the same then the signature fails. In this case Moneris is altering the order id before sending it back resulting in the mismatch.

You'll notice all payments that came through successfully from Moneris do not have an altered response_order_id.

I've tried to reach their documentation, but it all just lands on non-existent pages (the CA documentation; the US documentation is login gated, but is irrelevant to the CA implementation). So I've no idea what to suggest at this point beyond contacting Moneris regarding the above findings.

I will call them again with this data.

Thanks for looking into it Kyle!