This is a documentation for the CustomerIdentity API, a service within the Customer Insight Solution set of the GIDX Platform.
This set of documents serves as the integration guide for implementing services of the GIDX Platform API within the operator’s environment. The following pages outline the Customer Insight access points, security, methods, and parameters. As always, please contact us at devteam@tsevo.com any time if further explanation is needed.
An official SDK for the GIDX Platform API is available at GitHub.com and via NuGet (GIDX.SDK) located at the URL below. This SDK can be installed directly into your C# project using the NuGet Package Manager.
SDK LocationBelow are descriptions of the methods exposed by the GIDX Platform CustomerIdentity Service. For details about the parameters associated with these methods please see the Class Reference section below.
The following parameters are used in every CustomerIdentity Method Request and Responses. They are labeled within the methods below as Standardized Request Parameters and Standardized Response Parameters.
Making a Request
Each API method has a corresponding Request object used to transport the request parameters as shown below.
Using the Response
Each Response object returned from the method Request will contain properties you can use to determine the status of the methods service.
Use the IsSuccess property along with the ResponseCode and ResponseMessage values to detect if the Request completed without a problem.
4QhgWWJxRlqVctrc7SxHEQ
VpGYLoXhSS+WgU9N415IJQ
Fc+k5kRDSAOrh38e21vt0w
m+2XHlcIR0O1C+iBeNzfvA
VV4XTc3tRi6g1EYLOazn0g
xHhSS+WglqVctrc7-t7SEQrc
66.249.76.138
4QhgWWJxRlqVctrc7SxHEQ
VpGYLoXhSS+WgU9N415IJQ
xHhSS+WglqVctrc7-t7SEQrc
ABC-123_xyz
0
No Errors
This method should be called to register the customer within the GIDX system and find verify a match to their identity.
ABC-123
(Dr., Mr., Mrs., etc.)
John
Michael
Doe
(Sr., Jr., etc.)
Dr. John Michael Doe Jr.
04/03/1984 (In MM/DD/YYYY Format)
johndoe@msn.com
US
1
444-12-1234
(999) 834-5813
(999) 834-5814
5940 Main St.
Suite A
Las Vegas
NV
77587
US
US
ABC-123
['US-OFAC','US-FBI-HS']
['ID-VERIFIED', 'ID-EX', 'DFP-HR']
[See Object Details]
[See Object Details]
http://www.CustomUrl.com/UniqueID
98.5
98.5
This method may be called to get the profile information associated with a verified MerchantCustomerID within the GIDX system.
ABC-123
ABC-123
98.5
85.3
This method may be called to get the current compliance status of the customer profile associated with a verified MerchantCustomerID within the GIDX system.
ABC-123
["NFL-HOU", "NFL-ATL"]
ABC-123
See Object Definition
['ID-VERIFIED','ID-EX','LL-GEO-US-NV']
[See Object Details]
98.5
85.3
This method may be called to update a customer's information without going through any verification. ID-VERIFIED and ID-BLOCK can also be added using this method.
ABC-123
true, false, null
true, false, null
(Dr., Mr., Mrs., etc.)
John
Michael
Doe
(Sr., Jr., etc.)
Dr. John Michael Doe Jr.
04/03/1984 (In MM/DD/YYYY Format)
johndoe@msn.com
US
1
444-12-1234
(999) 834-5813
(999) 834-5814
5940 Main St.
Suite A
Las Vegas
NV
77587
US
ABC-123
This method may be called to remove a customer from your merchant account.
ABC-123
ABC-123
Receiving a Profile Notification from the GIDX Platform requires a pre-defined notification URL on a trusted merchant server.
When a customer's profile information is updated by the GIDX Platform a JSON post is sent to this notification URL containing the information shown below.
This URL must be able to accept the request (a) from the GIDX environment and provide a response in the format indicated in example (b) below. The format of the Notification Service request uses the same structure as the Callback service found in the WebReg Customer Identity service and the Web Cashier service.
ABC-123
CustomerProfile
When the merchant's service receives the Notification request the expected response from the merchant should be as follows...
true
If the response is not provided back to the GIDX service the Notification attempt will be placed back in the queue and will be retried in regular intervals up to 5 times or until an accepted response is provided back successfully.
Upon receiving this notification it is expected that the merchant will log the notification and make a call the CustomerProfile method in order to retrieve any updated/added data that has been applied to the Customers profile.
Location look-up is based on the IP address / Device GPS and the Merchant Settings. Although a MerchantCustomerID is not required it is suggested that any method calls for location associated with a registered customer should have a MerchantCustomerID provided for tracking and compliance audit purposes. The response contains the location details based on the Merchants settings.
ABC-123
[See Object Details]
The Object documented below are returned within the Response of Method Request within the GIDX Platform CustomerIdentity Services. When applicable an Object may be shared by among other Method Responses as indicated in the listings below.
Objects are always returned in JSON format.
This object contains the Address data associated with the customer's profile.
Residence
5940 Main St.
Suite A
Las Vegas
NV
Clark
89141-1097
US
Downtown
98.5
TRUE
This object contains the full name associated with the customer's profile.
Washington, US
(MM/DD/YYYY)
98.5
TRUE
This object contains the Citizenship data associated with the customer's profile.
(713) 834-5813
30746
98.5
TRUE
This object contains the Device data associated with the customer's profile.
D05OCnpoQ6OqlsE4gdjQug
Windows 7
98.5
TRUE
This object contains the education associated with the customer's profile.
2010-08-01
2014-05-01
University of Texas
Bachelor's Degree
98.5
This object contains the Email data associated with the customer's profile.
johndoe@msn.com
98.5
TRUE
This object contains the Identity Document data associated with the customer's profile.
1
*** ** 1234
San Diego, CA
07/33/1985
John M Doe
98.5
TRUE
This object contains the work history associated with the customer's profile.
2010-08-01
2014-05-01
TSEVO, LLC
Software Developer
Technology
98.5
This object contains the full name associated with the customer's profile.
(Dr., Mr., Mrs., etc.)
John
Doe
Michael
(Sr., Jr., etc.)
98.5
TRUE
This object contains the Phone data associated with the customer's profile.
(713) 834-5813
1
AT&T
Wireless
98.5
TRUE
This object contains the data match status of the customer profile information passed into the CustomerRegistration Request.
TRUE
TRUE
FALSE
TRUE
TRUE
FALSE
TRUE
TRUE
This object contains the social media account associated with the customer's profile.
100002122533075
facebook, linkedin, twitter
98.5
This object contains the matching Watch List data of the customer profile.
US-OFAC
98.5
TRUE
98.5
This object contains the data match status of the customer profile information passed into the CustomerRegistration Request.
36.169727
-115.141801
600
22.9871
45
10/01/2013 12:42:15 GMT
2
Standard
['LL-BLOCK-US-NV','LL-GEO-US-NV']
TRUE
Inactive
This object should contain the location data derived from the Devices GPS information.
For more information on collecting this data from the Device please click here to see the table below for both iOS and Android.
Device GPS Property | Class | Property | Declaration |
---|---|---|---|
Latitude & Longitude | CLLocation | coordinate | CLLocationCoordinate2D |
latitude | CLLLocationDegrees | ||
longitude | CLLLocationDegrees | ||
Radius | CLLocation | horizontalAccuracy | CLLocationAccuracy |
Altitude | CLLocation | altitude | CLLocationDistance |
Speed | CLLocation | speed | CLLocationSpeed |
DateTime | CLLocation | timestamp | NSDate |
Device GPS Property | Class | Property |
---|---|---|
Latitude | Location | getLatitude() |
Longitude | Location | getLongitude() |
Radius | Location | getAccuracy() |
Altitude | Location | getAltitude() |
Speed | Location | getSpeed() |
DateTime | Location | getTime() |
The DateTime in Android is a "ticks" and needs to be converted to the dateTime format MM/DD/YYYY HH:MM:SS.000 |
36.169727
-115.141801
600.999
22.9871
45.999
10/01/2013 12:42:15 GMT
The information documented below provides clarification of the codes used within the GIDX Platform CustomerIdentity Services.
ISO 3166-1 is part of the ISO 3166 standard published by the International Organization for Standardization (ISO), and defines codes for the names of countries, dependent territories, and special areas of geographical interest.
http://en.wikipedia.org/wiki/ISO_3166-1
ISO 3166-2:US is the entry for the United States in ISO 3166-2, part of the ISO 3166 standard published by the International Organization for Standardization (ISO), which defines codes for the names of the principal subdivisions (e.g., provinces or states) of all countries coded in ISO 3166-1.
http://en.wikipedia.org/wiki/ISO_3166-2:US
For the latest list of Reason Codes and their description please go to the following URL.
View Reason Codes