CORE-13711 Paymethod migration failed. Client's remote non-card gateway could not be determined.

[Mark_J]

I haven't found this same error anywhere yet so after I opened a ticket I thought I'd post it here as well. Basically after using the auto upgrader from 7.7 to 7.8.1  I ran into two issues, one with smarty templates and the Lara theme (which were quickly resolved) and this one which I can't pin down. 

I don't use Stripe it's not even enabled, I use Quantum Gateway and every client profile page I view pops this error:  "Paymethod migration failed. Client's remote non-card gateway could not be determined. Client ID: "

If anyone saw this error when they upgraded and were able to resolve it,  I'd sure like to know how you did it!

 

[Mark_J]

So it turns out there is an issue with how pay methods were being migrated that is being submitted to the development team to prevent this happening in the future. For now one of the  Support Techs was able to manually provide a workaround, not perfect but it was effective.

[WHMCS John]

Hi all,

I'm pleased to advise this has been resolved in the v7.8.2 maintenance update: https://docs.whmcs.com/Changelog:WHMCS_V7.8.2

[Mark_J]

I can confirm that upgrading to 7.8.2 did fix the issue, sort of.

So now I have:

One payment method display as "Card - XXXX" Showed up after upgrading to 7.8.2 on a client we missed with the workaround.

One payment method display is correct and what I expected "Real card type - real last 4 digits"

One payment method display as "Card - 1234" This was the workaround but didn't update to the real card type with the real last 4 digits after the 7.8.2 upgrade.

[vivithemage]

So this also happened to me. I was able to manually charge the card, but can we get a patch rolled out in general release at some point? This is happening to multiple of my customers with recurring payments done via CC. I have 7.8.2 installed as well. 

Edited September 12, 2019 by vivithemage

[vivithemage]

So this is still an issue for me, I had to force a few overdue invoices because of it. 

[WHMCS John]

The changes in 7.8.2 will help prevent this for users updating from 7.7 to 7.8.2 for the first time.

What was your upgrade path please @vivithemage?

Did you update directly from v7.7 to 7.8.2, or did you update to 7.8.0 first?

[vivithemage]

Good question, is there a way to check? I can't remember if I went to 7.8.0 first or not. 

[WHMCS John]

Hi @vivithemage,

Please review the tblupdatelog table in the database. You'll see a number of entries like:

Installing whmcs/whmcs ($version number here)

 

[vivithemage]

Looks like it went 7.7.0 -> 7.7.1 ->7.8.0-RC.1 -> 7.8.1 ->7.8.2

Everything! haha

[vivithemage]

Now on 7.8.3.

Edited September 27, 2019 by vivithemage

[WHMCS John]

Hi @vivithemage,

Are you finding that Pay Methods created after updating to 7.8.3 are still experiencing the problem? We made some changes to handle situations with invalid data reported by some users.

Pay Methods are created for existing clients when attempting capture on an invoice, visiting their Summary tab in the admin or when the client logs into the client area.

[vivithemage]

I will watch and verify, if no response assume I am good. Or i'll just open a ticket, thanks! 

[sahostking]

I'm running whmcs 7.8.3 and getting this error in logs and error_log file "Pay Method migration failed. Client's remote credit card gateway could not be determined. "

Could it be possibly the customers that have no payment method selected?

 

Edited November 6, 2019 by sahostking

[sahostking]

any update yet?