Simple request after fighting to re-subscribed: As a customer, I want better error messages at subscription time.
In a nutshell, I kept getting 'ERROR:Gateway Rejected: avs-gateway_rejected' when trying to sign up. Tried two cards, then decided to google-fu before giving up. A web hosting company (Directnic) had information on errors their customers might receive when accepting payments online. Their article explained that this error is typically associated with the billing address being incorrect. I reviewed the information again, found a typo that was saved in Chrome (saved addresses) which was supplying an incorrect zip code.
At this point, I *AM* a subscriber again, but no customer should ever have to dig up payment processing errors codes to figure out how to resolve this.
I agree. Layman error messages would probably help everyone (of course some errors appear for multiple reasons).
Kudos for having an uncommon problem and solving it yourself. Far too often people will come across a common error caused by user error or a well documented missing feature (pinned disclaimer thread and everything) and immediately head to forums to report it. To these people my answer is usually something like "here is the answer I gave to this same question that is still on the front page of this forum:" followed by a quote that reads something like "here is a quote from the pinned thread for all bugs for this source:". (When your google-fu is so weak you can't even find the answers you had to pass on the way to asking someone else to find the answer for you...)
Simple request after fighting to re-subscribed: As a customer, I want better error messages at subscription time.
In a nutshell, I kept getting 'ERROR:Gateway Rejected: avs-gateway_rejected' when trying to sign up. Tried two cards, then decided to google-fu before giving up. A web hosting company (Directnic) had information on errors their customers might receive when accepting payments online. Their article explained that this error is typically associated with the billing address being incorrect. I reviewed the information again, found a typo that was saved in Chrome (saved addresses) which was supplying an incorrect zip code.
At this point, I *AM* a subscriber again, but no customer should ever have to dig up payment processing errors codes to figure out how to resolve this.
I agree. Layman error messages would probably help everyone (of course some errors appear for multiple reasons).
Kudos for having an uncommon problem and solving it yourself. Far too often people will come across a common error caused by user error or a well documented missing feature (pinned disclaimer thread and everything) and immediately head to forums to report it. To these people my answer is usually something like "here is the answer I gave to this same question that is still on the front page of this forum:" followed by a quote that reads something like "here is a quote from the pinned thread for all bugs for this source:". (When your google-fu is so weak you can't even find the answers you had to pass on the way to asking someone else to find the answer for you...)