Identification Service

Identification Service

Overview

Rental Car Manage (RCM) allows for integration into a Identification Service. An Identification Service is normally something provided by a third-party company where they will validate the customer information and return a status of either valid or invalid. If you would like more information about this, please contact RCM Support (support@rentalcarmanager.com)

Identification Process Steps

There are two steps to the Identification Service integration with RCM, they are discussed in more detail below:
  1. Receiving a notification from RCM when an identification check is required.
  2. Sending the Identification Verification information through to RCM

Receiving a notification from RCM when driver identification is required

RCM can send a notification with the reservation details via a http request when a booking is created.  This request can be used to trigger the identification process.
The following information will need to be included in the request (json format required):
  1.     "bookingInfo": [
            {
                "reservationReference": "reservation reference - used within RCM to identify the booking <string>",
                "pickupDate": "date of pickup (pickup location-timezone)<date dd/MMM/yyyy>",
                "pickupTime": "time of pickup (pickup location-timezone)<24hour time HH:mm>",
                "pickupLocationName": "pickup location name <string>",
                "dropoffDate": "date of drop-off (dropoff location-timezone)<date dd/MMM/yyyy>",
                "dropoffTime": "time of drop-off (dropoff location-timezone)<24hour time HH:mm>",
                "dropoffLocationName": "drop-off location name<string>"
            }
        ],
        "customerInfo": [
            {
                "customerId": "id of customer<int_id>",
                "firstName": "first name<string>",
                "lastName": "last name<string>",
                "dateOfBirth": "date of birth<date dd/MMM/yyyy>",
                "licenseNo": "drivers license number<string>",
                "licenseIssued": "drivers license issued from<string>",
                "licenseExpires": "drivers license expires date/string <date dd/MMM/yyyy> or <string 'lifetime'>",
                "email": "email<string>",
                "phone": "phone number<string>",
                "mobile": "mobile number<string>",
                "address": "<string>",
                "city": "<string>",
                "state": "<string>",
                "postcode": "<string>",
                "country": "<string>",
                "passport": "<string>"
            }
        ],
        "additionalDrivers": [
            {
                "customerId": "customer id of extra driver<int_id>",
                "firstName": "first name <string>",
                "lastName": "last name<string>",
                "dateOfBirth": "date of birth<date dd/MMM/yyyy>",
                "email": "<string>",
                "phone": "<string>",
                "mobile": "<string>",
                "address": "<string>",
                "city": "<string>",
                "state": "<string>",
                "postcode": "<string>",
                "country": "country name<string>",
                "licenseNo": "license number<string>",
                "licenseExpires": "license expires date/string <date dd/MMM/yyyy> or <string 'lifetime'>",
                "licenseIssued": "license issued by<string>"
            }
        ]
    }

Sending identification verification information to RCM

When the identification process has been successfully completed, the Identification Service can send a http POST with the following content in json format:
Endpoint:
  1. [
        {
            "reservationReference": "reservation reference as provided by RCM",
            "identityReference": "unique identifier for this identity verification",
            "documentUrl": "url to documents for the identity verification",
            "customerId": "customer Id as provided by RCM"
        },
        {
            "reservationReference": "reservation reference as provided by RCM",
            "identityReference": "unique identifier for this identity verification",
            "documentUrl": "url to documents for the identity verification",
            "customerId": "customer Id for additional driver as provided by RCM (if applicable)"
        }
    ]