Payment Method Registration Errors

[Maero]

I have had the same thing happen to me, been over a week now and support was not very helpful at all.
Thankfully i believe i have resolved it today. I miss the fc members

[Nibbitz]

Here is some information about those errors from a programmer's view. I am not really defending SE, just giving the rest of you a little bit more information based on personal experience with these kinds of errors in general.

The errors that are being tossed out tells their computers that the bank is declining the card even though it is not. This makes the error really hard to track since mixed into people getting the error in the wrong, there are the cards that the banks are really declining. The invisible lock out is actually common to use in online payment processing because when it is working properly, it protects the legitimate holder of the card in the event that the card being used was reported lost or stolen.
The error seems to be fairly random with who will get an error and when. (For example, my husband just got a subscription three days ago, but my other friend is getting errors.)
I hope that just a little bit of extra information at least helps a teeny bit.

[miles00001001]

snip

Programmer here as well, and I work with online payment processors. In GlobalCollect's logs (if they keep any), they will know the exact reason why a payment was declined given from the respective financial institutions. I had an issue once where the amount being sent to the authorization call was being rounded, so when the value was sent again for the charge request it didn't match the authorization amount and payment was declined.

It's possible they aren't providing SE with the exact reason, or they are and SE is just lumping a given set of errors into these three error codes. There is just too much unknown, and we really don't need to know, which leads to limitless speculation. The problem is that there has been no official response or recognition about the issue.

I have never heard or used a major company that will lockout your account from all payments after one failed attempt.

Now that the purchase of Crysta using paypal is no longer an option the problem seems to have ballooned. Hopefully we will hear a response soon.

[siverstorm]

Programmer here as well, and I work with online payment processors. In GlobalCollect's logs (if they keep any), they will know the exact reason why a payment was declined given from the respective financial institutions. I had an issue once where the amount being sent to the authorization call was being rounded, so when the value was sent again for the charge request it didn't match the authorization amount and payment was declined.

It's possible they aren't providing SE with the exact reason, or they are and SE is just lumping a given set of errors into these three error codes. There is just too much unknown, and we really don't need to know, which leads to limitless speculation. The problem is that there has been no official response or recognition about the issue.

I have never heard or used a major company that will lockout your account from all payments after one failed attempt.

Now that the purchase of Crysta using paypal is no longer an option the problem seems to have ballooned. Hopefully we will hear a response soon.

This echoes my thoughts. I've also written some software utilizing payment processors and we always had a (long) list of error codes that would be returned and what those codes mean. This entire system is ridiculous. Especially when I contact my financial institution and they're saying that there was nothing wrong happening on their end.