Original publication date: November 24, 2020
Question:
After we submit a rail, we receive 3 webhook replies:
- Event: RailUpdated with a funding status
- Event: FundingAttemptComplete
- Event: LoanStatusUpdated (104 NotFullyFunded if more rails are expected)
As soon as we receive the webhook event, RailUpdated, we submit each subsequent rail, one at a time, with the endpoint /FundingInfo.
However, sometimes when we request the /FundingInfo update, the rail doesn't show in Arix. This causes the loan to be stuck in our system. We then have to make a manual adjustment to resend the rail instead of everything being automated.
How can we avoid this situation so that no loans get stuck?
Answer:
The webhook event, RailUpdated is always reported before the events, FundingAttemptComplete and LoanStatusUpdated.
To make sure that no rails are missed, wait until the event, fundingAttemptComplete is reported, and then send the next rail after about a second.