Credit Card Name

david.ells's Avatar

david.ells

12 Oct, 2009 08:35 PM

Although the API calls for first and last names for credit card information when creating/updating a subscription, they are not returned with the other CC fields when retrieving customer data. There may be times when we want to have a different account name and CC holder name, but currently we can't retrieve the CC first/last name to display.

Also, is the first/last name fields attached to the CC information used for verification in any way, or is verification only done using the billing zip?

  1. 1 Posted by david.ells on 12 Oct, 2009 08:46 PM

    david.ells's Avatar

    Is there any reason why CG has not decided to accept CVV codes in addition to (or instead of) the billing zip for credit card verification? It's a little unfortunate to between accepting non US cards OR having credit card verification. (since billing zip, a US only feature, is the only verification mechanism available)

  2. Support Staff 2 Posted by Marc Guyer on 12 Oct, 2009 09:06 PM

    Marc Guyer's Avatar

    ccFirstName and ccLastName are currently only stored at the gateway. We do intend to have CG store this information for exactly the purpose you suggest. CG displays the information in the GUI now but not via the API.

    Again, yes, we do intend to begin supporting CCV. For now, only billing zip is available for verification. We decided initially to not use this form of verification because the CCV values cannot be stored (and so cannot be reused). However, when using the Authorize.Net CIM, you can use it for the initial verification and benefit from that for subsequent transactions. The groundwork has been laid for supporting CCV in our error handling system. Once everything else is complete, we'll begin accepting the CCV value.

  3. Marc Guyer closed this discussion on 12 Oct, 2009 09:06 PM.

  4. david.ells re-opened this discussion on 23 Nov, 2009 03:16 PM

  5. 3 Posted by david.ells on 23 Nov, 2009 03:16 PM

    david.ells's Avatar

    I noticed that CG now supports CVV codes. We'd like to switch from using billing zip to CVV codes for verification, and I was curious to know what would happen to any existing customers who didn't originally provide a CVV and want to upgrade their account. Will they need to provide the CVV code on upgrade?

  6. Support Staff 4 Posted by Marc Guyer on 23 Nov, 2009 05:37 PM

    Marc Guyer's Avatar

    The CVV is only used for the initial card verification. If a customer already exists, the CVV is not needed again unless the customer would like to update their credit card. It sounds like a seamless change to me.

    Also note the new preferences for requiring zip and/or cvv here

  7. 5 Posted by david.ells on 01 Dec, 2009 10:38 PM

    david.ells's Avatar

    We are getting 2001 "The configuration at the gateway is incompatible" errors when trying to use CVV's in our production account. Is there any recommendation on how to configure our Authorize.net account for CVV's (I couldn't find anything about it here (http://support.cheddargetter.com/faqs/getting-started-19/configurin...)). Should we only be using some of the options under Card Code Verification (CCV) Settings? Which ones?

  8. Support Staff 6 Posted by Marc Guyer on 02 Dec, 2009 12:05 AM

    Marc Guyer's Avatar

    The error report here has more detail. It looks like you've got the phone number required. I don't know off the top of my head how to change that on the authnet side. Let us know if you can't find it.

  9. 7 Posted by david.ells on 02 Dec, 2009 01:12 AM

    david.ells's Avatar

    Marc, thanks a bunch for the help, as soon as I knew the underlying error I was able to go hunt down the settings I needed to change. It turns out that a number of fields within Authorize.net (under Account -> Settings -> Payment Form -> Form Fields) were checked under the "required" column. Unchecking those fields solved the problem. What's odd is that we never experienced that error during our initial launch (and final production testing), although those settings in Authorize.net surely must have been the same then.

    Once what was going on was clear, it was pretty easy to fix. But it really wasn't very clear to start with. May I suggest that a) the Configuring Authorize.net document includes a section about those Payment Form fields (which may only recently be necessary to unset?), and that it also includes at least some word about CVV settings (although checking everything seems to work fine there) and b) documenting in a new or existing KB article about the CG error report found under Reports->errors. I know there's a link to it there in the GUI, but it's small, and under what I thought was only customer and revenue reports. It's really useful but there's no mention of it anywhere, in any discussions or articles.

  10. Support Staff 8 Posted by Marc Guyer on 07 Dec, 2009 04:02 PM

    Marc Guyer's Avatar

    David -- Thanks for the suggestion and the troubleshooting. I've updated the Configuring AuthorizeNet article.

    Strange that you were not experiencing this issue in production testing. Were you in test mode or using a developer account at the time? Could someone else in your org have altered the settings after launch? As shown in the KB article, in our experience the default settings do not require any fields.

    I've also added some info about the error report on the Error Handling article.

  11. 9 Posted by david.ells on 07 Dec, 2009 04:11 PM

    david.ells's Avatar

    Marc, thanks a bunch for following up and updating the KB articles, it adds another vote of confidence that you all are accessible and receptive.

    Embarassingly, it did turn out that someone had updated those fields, trying to use our same Authorize.net account for a generic hosted payment form.

    I'm sure future users will find the additional information about the errors report and those settings useful if they find themselves in a sudden bind. Thanks again.

  12. Support Staff 10 Posted by Marc Guyer on 07 Dec, 2009 04:31 PM

    Marc Guyer's Avatar

    No prob. I'm sure the extra info will be found useful.

  13. Marc Guyer closed this discussion on 07 Dec, 2009 04:31 PM.

Discussions are closed to public comments.
If you need help with Cheddar please start a new discussion.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac

Recent Discussions

28 Mar, 2024 10:45 PM
24 Jan, 2024 08:33 AM
11 Jan, 2024 07:13 AM
30 Nov, 2023 02:07 AM
22 Nov, 2023 08:41 AM