This feature allows Administrators to associate credit card number entries with Unanet users. Note that this is not a credit card transaction import, but rather a mean for an Administrator to load user credit card number information in mass.
This screen is available to users having any of the following roles: Administrator and P&R Administrator
This feature is available with any Unanet edition.
Topics covered on this help page include:
Import File Record Layout (field by field descriptions)
Import File Format (generic rules and Excel spreadsheet tips)
Excel Template (spreadsheet template containing column headings)
Import Screen (invoking the import via the user interface)
IMPORTANT: Note that there are multiple places within this documentation that say you MUST use double quotes for the strings in your import. If you are working in Excel, Excel will provide the double quotes and thus you do not need to add them in manually. Manually adding double quotes within Excel would result in multiple sets of double quotes in the resulting .csv file and thus cause an error (should you attempt to import that resulting file). Please see Excel Tips for more information.
|
|
Field Header Name |
Required/Comments |
1 |
A |
Username |
ALWAYS REQUIRED. Unique username (user id), for example JDoe or jdoe (it does not need to be capitalized.) This value must match an existing Username value in your system. If the Username you are trying to import is not an existing valid value, the entire record will be rejected. |
2 |
B |
Issued_By |
REQUIRED on Add. This field will contain the name of the lending institution that issued the credit card. This field is not displayed on other Unanet screens. Maximum Length: 64 characters |
3 |
C |
Name_On_Card |
REQUIRED on Add. This field is intended to contain the name as it appears on the credit card. Maximum Length: 128 characters |
4 |
D |
Card_Number |
ALWAYS REQUIRED. This field is used to contain a value that will uniquely identify a users credit card account. The value supplied in this field (may it be an actual credit card number or other user identifying number) will be stored in Unanet as a hashed value for security purposes. This value is used in conjunction with the various credit card import facilities. Imported credit card transactions will be associated with users by matching a similarly hashed value on the imported transaction files with the values stored in each users person profile. On various screens, only the last 4 digits of this number are displayed. Note that having existing credit card transactions in the system that relate to a specific credit card number does not prevent the disassociation of that card number from a user. Minimum Length: 5 Maximum Length: 32 characters |
5 |
E |
Expiration_Date |
REQUIRED on Add. This field is intended to contain the expiration date as printed on the credit card. The value supplied must be in mm/yy format (2 position month / 2 position year). Maximum Length: 5 characters |
6 |
F |
Card_Type |
REQUIRED on Add. The intention of this field is for the user to enter a value identifying the type of credit card (e.g. MasterCard, Visa, Amex, etc). This value is displayed on various imported credit card detail screens in conjunction with the last for digits of the users credit card number in what is called a "Source" field (e.g. Mastercard ********1234). There is no predetermined valid value set for this field. Maximum Length: 32 characters |
7 |
G |
Delete |
This field can be used to trigger the system to delete a person credit card entry. In order for the delete to happen, you must include the following text string !DELETE! in this field. Note that having existing credit card transactions in the system that relate to a specific credit card number does not prevent the disassociation of that card number from a user. |
Note: Check out the Unanet Data model for specific field data types, lengths, and other attributes.
The file to import must be saved in a comma delimited format. The fields can be enclosed in double quotes -- which would be particularly necessary should the data being imported contain commas.
If you are not using the default column layout sequence as defined above, you must include a header record (prefixed with an asterisk *), containing the column Header Names for those columns you are including in the import file (to indicated what data is contained in each column). The specific Header Names for each column are listed in the table above.
Example:
#Delete example
*Username,Card_Number,Delete
JIM,12345,!DELETE!
You can create the comma delimited import file with any number of tools. For those interested in using an Excel spreadsheet to create the file, you can download an Excel Template with predefined headers and required fields noted.
See the Excel Tips regarding the use of double quotes and more.
The Import Person Credit Card Number screen looks like:
Field |
Description |
Type of Import |
Select the appropriate import type from the list of available types of imports. |
File to Import |
Enter (or browse for) the file that you would like to import. |
Output Options |
Specify the level of detail included in the output. |
The import process is triggered by pressing the Import button. All Warnings and Error messages are written to the screen and can then be saved if desired. While some line items may be found invalid and rejected, the remaining line items will be successfully imported and saved in the database. The rejected line items will be written out to a file on the Unanet server as well as displayed at the bottom of the user feedback screen. The rejected record file name will be UnanetPersonCreditCardNumberImportErrorxxx, where xxx is a randomly generated number. The file will be placed in the Unanet temporary directory (which is defined by the Temp Directory (Fully Qualified Directory Name) (unanet.temp_directory) Unanet property).