---
title: "Handling Timeouts"
source_url: https://docs.rapyd.net/en/handling-timeouts-422739.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)

### 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.

![image18.png](image/img-470135b70dca8b9b58c32fd79a187c3d.png)

### Sale is not confirmed

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 and the client polls the response (or not), but does not confirm within a time period.

The terminal voids the previous sale.

![image11.png](image/img-7c9354abdbdf2fd8e426f0dc370da5c4.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.

![image4.png](image/img-617a1d51f356d1db5e3d4d66e09cc417.png)