1. User determines the Enrollment type as that is the required field in CheckServiceAvailaibility
2. We have selected the Lifeline Order which is tied to ENROLLMENTTPE "LIFELINE"
3. After user has selected the ENROLLMENTTYPE you store the selection.

User enters the Zip Code since that is a required field in CheckServiceAvailability API and is necessary to check for the service availability in the area

Once user knows the ENROLLMENTTYPE and Zip Code they can call CheckServiceAvailability API with the proper values passed in the API parameters.

Once you know that the services are available next you would want to know the eligibility programs and plans available on that Zip Code for that you call getProgramIncomeList and GetPlanService plan list at the same time to get the list of the plans and eligibility programs.

Based on the results from getProgramIncomeList and GetPlanService you select the eligibility program which customer is getting and also make the plan selection which customer wants.

When you select the eligibility type you can also ask to enter the proof of eligibility number. To check the duplicate on the basis of the eligibility number you can call CheckEligibilityNumbers API.

In this step you capture applicant’s personal information. You would want to do the duplicate check for that you call:

1. DuplicateCheck- If your order fails duplicate check system will not allow you to proceed. After the duplicate check is successful you would to NLAD check and verify and to do that you call below mentioned APIs
2. NladEtcVerify- If this API fails it will return the error from NLAD.
3. NladVerify- If this API fails it will return the error from NLAD.

You can decide how would you want to handle the NLAD errors for example if you want to allow TPIV orders to proceed or not and same goes for other NLAD errors.

If you get it as Portfrezee then you pass ISBENEFITTRANS as Y in Createcustomer XML API and also the responses to the benefit transfer statements in CERTIFYBENI1 and CERTIFYBENI2

In this step you define the enrollment type.

• • Handover: if enrollment type is handover then status should be approved and you need to pass the ESN/MDN/IMEI
• • Shipment: if enrollment type is shipment then status should be either pending/approved or you don’t need to pass ESN/MDN/IMEI. Those will be attached to the account via dropship process

Those will be attached to the account via dropship process

You pass the enrollment type in createcustomer API in :

As a next step user should be validating the ESN/SIM and if it is provisioned or not provisioned and to check if it is assigned to the user who is doing the enrollment or not to do so it shall call Devicelookup XML API which will return the status of the ESN/SIM and also the MDN if the status is provisoned.

After the ESN/SIM is validated if GSM device is also been assigned to the customer then user shall also validate the availaibility and the status of the IMEI which will be done using IMEIlook up APi

As soon as you hit continue you need to call createcustomer API and pass all the information which is needed in the API, all the info has already been collected in the previous steps, as soon as createcustomer API returns the success response order gets created successfully in Vcare and at the same time we call the enroll/transfer API in NLAD according to the response mentioned in create customer API in the parameter Y (NLAD enroll/transfer call can also be made at a later stage when customer dials 611)

If there is any payment included then next step is for taking the payment if there was any payment included for paid plans or paid equipments. For taking the payment you call Payment XML API and pass the below mentioned parameters in Payment XML API