authorize.net, field, fields, first name, last name, empty
First and Last Name fields for customers are empty in Authorize.net. Why?
You could find the First and Last name fields populated under the Account details for a customer in
38989385
2020-12-22T08:33:32Z
2021-01-04T12:01:36Z
649
0
0
249217
First name and last name fields for customers are empty in Authorize.net. Why?
First name and last name fields for customers are empty in Authorize.net. Why?
This article covers
Transactions from Chargebee have no first/last name and Authorize.net is starting to flag those as suspicious.
I can find the first name and last name in Chargebee. Why is this not being sent to my gateway?
Summary
You could find the first and last name fields populated under the 'Account details' of a customer in Chargebee but the same would appear 'empty' in your merchant account. However, Chargebee does send this data to your gateway account, provided it is captured as part of the Card details. If you are using Chargebee's checkout pages, then ensure to enable and/or make the fields mandatory in the Payments section.
Go to Settings > Configure Chargebee > Checkout & Self-serve Portal settings > Fields
Ensure to hit Publish once you make the changes.
You can verify if the data is captured from the customer by selecting “Show More” on their card information in Chargebee:
Data present under 'Payment Methods' are only sent to the gateway account on transactions.
Note: If you're using our API to create customer information in Chargebee, ensure to use the card[first_name] [last_name] parameters
Billing/error-e00027-payment-collection-failedpayment-has-been-declined-whats-going-on.txt
Billing/error-e00007-user-authentication-failed-due-to-invalid-authentication-values-whats-going-on.txt
Billing/error-card-declined-by-issuer-whats-going-on.txt
Billing/authorizenet-error-user-authentication-failed-due-to-invalid-authentication-values.txt
Billing/error-street-address-and-postal-code-do-not-match-whats-going-on.txt
Billing/error-charge-failed-e00027-bill-to-zippostal-code-is-required-whats-going-on.txt
Billing/can-i-configure-when-payment-batches-are-submitted-for-settlement-if-yes-how-can-i-do-it.txt
Billing/my-customers-have-received-payment-notification-emails-but-i-have-not-enabled-email-settings-on-chargebee-whats-going-on.txt
Billing/how-long-will-a-payment-done-via-ach-direct-debit-take-to-reach-my-account.txt
Billing/error-you-do-not-have-permissions-to-call-the-transaction-details-apitransaction-details-not-enabled-whats-going-on.txt
Billing/error-the-market-type-is-invalidtransaction-of-this-market-type-cannot-be-processed-on-this-system-whats-going-on.txt
Billing/how-to-start-the-migration-of-direct-integration-with-authorizenet.txt
Billing/is-there-a-downtime-scheduled-during-the-migration-of-authorizenet-from-spreedly.txt
Billing/what-if-i-have-issues-with-the-migrated-cards-data-from-spreedly-to-authorizenet.txt
Billing/why-do-i-still-need-to-enable-transaction-details-api.txt
Billing/will-authorizenet-direct-be-used-as-the-default-gateway.txt
Billing/what-should-i-do-upon-receiving-the-chargebee-authorizenet-account-is-not-active-email.txt
Billing/can-i-continue-to-use-the-authorizenet-integration-spreedly.txt
Billing/how-long-will-the-migration-of-cards-from-spreedly-to-authorizenet-take.txt
Billing/what-are-benefits-of-migrating-to-authorizenet-direct-integration-for-my-business.txt
Articles & FAQ