e commerce - Complex Names with Authorize.net AIM -


how rest of handle complex names when submitting transaction authorize.net using aim?

nearly every ecommerce application on planet asks user fill in "name appears on credit card". odd reason, authorize.net wants submit x_first_name , x_last_name however.

this fine when you're dealing mary jones or jack smith. becomes real hassle when you've got margret a. jones-robinson , h. william robert van horn, sr. though.

is there best practice here?

first & middle names in x_first_name field?

last name, hyphenated name and/or suffix in x_last_name field?

has developed routine parse names accordingly?

thanks!

have 2 fields on payment form. 1 first name , 1 last name. customer chooses complete form how should submit (and save in database if choose so). fyi, name on credit card not used in processing of credit card not have transmit authorize.net process transaction. should anyway helps keep records accurate , complete handy when doing audits of transaction history.

you should try avoid using 1 field names opens possibility people enter bad information like, "the smith family" or "barabara , steve". having 2 delimited fields reduce occurrence of this.


Comments

Popular posts from this blog

java - SNMP4J General Variable Binding Error -

windows - Python Service Installation - "Could not find PythonClass entry" -

Determine if a XmlNode is empty or null in C#? -