Boarding Timeouts

When encountering a boarding timeout, please observe the following steps to ensure that your application is correctly resubmitted.

Avoiding Duplicate Applications

  1. Ensure the uniqueId for the initial boarding attempt is guaranteed to be original and never repeated for subsequent applications. Using the partner's name followed by a millisecond timestamp is a good way to create a uniqueId.

    Example. AcmeCorp1572566399123
  2. For each boarding request, wait 180 seconds for the MID response to be returned. If 180 seconds elapses without a response, send the boarding request again AND modify the uniqueId. It is recommended to incrementally change the uniqueId for each boarding attempt. For example, the second attempt would add "-1" at the end of the uniqueId.

    Example. AcmeCorp1572566399123-1

Retry Logic

The most common reasons for a delay in returning a MID is when new eBoarding software is being deployed or there is some temporary system malfunction. If no MID is returned when expected, then retry submitting the application based on this timetable:

  1. First retry after 180 seconds.
  2. Then retry every 15 minutes for 4 hours.
  3. Then retry every 60 minutes for 72 hours.

If there is still no MID returned, then you may need to reference error logs or consult your Elavon relationship manager.

 

❮ Back to Request a Boarding Application Status   Next:  Error Messages ❯