Exchange API Product Guide Welcome to the product guide for our Exchange API, also referred to as the Crypto Exchange API in the product page. We wrote this guide as an intermediate step between our product page and the API endpoints documentation where we describe all possible usages and nuances of the Exchange API without delving into code nor API responses. In a nutshell, the Exchange API gives programmatic access to our engine and it allows users to exchange up to 1,000 CHF per day and 100,000 CHF per year without identity verification, or above this limit with identity verification.

Audience This document is meant for: Partners implementing the Crypto Exchange API via an application they operate. Developers working on applications to be operated by partners. Goals Specify an additional fee to be deducted on the input amount on behalf of the partner by Bity. Overview Partners can specify an additional fee for each order they facilitate. This fee is hereafter referred to as the “Partner Fee”.

Audience This document is meant for: Partners implementing the Crypto Exchange API via a confidential application they operate and which acts of their behalf. Developers working on a confidential application to be operated by partners (the user and the operator is the same person, the application is not provided as a service). Goals Place orders via a confidential application on behalf of the application operator such that the following points are satisfied:

Audience This document is meant for: Partners implementing the Crypto Exchange API via a confidential application they develop. Developers working on a confidential application with users using a Bity account. Goals Place orders via a confidential application, on behalf of users using their Bity account, in such a way that the following points are satisfied: The rules applying specifically to the logged-in user are in effect which can enable more flexibility, such as: higher volume, money transfer, use of an unspecified object to pay the order, no need to provide a signature, listing and accessing previously placed orders etc.

Audience This document is meant for: Partners implementing the Crypto Exchange API via a confidential application they operate. Developers working on a confidential application to be operated by partners. Goals Place orders via a confidential application, on behalf of users which don’t have a Bity account or don’t use their Bity account, in such a way that the following points are satisfied: The confidential application is able to list orders it previously placed and is able to obtain the order details of orders it previously placed with the limitation that only the orders for which the following property holds true are fully visible: the order has not reached a final state or the order has reached a final state in the last two weeks.

Audience This document is meant for: Partners implementing the Crypto Exchange API via a public application they develop. Developers working on a public application with users using a Bity account. Goals Place orders via a public application, on behalf of users using their Bity account, in such a way that the following points are satisfied: The rules applying specifically to the logged-in user are in effect which can enable more flexibility, such as: higher volume, money transfer, use of an unspecified object to pay the order, no need to provide a signature, listing and accessing previously placed orders etc.