Payment_Due invoice was updated to NOT_PAID Status on adding the Payment method.
The invoice status was updated to Not_Paid even after disabling the setting “Attempt payment collection when the payment method is added“.
Solution
If the merchant faces the issue - Payment_Due invoice was updated to NOT_PAID Status on adding the Payment method then provide the below solution
Step1: Check if 'Attempt payment collection when the payment method is added' setting is enabled.
If the setting “Attempt payment collection when the payment method is added“ is set to TRUE( i.e. enabled), then if a payment method or a card is added, the payment will be initiated and the invoice status will be updated accordingly.
If the merchant does not want to attempt Payment collection on adding the Payment method, then, please suggest they turn OFF the setting “Attempt payment collection when the payment method is added”. This will not update the invoice status to “NOT PAID“.
Step 2:
If the merchant came back stating that the invoice status was updated to Not_Paid even after disabling the setting “Attempt payment collection when the payment method is added“, then do the following.
Settings Configured:
Attempt payment collection when the payment method is added = False (Setting #1)
Continue dunning when Auto-collection changed = false (Setting #2)
In this case, when I add a Bank Account to the customer, this changes the auto-collection of the customer from OFF to ON. Now, though setting #1 is set to false, as Setting #2 is set to false, the dunning in the Payment Due invoice is stopped. This stopping of dunning has updated the status of the invoice from Payment_Due to Not_Paid.
Screenshot #1:
Settings Configured:
Attempt payment collection when the payment method is added = False (Setting #1)
Continue dunning when Auto-collection changed = true (Setting #2)
In this case, when I add a Bank Account to the customer, this changes the auto-collection of the customer from OFF to ON. Now, though setting #1 is set to false, and Setting #2 is set to true, the dunning in the Payment Due invoice DOES NOT STOP. It still continues in spite of the auto-collection being changed because of setting #2. Therefore, the status of the invoice does not seem to change.
And this setting “Continue Dunning if auto-collection is changed“ should be enabled via Backend.
Invoke Action → add_settings → Continue dunning when Auto-collection changed.
Therefore, we suggested the customer to try enabling this setting and the status of the invoice will not be changed.
Reference JIRA:
https://mychargebee.atlassian.net/browse/ASEL2-18752