Customer Lookup

QFD can integrate either via REST or SOAP using real time API calls to the system of record in order to search for and load customer information.

Please note: We do NOT support any custom additions to the below list, and the customer search options we can implement is dependent on the allowed values that your API supports.

By default, QFD supports searching for customers using the following API request options:

	Possible Request Option	Notes

	Possible Request Option	Notes
1	First Name	First name of the desired customer.
2	Last Name	Last name of the desired customer.
3	Address Line 1	Street address of the desired customer.
4	City	Address city of the desired customer.
5	State	Address state of the desired customer.
6	Zip Code	Address zip code of the desired customer.
7	Account Number	The unique account identifier that can be used to look up a specific customer.
8	Social Security Number or Tax ID Number	QFD is usually configured to not store this value, and prefers to not leverage this option unless absolutely required to do so.
9	Customer ID	Unique identifier that can be used to look up a specific customer.
10	Card Number	This can either be the full card PAN or the Card ID/Token depending on the configuration of the API.

In order for QFD to display search results, and to retain other needed customer information, we will need as many of the following data points as possible to be made available from the API response:

	Needed Response Field	Required?

	Needed Response Field	Required?
1	Client ID	Yes - for processors who support multiple clients
2	Customer ID	Yes - A unique identifier that will be used to easily locate a specific customer every time.
3	First Name	Yes - for individual customers
4	Middle Name	No
5	Last Name	Yes - for individual customers
6	Name Prefix (Mr., Mrs., Dr., etc)	No
7	Name Suffix (Sr., Jr., etc.)	No
8	Business Name	Yes - for business customers
9	Address Line 1	Yes
10	Address Line 2	No
11	Address Line 3	No
12	Address City	Yes
13	Address State	Yes
14	Address Zip Code	Yes
15	Address Country	Yes
16	Email Address	Yes - If the ability to send email correspondence is desired for the project. In a non production environment, these email addresses should be sanitized, but should still be formatted like legitimate email addresses, and they should be unique for each customer record.
17	Opt In For Electronic Communication	No - However, if the ability to send email correspondence is desired for the project, and the customer has to opt in to receive emails, then this will be required.
18	Phone Number	No
19	Phone Type (Landline, Mobile, etc.)	No
20	Language Preference	No - send if you’d like user language/letter language to be based on Preference
21	Preferred Communication Method	No - send if you’d like correspondence method to be based on Preference
22	Social Security Number or Tax ID Number	No - Quavo’s preference is NOT to receive this field unless unavoidable.