Customer Name Validation for Loyalty Point Allocation

Requirement

An airline brand needs a validation mechanism to ensure that the first name and last name provided during a flight booking match the customer profile stored on Capillary’s platform. This validation is essential to ensure that loyalty points are allocated to the correct customer.

If the provided names do not match either the primary names or any of the stored alternate names (aliases) in the customer profile, the system will not allocate loyalty points.

Currently, Capillary’s platform does not offer built-in validation to compare the airline’s booking data with the stored customer records.

Solution

To solve this, create a Neo dataflow that compares the passenger names from the airline record with those stored in the Capillary system.

Step One: Use Schema block to Validate Input Parameters

Perform schema validation to ensure that all mandatory parameters are present. If any parameter is missing, return an appropriate error response. The required input parameters are:

• FFN (Frequent Flyer Number)
• First Name (Fname)
• Last Name (lname)

Handle validation failures with the appropriate error messages.

Step Two: Use the Script Block to Create Payload for the GET Customer API

Use the Script block to construct valid headers and query parameters, transform data to create a request payload for the GET Customer API call by following these steps:

• Fetch the input query parameters.
• Remove unnecessary or error-prone headers.
• Build the query using the required values: externalId (FFN) and source.

Step Three: Use API Request Block to Invoke GET Customer API with the Appropriate Query Parameters

Use the API Request block to invoke the https://{host}/v2/customers/lookup/customerDetails.

Step Four: Use the Script Block to Compare Names

Use the Script block to verify whether the combination of First Name and Last Name from the airline's booking data matches any of the following:

• Primary name in the customer profile
• Any of the alternate names (alias1, alias2, alias3)

If there’s a match, return a success response. If not, return a failure response.