gei Posted February 17 Share Posted February 17 (edited) WHMCS has always handled fraud orders poorly and inconsistently, and this is even worse now with the strange "immutable" invoice issues. For example, when an order contains a single DOMAIN REGISTRATION, and is marked as fraud, we can set the order back to pending by clicking the set as pending button for the order. This previously set the invoice as "unpaid" and the client could complete the order by paying the invoice. Now the invoice is set as "Payment Pending" and the user is not able to pay the invoice at all. The only way to resolve this is to add the disable immutable invoices hack to configuration.php and then manually set the invoice to "unpaid". Then the client can pay the invoice and the domain is registered. What's an even bigger mess is when an order contains a single DOMAIN TRANSFER, and is marked as fraud. If we set the order back to pending, for whatever reason, the invoice stays as "cancelled" - this was the case even before WHMCS 9 and is still the case now (this is likely a bug). Previously we would just set the invoice to unpaid, then manually pay it (or have the client pay it). However the issue then is that even after the invoice is paid in this case, the domain is never actually transferred - we have always had to handle this step manually. What's even worse now in WHMCS 9.0 with domain transfer orders initially marked as fraud, is when we set the order back to pending, the invoice is still "cancelled" and we can't do anything with it. If we enable the hack in configuration.php to allow us to edit the invoices again, we can set the invoice to "unpaid", but now for some reason it has a "credit note" in it so the total amount owing on the invoice is now $0 and there is no way to actually complete the order. What a complete mess. One truly wonders what they do with all the extra money from the extortionate price increases. TLDR: If you receive a domain transfer order that is initially marked as fraud, there is literally no way to complete the order. Edited February 17 by gei -1 Quote Link to comment Share on other sites More sharing options...
WHMCS Product Manager WHMCS John Posted yesterday at 01:57 PM WHMCS Product Manager Share Posted yesterday at 01:57 PM Hi @gei, The Payment Pending status is not a terminal status and the status can be changed to Unpaid or Collections. On the invoice screen click "Manage Invoice" and choose the Options tab, use the Status dropdown to choose Unpaid. Finally click Save Changes. In v9.1 we will implement a routine to transition invoices from Payment Pending to Unpaid when marking an invoice paid. Our case number is WHMCS-25294. 0 Quote Link to comment Share on other sites More sharing options...
gei Posted yesterday at 03:10 PM Author Share Posted yesterday at 03:10 PM You only replied to half my message: What's an even bigger mess is when an order contains a single DOMAIN TRANSFER, and is marked as fraud. If we set the order back to pending, for whatever reason, the invoice stays as "cancelled" - this was the case even before WHMCS 9 and is still the case now (this is likely a bug). Previously we would just set the invoice to unpaid, then manually pay it (or have the client pay it). However the issue then is that even after the invoice is paid in this case, the domain is never actually transferred - we have always had to handle this step manually. 0 Quote Link to comment Share on other sites More sharing options...
Damo Posted 12 hours ago Share Posted 12 hours ago 20 hours ago, WHMCS John said: Hi @gei, The Payment Pending status is not a terminal status and the status can be changed to Unpaid or Collections. On the invoice screen click "Manage Invoice" and choose the Options tab, use the Status dropdown to choose Unpaid. Finally click Save Changes. In v9.1 we will implement a routine to transition invoices from Payment Pending to Unpaid when marking an invoice paid. Our case number is WHMCS-25294. Can you please elaborate on Terminal Status? And the routine to transition invoices in v9.1? There has not been a WHMCS announcement or clear documentation about the immutable invoice changes, yet there are many posts and concerns a detailed document showing what has changed and is expected behaviour would be a good way forward. 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.