Disable Unique Transaction ID validation

Yes it should be an option and not mandatory

hello!

I do agree, I have 90% of my customers pay by bank wire transfer, and the trasaction is most of the time os the same for that customer. even if i don't get a confirmation often just by search the string on old transactions often i found the customer...

this is not the best solution as now i need add the - invoice number to the end, and with that the search function wont work (no wildcards allow)

I have quite a few customers that use checks as payment but even with any form of payment there is a chance of duplication of transaction IDs

Please implement this. Strange if customer pay by cash as we have "CASH1", "CASH2".. etc.. it is just "CASH"!

Please implement this. Strange to have "CASH1", "CASH2" as transaction code, when it is just "CASH"!

The same here, we often have a customer paying by BACS for a number of invoices in one go, so it is supposed to be the same bank transaction ID. Please remove this un-required 'feature' ASAP as it's causing grief.

why it's taking you guys so long to fix this small issue ?

We first raised issues around the new "unique transaction ID" requirements with WHMCS in October 2014 after the first signs of this "feature" were implemented under case #3244 in version 5.3.10. Not only have WHMCS completely failed to address this, but they have made it significantly worse in the mean time by extending it to also include invoice payments in 6.x!

The WHMCS developers seems to either be significantly out of touch with their users or just have a complete disregard for the way that their software is actually used in the real world. It would be trivial to add the option to disable this unwanted and unnecessary "feature", but over 18 months later there is still no sign of it happening.

I was sure it's will be in 6.3, but no :(

Yes, please make the unique transaction id optional. This is rather frustrating.

This is a problem for both Cash and Check clients.

Cash is obvious as presented above.

Checks are odd in that Client A and Client B could both use the same check number.

All was working fine until this was added.

I don't think its a rocket science for WHMCS to make this optional, but rather its a lazy approach. It's becoming really cumbersome to receive cash day by day.

WHMCS, please get going on this.

Yes please its badly required.. we are just not upgrading the version because of it.

Issue also arises where when paying different customers with the same cheque id. This often happens as difference customers pay have the chequue id 000002.

Another option here is rather than make a general setting make it a setting against each payment processor.

You also get this when people by cheque. It is quite possible for two different customers to use the same cheque number.

I noticed this as well when all of the sudden I couldn't do Bank transfers the way we normally do using just BTRANSFER, now we're doing some BTRANSFER random string... It makes no sense.

+1 please fix this, it's really annoying

Hi,

Thanks for your comments and votes so far. This is something that we are currently working on finessing for a future release. In the meantime, duplicate transaction IDs can still be entered via the Billing > Transaction List > Add Transaction tab.

So if you need to enter a duplicate transaction ID, it is possible from that location instead.