---
title: "Handling Timeouts"
source_url: https://docs.rapyd.net/en/handling-timeouts.html
lang: en
---

# Handling Timeouts

### Terminal is down

The client successfully sends a sale request to CloudLink but the terminal is down. A callback is therefor never delivered to the client.

![image7.png](image/img-d28811d6b84c597ad7b046031d0ab5db.png)

### Callback is down or invalid

The client successfully sends a sale request to CloudLink which delivers the request to the terminal. The terminal then tries to send a SALE_RECEIVED event but can not contact the callback.

![image9.png](image/img-2d998f06d8741398b23a73025317c988.png)

### CloudLink API is down after successful sale

The client sends a sale request to the terminal and the sale is displayed on the terminal and the cardholder makes the payment. When the terminal then tries to send a SALE_COMPLETED to CloudLink, it can not be contacted.

The terminal voids the previous sale.

![image6.png](image/img-dbded41070190d9e62c30a4ff06368f8.png)

### Callback is down after successful sale

The client sends a sale request to the terminal and the sale is displayed on the terminal and the cardholder makes the payment. When the terminal then sends a SALE_COMPLETED to CloudLink which will try and contact the callback, but it can not be contacted.

The terminal voids the previous sale.

![image5.png](image/img-e40ccda392dc61c2ef3483d3cfdfbfb8.png)

### Terminal busy

A client tries to send a sale to a terminal who is already processing a sale from another client, the terminal sends back an event TERMINAL_BUSY.

![image1.png](image/img-5298655a160bd0ed16f0fcbc5751095b.png)