How to submit payments for impound vehicles

Fundamentally submitting a payment for an impound vehicle consists of 3 steps:

1. Finding the correct vehicle

2. finding its fees/total to the user and eligibility for release

3. Creating the receipt & payment

Finding the correct vehicle is done by calling the /impound/lookup endpoint with a payload containing either

1. Partial or full VIN

2. License plate number & License state

3. Date + vehicle details

You’ll also need to send along your region code, and the statuses you’re interested in. In this case the status you’re interested in is “STORED”. Here is an example looking for vehicle in the test region of IMP-TS, in the stored status, with a particular license and license state

Here is an example of looking up by VIN

Looking up by vehicle details is more complicated, since you need our list of makes, models and colors.

You can get these lists by calling /api-web/api/refdata/{regionCode}/colors
/api-web/api/refdata/{regionCode}/makes

and once you have the make, you can request all models for that make using

/api-web/api/refdata/{regionCode}/models/by-make/{makeCode}

Once the user has selected a value for these they should select a date, then you can send those to us, for example.

Note that the limit is very important here, as you could end up returning many vehicles if you allow the user to select something very broad, like all toyotas towed in January.

Once you have the correct vehicle you can then retrieve its fees and total unpaid amount by its vehicleId.

VehicleId is the unique id for each time a vehicle gets towed. If it gets towed twice, it will get 2 vehicleIds. You then make a request to the /impound endpoint which will get you the complete vehicle details including the fees as of the time of the request.

for example will give a response containing most of the details of the vehicle. In particular you’ll want to look at

• currentLocation which represents the best way to get into contact with whoever has current possession of the vehicle

• make.name , model.name , color.name , license , licenseState.code

• unpaidFeeItems which contains all of the fee items that are not paid yet.

• totalUnpaid which contains the total unpaid amount for this vehicle

• eligibleForOnlinePayment indicates if the vehicle is currently releasable. Holds may prevent release of the vehicle, in which case you probably don’t want to let people pay for it. The vehicle may also enter other states that would make online payments not apply correctly.

Here is an example of the response

Once the user has indicated that they want to pay you must collect contact information from the user, this is used to ensure that the vehicle is released to the correct person later in the process.

You then call the /createReceiptAndPayment endpoint with the vehicleId, contact details and amount paid.

Note how in the response the vehicle’s status has changed to RELEASE_PENDING. This happens when a vehicle in a releasable state has been fully paid for. Also note the value in vehicle.releaseAuthorizedThrough, this is the latest time that the vehicle owner can show up to the yard to retrieve the vehicle before additional fees might be applied.