Bisq Wiki - User contributions [en]

Bisq 2

2026-06-12T07:44:05Z

SuddenWhipVapor: /* Download and verify */ step to refresh expired key

Bisq 2 is the successor to the original Bisq ([[Bisq 1|Bisq v1]]). It has been developed from the ground up to allow for multiple trade protocols to be accessed via a single decentralized exchange platform, and it also sports a proper mobile version, [[Bisq 2 mobile]].

At the initial launch of Bisq 2 will support only one trading protocol '[[Bisq Easy]]'. Over time more trading protocols will be added.

Once the Bisq Multisig protocol is implemented in Bisq 2, the old version of Bisq can fade out. [[Bisq 1]] will still find its usage as Bisq DAO management tool and for BSQ-BTC trading.

Similar to Bisq v1, Bisq 2 will be a decentralized bitcoin exchange that allows anyone to buy and sell bitcoin in exchange for national currencies or other cryptocurrencies.

* Bisq 2 is a desktop application that works across platforms.
* Bisq 2 allows users to choose between multiple trading protocols to find the best fit for their preference. Aspects like privacy and security, convenience, costs and trade duration will differ and the user can make the choice.
* Bisq 2 is a peer-to-peer network that enables users to find people to trade with, make and take offers to buy and sell bitcoin, communicate with their trading peers and when necessary access support.
* Bisq 2 is privacy focused, no verified accounts or KYC will be required and run over the Tor network (as well as I2P in future).
* Bisq 2 is self custodial. Your keys are always under your control.
* Bisq 2 is open source (AGPL) and built and maintained by contributors who form the Bisq DAO.

== Why Bisq 2? ==

Bisq v1 is a powerful tool for bitcoiners that want to be able to buy and sell bitcoin peer to peer whilst maintaining their privacy, not having to undergo arduous KYC processes, and keeping control of their bitcoin.

Bisq v1 was launched on mainnet in April 2016 and whilst there has been constant improvements to the trade protocol and user interface over the years it was designed from the outset to support only one trade protocol. As bitcoin has developed and Bisq user base has grown there has been an obvious need for Bisq to expand its offerings to offer more options to its users for example trades over lightning and access via mobile devices. Bisq 2 is the first step to develop something that is built from the ground up to be more accessible to users and provide access to multiple trading protocols that can expand over time.

The core benefits of Bisq 2 are:

=== Multiple Trade Protocols ===

Bisq 2 will offer a variety of [[trade protocols]] for users. Each trade protocol will come with its own benefits and tradeoffs. Having multiple protocols allows users to choose what trade protocols are best for them based on; convenience, security, miner costs, trade fees, privacy, available support etc. All trade protocols can be accessed independently and users can switch between protocols for different trades.

The follow trade protocols are on the roadmap:

* [[Bisq_Easy|Bisq Easy]]: Reputation based trading with no security deposit requirements (included in the initial launch)
* Bisq Multisig: Similar to the current trade protocol used by Bisq 1 but with some improvements

* Submarine Swaps: Atomic swap of LN BTC <-> mainnet BTC

* Liquid Submarine Swaps: Atomic swap of LN BTC <-> Liquid BTC

* Liquid Multisig: Bisq Multisig ported to Liquid network with faster confirmation, lower fees and better privacy (confidential transactions)

* Bisq Lightning: LN BTC <-> Fiat (chain of multiple protocols: Liquid Submarine Swaps, Liquid Multisig)
* Liquid Swaps: Atomic swap of Liquid BTC <-> Liquid assets like L-USDT

* BSQ Swaps: Atomic swap of BSQ <-> BTC
* Monero Swaps: Cross chain atomic swap of BTC <-> XMR

Find out more about the [[Trade_Protocols|trade protocols]] Bisq 2 will use.

=== Multiple privacy networks ===
Bisq 2 will support multiple privacy networks. Initially it will only support Tor but I2P support is already implemented but in an experimental state. Upcoming privacy networks like Nym could be added in future if they fit the requirements.

Having multiple networks adds resilience in case one network has availability issues (as it happened multiple times with Tor when DoS attacks decreased the Tor network stability and with that Bisq's availability and stability).

The P2P network has also a built in DoS protection using Proof of Work and comes with many improvements compared to the Bisq 1 P2P network.

===Multiple Identities ===

Bisq 1 used a single onion address and key pair which represent the user's identity. Bisq 2 will allow users to create multiple identities, giving the user more control and better privacy. The user can choose between the highest level of convenience and use just one global identity for all interactions (like Bisq 1) or at the other extreme use a separate identity for any type of interaction (e.g. use a different identity for each trade as well as for each chat room). And anything in between (separating fiat and altcoin trades,...).

Find out more about how Bisq 2 manages [[Identity|identities]].

=== Multiple applications ===

The reference implementation will be the Bisq 2 JavaFx desktop application.

But there is also ongoing work on a HTML interface with a headless application to be used on personal Node projects like Start9, Umbrel, MyNode,...

Beside that there will be a REST API (useful for trading bots,...).

Bisq Easy can be implemented as a mobile app (at least for Android there are no conceptual or technical hurdles).

=== Multiple wallets ===

At launch time Bisq 2 will not include a wallet, but work is underway to support multiple wallet options.

Bitcoin core as a full wallet is already implemented (but not exposed in the UI). For users who do not want to run a full Bitcoin node, there will be a light wallet option. Currently Electrum is implemented but we might change to another solution.

For the different trade protocols there will be the specific wallets required. E.g. for Liquid the Elements wallet is already integrated. For Monero Swaps we need to provide an interface for using the Monero wallet. Find out more about the [[Bisq_2_Wallet|Bisq 2 wallet]].

=== Bonded Roles ===

The contributors providing the resources and infrastructure for Bisq 2 will require their roles to be bonded. This concept was also used in Bisq 1 but as it was not strictly enforced by the system, not all roles are secured by bonds as it was envisioned. In Bisq 2 having set up a BSQ bond is mandatory for most roles and node operators and enforced by the system.

Find out more about the [[Bisq_2_Roles|Bisq 2 roles]].

== Bisq 1 vs Bisq 2 ==

When Bisq 2 is launched it will initially only use the one trade protocol '[[Bisq Easy]]' therefore the differences are based on a 2-of-2 multisig protocol (Bisq 1) vs a reputation based trade protocol (Bisq Easy).

== Bisq Easy ==

Bisq Easy was designed for new Bitcoin users who have not yet purchased Bitcoin and therefore cannot use Bisq 1 due the requirements of the security deposit. A lot of effort was put into making it as simple to use as possible.

Bisq Easy tries to replicate the experience of a novice Bitcoiner visiting a Bitcoin meetup and getting a gentle and friendly introduction into the Bitcoin world as well as the opportunity to purchase their first Bitcoin from a helpful peer. This is inspired by the famous Satoshi Squares (early days informal Bitcoin meetups), which was also the initial name inspiration for Bitsquare - the previous brand name of Bisq.

The seller is expected to be an experienced Bitcoin and Bisq user and to have built up a reputation. The seller should be helpful and serve as guide through the newbie's first Bitcoin trade.

Bisq Easy tries to be a much more social experience as it is the case on Bisq 2. It also provides a "learn" section where newbies can learn about important topics like wallets, privacy and security. The various sections for chat rooms should also boost the social and communicative aspect of Bisq Easy.

=== Main differences for BTC buyers ===

Initially when Bisq 2 is launched the difference between versions will be that Bisq 2 will allow for users to buy bitcoin with no security deposit, no trade fees and no miner fees. Whereas, Bisq 1 will allow users to buy bitcoin with a security deposit and incur trade fees and miner costs.

The tradeoff for Bisq 2 is that the security of the trade will be based on seller reputation as opposed to Bisq 1 where the security of the trade is based on bitcoin collateral secured in the multisig.

Therefore, Bisq 2 will be cheaper and more convenient to trade for bitcoin buyers but at the cost of less robust security than Bisq 1. This is opposed to Bisq 1 that will be more secure but also more expensive, in terms of trade and miner fees, and less convenient for bitcoin buyers.

Bisq 2 will initially be more suitable for users wanting to complete trades for small amounts of bitcoin, whereas, Bisq 1 will continue to be suitable for users wanting to complete trades for larger amounts of bitcoin.

=== Main differences for BTC sellers ===

Initially when Bisq 2 is launched the difference between versions will be that Bisq 2 will allow users to sell bitcoin with no security deposit, no trade fees and no security deposit. Whereas, Bisq 1 will allow users to sell bitcoin with a security deposit and incur trade fees and miner costs.

Sellers on Bisq 2 will be expected to build their reputation. This can be done in multiple ways but to achieve a high reputation they will need to either burn BSQ and / or create a BSQ bond that locks in a specific amount of BSQ for a specified length of time.

The first iteration of Bisq 2 will have more buyers than sellers. That means a small number of sellers will be servicing the buyers. Bitcoin sellers on Bisq 2 will be required to make a judgement on how best to achieve their reputation and what the cost of doing so will involve. Bitcoin seller's using Bisq 2 will also need to account for the fact that bitcoin buyers are not putting down a security deposit for their trades so there will likely be a higher trade abandonment than in Bisq 1.

It is expected that some bitcoin sellers currently active on Bisq 1 may choose to experiment with Bisq 2, and the number of buyers and sellers on Bisq 2 will grow over time.

As in Bisq 1 seller's will be able to choose the price above or below market they wish to sell their bitcoin for.

Due to the requirements on bonds and the potential higher effort on communication with a newbie Bitcoiner, the price premium can be expected to be much higher than in Bisq 1 (maybe 10-15% above market). The Seller is the one who sets the price.

== How Bisq 2 keeps data private ==

Bisq 2 achieves data privacy for users in the same way as Bisq 1:

* Using Bisq requires no registration or centralized identity verification
* Every Bisq application connects to the Bisq network with a Tor hidden service (as well as I2P in future)
* Bisq has no central servers or databases to record data
* Data is encrypted such that trade details are readable only by counter-parties

== How Bisq 2 resists censorship ==

Bisq 2 achieves censorship resistance in the same way as Bisq 1:

* Bisq’s network is a fully distributed P2P network, and thus difficult to shut down
* Bisq’s network is built on top of Tor (I2P), and thus inherits Tor’s own censorship resistance
* Bisq is an open source project and a DAO, not a company; it is not incorporated, and thus cannot be dis-incorporated

== Advanced configurations for Bisq 2 ==

For users that want to tinker with the default config setting. Bisq 2 supports users to add a config file in the data directory which overrides the default config.

This can be useful instead of dealing with command line options. Command-line options override values set in the configuration file.

For more info see the GitHub pull request [https://github.com/bisq-network/bisq2/pull/2201 here].

== Installation ==

=== Download and verify ===

Bisq2 can be downloaded [https://bisq.network/downloads/ here]. Before installing software that manages your funds, you should always verify the installer has not been tampered with, to avoid the risk of losing funds due to a compromised download.

To import the key in Linux and MacOS:

<code>curl https://bisq.network/pubkey/E222AA02.asc | gpg --import </code>

GPG will return "This key is not certified with a trusted signature!", this is normal (see https://serverfault.com/questions/569911/how-to-verify-an-imported-gpg-key for background information what it means)

To verify the installer against the signature:

<code>gpg --digest-algo SHA256 --verify BINARY{.asc*,}</code>

Replace BINARY with the name of the file you downloaded.

In case you receive an error for an expired key, you can refresh the keys on your system from an official keyserver:

<nowiki>gpg --keyserver hkps://keys.openpgp.org --refresh-keys</nowiki>

In Windows you can import the key, and subsequently verify the installer, by using [https://www.gpg4win.org/download.html Kleopatra].

=== Known issues with installation ===

'''MacOS'''

Notarization was removed from the build pipeline because of the risk of Apple certification revocation ([https://github.com/bisq-network/bisq/discussions/6341 GitHub issue]). Unfortunately this will require extra steps when installing Bisq on macOS.

Please follow the guide at https://support.apple.com/en-us/HT202491 in the section "If you want to open an app that hasn’t been notarized or is from an unidentified developer".

If you are using macOS Ventura (13.0+) you need to execute the following in your terminal to be able to start Bisq 2:

<code>sudo xattr -rd com.apple.quarantine /Applications/Bisq2.app</code>

You will be prompted to enter your password to execute the command as super user, and this should allow you to start Bisq 2 normally.

'''Windows'''

The developer code signing was removed for the same reason as above. You can ignore the warning after having verified the installer.

There are known issues with antivirus software: Bisq or Tor processes could be prevented from running, files could get deleted in the data directory [2] or the application directory [1]), or startup could be delayed to the point that Tor is terminated, and a lockfile is left behind preventing Bisq from being started again (this requires you to restart Windows in order to remove the lockfile). These issues are currently being evaluated and addressed.

Windows suffers from a much wider attack surface compared to Linux or OSX, please consider using a different operating system when dealing with cryptocurrencies.

[1] Application directory (contains application installation files): C:\Users<username>\AppData\Local\Bisq2

[2] Data directory (contains all Bisq data): C:\Users<username>\AppData\Roaming\Bisq2

'''Linux'''

Debian users: if you have issues starting Bisq, run <code>/opt/bisq2/bin/Bisq2</code>

If your Linux distribution does not support .deb files please follow these instructions:

<code>
cd ~/Downloads

mkdir tmp

cd tmp

ar x ../Bisq-64bit-2.1.2.deb

sudo tar Jxvf data.tar.xz

sudo cp -rp opt/Bisq2 /opt/
</code>

The above is not tested in all distributions, if you encounter issues please report them [https://github.com/bisq-network/bisq2/issues here].

Downloading and installing

2026-06-12T07:43:10Z

SuddenWhipVapor: /* Verify the signature of the binary you downloaded */ step to refresh keys where needed

To use Bisq, you must first '''[https://bisq.network/downloads/ download and install]''' it. Most exchanges are centralized exchanges running on servers controlled by the exchange. Bisq is decentralized, running only on the desktops of Bisq users.

Bisq manages offers to trade using a peer-to-peer network. This is a global network made of users who are also running Bisq on their own computers.

Centralized services are easy to monitor, block, and shut down, while peer-to-peer networks like BitTorrent, Bitcoin and Bisq are difficult to surveil, censor, shut down or hack.

All of this means that if you want to use the Bisq network, you must download and run the software on your own machine.

== Download Bisq ==

The most convenient way to install Bisq on your machine is from a pre-built install file from the [https://bisq.network/downloads/ Bisq website] or [https://github.com/bisq-network/bisq/releases/latest latest GitHub release].

There's also a community-maintained [https://snapcraft.io/bisq-desktop Snap package] for various Linux distributions.

{{Admonition_Note|See [[#OS-specific_install_notes|install notes for various Linux distributions below]].}}

You can download the installer for your operating system and install Bisq right away, but we strongly recommend that you [[ #Verify installer file | verify the integrity ]] of your installer file first.

'''If you have issues, please check the ''Known issues with installation'' section in [https://github.com/bisq-network/bisq/releases/latest release notes].'''

== Verify installer file ==

=== Bisq2 specific instructions ===

Bisq2 can be downloaded [https://bisq.network/downloads/ here]. Before installing software that manages your funds, you should always verify the installer has not been tampered with, to avoid the risk of losing funds due to a compromised download.

Usually, installation binaries are signed by Alejandro García (key ID: E222AA02, primary release manager). However, since this key has expired — and the expired key was included in previous versions of the Bisq2 app — the in-app verification process would fail when attempting to download version 2.1.2. To prevent this issue, the secondary release manager assumed responsibility for signing that release. The signingkey.asc file specifies the key used for signing the binaries.

HenrikJannsen's signing key can be downloaded [https://bisq.network/pubkey/387C8307.asc here] (full fingerprint: B8A5 D214 ADFA A387 A14C 8BCF 02AA 2BAE 387C 8307).

To import the key in Linux and MacOS:

<nowiki>curl https://bisq.network/pubkey/387C8307.asc | gpg --import </nowiki>

GPG will return "This key is not certified with a trusted signature!", this is normal (see https://serverfault.com/questions/569911/how-to-verify-an-imported-gpg-key for background information what it means)

To verify the installer against the signature:

<nowiki>gpg --digest-algo SHA256 --verify BINARY{.asc*,}</nowiki>

In case you receive an error for an expired key, you can refresh the keys on your system from an official keyserver:

<nowiki>gpg --keyserver hkps://keys.openpgp.org --refresh-keys</nowiki>

Replace BINARY with the name of the file you downloaded.

In Windows. you can import the key, and subsequently verify the installer, by using [https://www.gpg4win.org/download.html Kleopatra].

Any software that manages funds, signs transactions, and deals with highly sensitive data is a prime target for malware. Bisq does all three. Therefore, it is highly recommended that you verify the integrity of the installer file you use to install Bisq.

This verification is something that you should do for the initial Bisq install. After the initial install, you will be prompted to install updates through Bisq's interface. The Bisq software will verify the integrity of updates for you.

Bisq installer files are currently built and signed by Alejandro Garcia (alejandrogarcia83). His public key ID is <code>E222AA02</code> and fingerprint is <code>B493 3191 06CC 3D1F 252E 19CB F806 F422 E222 AA02</code>, which you can verify through [https://github.com/bisq-network/bisq/commits?author=alejandrogarcia83 commits on GitHub].

The full public key is available [https://bisq.network/pubkey/E222AA02.asc here on the Bisq website].

<span id="bisq-1-obtain-signature-files-for-installer-files"></span>

= Bisq 1: Obtain signature files for installer files =

All Bisq releases are cryptographically signed by its maintainer. Users can ensure that nobody tampered with the release by verifying its signatures. It’s recommended to download the GPG key from an independent keyserver (such as [https://keys.openpgp.org/ keys.openpgp.org] or [https://keyserver.ubuntu.com/ keyserver.ubuntu.com]) to ensure that no adversary replaced the GPG keys and signatures on the release server.

Bisq 1 releases are signed by Alejandro García (alejandrogarcia83), Gabriel Bernard (gabernard), or Henrik Jannsen (HenrikJannsen). Here are the public key ids and fingerprints of the keys:

Alejandro García (public key id <code>0xF806F422E222AA02</code>): <code>B493 3191 06CC 3D1F 252E 19CB F806 F422 E222 AA02</code>
<br>
Gabriel Bernard (public key id <code>0x6C8D14D84A133008</code>): <code>1655 3BA9 2694 95EE 53BB A33A 6C8D 14D8 4A13 3008</code>
<br>
Henrik Jannsen (public key id <code>0x02AA2BAE387C8307</code>): <code>B8A5 D214 ADFA A387 A14C 8BCF 02AA 2BAE 387C 8307</code>

<span id="windows"></span>
== Windows ==

<span id="download-and-install-gpg4win"></span>
=== Download and install Gpg4win ===

Windows does not come with GPG software installed by default, so you will need to install it in order to verify Bisq’s installer files. You can get Gpg4win [https://www.gpg4win.org/ here]. Double-click the installer file and proceed to install with all default settings.

<span id="import-alejandro-garcías-key"></span>
=== Import Signing Keys ===

Open Kleopatra (part of Gpg4win) and click on “Lookup on Server”.

[[File:Image_1.cleaned.png]]

Next type into the search field <code>alejandro.garcia@disroot.org</code> (or <code>0x387C8307</code> if verifying a release signed by Henrik Jannsen) and press on search. You’ll see the following output:

[[File:Image 2.cleaned.png]]

Press on “Details…” to see the key’s fingerprint and confirm that it is correct based on the list above.

[[File:Image 3.cleaned.png]]

After verifying that the fingerprint is correct, press on “Close” and press on “Import” to import the key.

<span id="verify-the-signature-of-the-binary-you-downloaded"></span>
=== Verify the signature of the binary you downloaded ===

With the <code>install-file.exe</code> and <code>signature-file.exe.asc</code> in the same directory, double-click on the <code>.exe.asc</code> file.

You should see a Kleopatra window pop up with a green progress bar that says “Verified .exe with .exe.asc”. The program will continue to say “The data could not be verified” in bold but you can disregard that message.

This means the installer file we downloaded is intact and as intended. You can proceed to install Bisq by double-clicking the .exe file.

<span id="mac-and-linux"></span>
== Mac and Linux ==

<span id="import-alejandro-garcías-key-1"></span>
=== Import Signing Keys ===

To import the signing keys for Alejandro García and Henrik Jannsen, open a terminal and run:

<pre>gpg --receive-keys 0xF806F422E222AA02 0x02AA2BAE387C8307</pre>
Next you need to verify key’s fingerprint and tell GPG to trust the key. For example, to verify Alejandro's key, run:

<pre>gpg --edit-key 0xF806F422E222AA02</pre>
Then type:

<pre>fpr</pre>
Now ensure that you see the same output as here:

<pre>gpg> fpr
pub rsa4096/0xF806F422E222AA02 2022-09-28 Alejandro García <alejandro.garcia@disroot.org>
Primary key fingerprint: B493 3191 06CC 3D1F 252E 19CB F806 F422 E222 AA02</pre>
If the fingerprint matches you can trust the key. To trust the key type:

<pre>trust</pre>
Now you’ll see following output:

<pre>gpg> trust
pub rsa4096/0xF806F422E222AA02
created: 2022-09-28 expires: 2026-10-03 usage: SC
trust: unknown validity: unknown
sub rsa4096/0xE7F08D07C72561D0
created: 2022-09-28 expires: 2026-10-03 usage: E
[ unknown] (1). Alejandro García <alejandro.garcia@disroot.org>

Please decide how far you trust this user to correctly verify other users' keys
(by looking at passports, checking fingerprints from different sources, etc.)

1 = I don't know or won't say
2 = I do NOT trust
3 = I trust marginally
4 = I trust fully
5 = I trust ultimately
m = back to the main menu

Your decision?</pre>
Type <code>5</code> to trust to the key and you’ll see following output:

<pre>Do you really want to set this key to ultimate trust? (y/N) </pre>
Now type <code>y</code> to confirm. Now you can quit by typing <code>quit</code>.

<span id="verify-the-signature-of-the-binary-you-downloaded-1"></span>
=== Verify the signature of the binary you downloaded ===

With the installer file and installer signature file in the same directory, run:

<pre>gpg --verify INSTALLER.asc INSTALLER</pre>
Where <code>INSTALLER.asc</code> is the filename of the <code>.asc</code> file you just downloaded.

You should see an output similar to this:

<pre>gpg: Signature made Fri 22 Nov 2024 07:42:50 PM UTC
gpg: using RSA key B493319106CC3D1F252E19CBF806F422E222AA02
gpg: checking the trustdb
gpg: marginals needed: 3 completes needed: 1 trust model: pgp
gpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: next trustdb check due at 2026-10-03
gpg: Good signature from "Alejandro García <alejandro.garcia@disroot.org>" [ultimate]</pre>

In case you receive an error for an expired key, you can refresh the keys on your system from an official keyserver:

<nowiki>gpg --keyserver hkps://keys.openpgp.org --refresh-keys</nowiki>

== Build from source ==

[https://github.com/bisq-network/bisq/blob/master/docs/build.md Building Bisq from source] requires only a single command once you have the correct JDK installed on your machine.

Finding and installing the correct JDK can sometimes be frustrating, so Bisq's developers have written scripts to make it easier:
* [https://github.com/bisq-network/bisq/blob/master/scripts/install_java.sh For Linux and macOS]
* [https://github.com/bisq-network/bisq/blob/master/scripts/install_java.bat For Windows]

== OS-specific install notes ==

=== macOS ===

Starting with version v1.9.6, we remove notarization from our build pipeline because of of the risk of Apple certification revocation (see https://github.com/bisq-network/bisq/discussions/6341). Unfortunately this will require extra steps when installing Bisq on macOS.

You will receive an error popup saying that Bisq ''is damaged and can't be opened. You should move it to the Trash''.

Please follow the guide at https://support.apple.com/en-us/HT202491 in the section ''If you want to open an app that hasn’t been notarized or is from an unidentified developer''

If you are running already macOS Ventura (13.0+) you need to do following to be able to start Bisq:
* enter following command in Apple Terminal <code>sudo xattr -d com.apple.quarantine /Applications/Bisq.app</code>
* hit enter and you will be prompted to enter your password to be able to execute the command as super user

After running this successfully you should be able to start Bisq as always.

If this procedure still does not allow you to install Bisq, a last resort workaround is to install Bisq in a Linux Virtual Machine running on your system.

=== Windows ===

Starting with version v1.9.6, we remove the developer code signing because of the same reason as with Apple.

For Windows you just have to ignore the warning after you have verified the installation file yourself and proceed with the installation.

=== Linux (General) ===

Bisq works with a number of Linux distros, but not all desktop environments are supported.

These are all known compatible desktop environments. This is a growing list. If you find another compatible desktop, please inform us so it can be added.

* GNOME
* Mate
* Xfce
* KDE Plasma
* Cinnamon

Bisq might not work properly if you switch from the original desktop environment of your Linux distribution to a different one.

Note: users with discrete GPUs may encounter issues launching Bisq in some desktop environments.

=== Arch Linux ===

The Bisq [https://bisq.network/downloads/ downloads page] includes a link to the Arch User Repository (AUR) page for the [https://aur.archlinux.org/packages/bisq/ bisq package].

# From the command line, clone the repository from AUR.
# Then from the cloned directory, run <code>makepkg -si</code>. This will read the PKGBUILD file to download, verify, build, and install the various tools necessary to install Bisq.

If the version found on AUR is not up to date, you can read [[Fix_Arch_release]].

Please be advised: when you're using AUR, you're responsible for your own safety. Be sure to verify the PKGBUILD file.

=== Gentoo ===

Use <code>eselect repository enable booboo</code> to use the 'booboo' overlay which carries the binaries, and then emerge <code>bisq</code>

=== Tails ===

Please see [[Running Bisq on Tails]] for details on downloading, installing, and configuring Bisq on Tails.

=== Qubes ===

Please see [[Running Bisq on Qubes]] for a detailed Qubes setup guide.

== Update Bisq ==

Installing a new Bisq version will update Bisq. More details at [[Updating Bisq]].

[[Category:Use Cases]]

Downloading and installing

2026-06-12T07:42:45Z

SuddenWhipVapor: /* Bisq2 specific instructions */ add step to refresh expired keys

To use Bisq, you must first '''[https://bisq.network/downloads/ download and install]''' it. Most exchanges are centralized exchanges running on servers controlled by the exchange. Bisq is decentralized, running only on the desktops of Bisq users.

Bisq manages offers to trade using a peer-to-peer network. This is a global network made of users who are also running Bisq on their own computers.

Centralized services are easy to monitor, block, and shut down, while peer-to-peer networks like BitTorrent, Bitcoin and Bisq are difficult to surveil, censor, shut down or hack.

All of this means that if you want to use the Bisq network, you must download and run the software on your own machine.

== Download Bisq ==

The most convenient way to install Bisq on your machine is from a pre-built install file from the [https://bisq.network/downloads/ Bisq website] or [https://github.com/bisq-network/bisq/releases/latest latest GitHub release].

There's also a community-maintained [https://snapcraft.io/bisq-desktop Snap package] for various Linux distributions.

{{Admonition_Note|See [[#OS-specific_install_notes|install notes for various Linux distributions below]].}}

You can download the installer for your operating system and install Bisq right away, but we strongly recommend that you [[ #Verify installer file | verify the integrity ]] of your installer file first.

'''If you have issues, please check the ''Known issues with installation'' section in [https://github.com/bisq-network/bisq/releases/latest release notes].'''

== Verify installer file ==

=== Bisq2 specific instructions ===

Bisq2 can be downloaded [https://bisq.network/downloads/ here]. Before installing software that manages your funds, you should always verify the installer has not been tampered with, to avoid the risk of losing funds due to a compromised download.

Usually, installation binaries are signed by Alejandro García (key ID: E222AA02, primary release manager). However, since this key has expired — and the expired key was included in previous versions of the Bisq2 app — the in-app verification process would fail when attempting to download version 2.1.2. To prevent this issue, the secondary release manager assumed responsibility for signing that release. The signingkey.asc file specifies the key used for signing the binaries.

HenrikJannsen's signing key can be downloaded [https://bisq.network/pubkey/387C8307.asc here] (full fingerprint: B8A5 D214 ADFA A387 A14C 8BCF 02AA 2BAE 387C 8307).

To import the key in Linux and MacOS:

<nowiki>curl https://bisq.network/pubkey/387C8307.asc | gpg --import </nowiki>

GPG will return "This key is not certified with a trusted signature!", this is normal (see https://serverfault.com/questions/569911/how-to-verify-an-imported-gpg-key for background information what it means)

To verify the installer against the signature:

<nowiki>gpg --digest-algo SHA256 --verify BINARY{.asc*,}</nowiki>

In case you receive an error for an expired key, you can refresh the keys on your system from an official keyserver:

<nowiki>gpg --keyserver hkps://keys.openpgp.org --refresh-keys</nowiki>

Replace BINARY with the name of the file you downloaded.

In Windows. you can import the key, and subsequently verify the installer, by using [https://www.gpg4win.org/download.html Kleopatra].

Any software that manages funds, signs transactions, and deals with highly sensitive data is a prime target for malware. Bisq does all three. Therefore, it is highly recommended that you verify the integrity of the installer file you use to install Bisq.

This verification is something that you should do for the initial Bisq install. After the initial install, you will be prompted to install updates through Bisq's interface. The Bisq software will verify the integrity of updates for you.

Bisq installer files are currently built and signed by Alejandro Garcia (alejandrogarcia83). His public key ID is <code>E222AA02</code> and fingerprint is <code>B493 3191 06CC 3D1F 252E 19CB F806 F422 E222 AA02</code>, which you can verify through [https://github.com/bisq-network/bisq/commits?author=alejandrogarcia83 commits on GitHub].

The full public key is available [https://bisq.network/pubkey/E222AA02.asc here on the Bisq website].

<span id="bisq-1-obtain-signature-files-for-installer-files"></span>

= Bisq 1: Obtain signature files for installer files =

All Bisq releases are cryptographically signed by its maintainer. Users can ensure that nobody tampered with the release by verifying its signatures. It’s recommended to download the GPG key from an independent keyserver (such as [https://keys.openpgp.org/ keys.openpgp.org] or [https://keyserver.ubuntu.com/ keyserver.ubuntu.com]) to ensure that no adversary replaced the GPG keys and signatures on the release server.

Bisq 1 releases are signed by Alejandro García (alejandrogarcia83), Gabriel Bernard (gabernard), or Henrik Jannsen (HenrikJannsen). Here are the public key ids and fingerprints of the keys:

Alejandro García (public key id <code>0xF806F422E222AA02</code>): <code>B493 3191 06CC 3D1F 252E 19CB F806 F422 E222 AA02</code>
<br>
Gabriel Bernard (public key id <code>0x6C8D14D84A133008</code>): <code>1655 3BA9 2694 95EE 53BB A33A 6C8D 14D8 4A13 3008</code>
<br>
Henrik Jannsen (public key id <code>0x02AA2BAE387C8307</code>): <code>B8A5 D214 ADFA A387 A14C 8BCF 02AA 2BAE 387C 8307</code>

<span id="windows"></span>
== Windows ==

<span id="download-and-install-gpg4win"></span>
=== Download and install Gpg4win ===

Windows does not come with GPG software installed by default, so you will need to install it in order to verify Bisq’s installer files. You can get Gpg4win [https://www.gpg4win.org/ here]. Double-click the installer file and proceed to install with all default settings.

<span id="import-alejandro-garcías-key"></span>
=== Import Signing Keys ===

Open Kleopatra (part of Gpg4win) and click on “Lookup on Server”.

[[File:Image_1.cleaned.png]]

Next type into the search field <code>alejandro.garcia@disroot.org</code> (or <code>0x387C8307</code> if verifying a release signed by Henrik Jannsen) and press on search. You’ll see the following output:

[[File:Image 2.cleaned.png]]

Press on “Details…” to see the key’s fingerprint and confirm that it is correct based on the list above.

[[File:Image 3.cleaned.png]]

After verifying that the fingerprint is correct, press on “Close” and press on “Import” to import the key.

<span id="verify-the-signature-of-the-binary-you-downloaded"></span>
=== Verify the signature of the binary you downloaded ===

With the <code>install-file.exe</code> and <code>signature-file.exe.asc</code> in the same directory, double-click on the <code>.exe.asc</code> file.

You should see a Kleopatra window pop up with a green progress bar that says “Verified .exe with .exe.asc”. The program will continue to say “The data could not be verified” in bold but you can disregard that message.

This means the installer file we downloaded is intact and as intended. You can proceed to install Bisq by double-clicking the .exe file.

<span id="mac-and-linux"></span>
== Mac and Linux ==

<span id="import-alejandro-garcías-key-1"></span>
=== Import Signing Keys ===

To import the signing keys for Alejandro García and Henrik Jannsen, open a terminal and run:

<pre>gpg --receive-keys 0xF806F422E222AA02 0x02AA2BAE387C8307</pre>
Next you need to verify key’s fingerprint and tell GPG to trust the key. For example, to verify Alejandro's key, run:

<pre>gpg --edit-key 0xF806F422E222AA02</pre>
Then type:

<pre>fpr</pre>
Now ensure that you see the same output as here:

<pre>gpg> fpr
pub rsa4096/0xF806F422E222AA02 2022-09-28 Alejandro García <alejandro.garcia@disroot.org>
Primary key fingerprint: B493 3191 06CC 3D1F 252E 19CB F806 F422 E222 AA02</pre>
If the fingerprint matches you can trust the key. To trust the key type:

<pre>trust</pre>
Now you’ll see following output:

<pre>gpg> trust
pub rsa4096/0xF806F422E222AA02
created: 2022-09-28 expires: 2026-10-03 usage: SC
trust: unknown validity: unknown
sub rsa4096/0xE7F08D07C72561D0
created: 2022-09-28 expires: 2026-10-03 usage: E
[ unknown] (1). Alejandro García <alejandro.garcia@disroot.org>

Please decide how far you trust this user to correctly verify other users' keys
(by looking at passports, checking fingerprints from different sources, etc.)

1 = I don't know or won't say
2 = I do NOT trust
3 = I trust marginally
4 = I trust fully
5 = I trust ultimately
m = back to the main menu

Your decision?</pre>
Type <code>5</code> to trust to the key and you’ll see following output:

<pre>Do you really want to set this key to ultimate trust? (y/N) </pre>
Now type <code>y</code> to confirm. Now you can quit by typing <code>quit</code>.

<span id="verify-the-signature-of-the-binary-you-downloaded-1"></span>
=== Verify the signature of the binary you downloaded ===

With the installer file and installer signature file in the same directory, run:

<pre>gpg --verify INSTALLER.asc INSTALLER</pre>
Where <code>INSTALLER.asc</code> is the filename of the <code>.asc</code> file you just downloaded.

You should see an output similar to this:

<pre>gpg: Signature made Fri 22 Nov 2024 07:42:50 PM UTC
gpg: using RSA key B493319106CC3D1F252E19CBF806F422E222AA02
gpg: checking the trustdb
gpg: marginals needed: 3 completes needed: 1 trust model: pgp
gpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: next trustdb check due at 2026-10-03
gpg: Good signature from "Alejandro García <alejandro.garcia@disroot.org>" [ultimate]</pre>

== Build from source ==

[https://github.com/bisq-network/bisq/blob/master/docs/build.md Building Bisq from source] requires only a single command once you have the correct JDK installed on your machine.

Finding and installing the correct JDK can sometimes be frustrating, so Bisq's developers have written scripts to make it easier:
* [https://github.com/bisq-network/bisq/blob/master/scripts/install_java.sh For Linux and macOS]
* [https://github.com/bisq-network/bisq/blob/master/scripts/install_java.bat For Windows]

== OS-specific install notes ==

=== macOS ===

Starting with version v1.9.6, we remove notarization from our build pipeline because of of the risk of Apple certification revocation (see https://github.com/bisq-network/bisq/discussions/6341). Unfortunately this will require extra steps when installing Bisq on macOS.

You will receive an error popup saying that Bisq ''is damaged and can't be opened. You should move it to the Trash''.

Please follow the guide at https://support.apple.com/en-us/HT202491 in the section ''If you want to open an app that hasn’t been notarized or is from an unidentified developer''

If you are running already macOS Ventura (13.0+) you need to do following to be able to start Bisq:
* enter following command in Apple Terminal <code>sudo xattr -d com.apple.quarantine /Applications/Bisq.app</code>
* hit enter and you will be prompted to enter your password to be able to execute the command as super user

After running this successfully you should be able to start Bisq as always.

If this procedure still does not allow you to install Bisq, a last resort workaround is to install Bisq in a Linux Virtual Machine running on your system.

=== Windows ===

Starting with version v1.9.6, we remove the developer code signing because of the same reason as with Apple.

For Windows you just have to ignore the warning after you have verified the installation file yourself and proceed with the installation.

=== Linux (General) ===

Bisq works with a number of Linux distros, but not all desktop environments are supported.

These are all known compatible desktop environments. This is a growing list. If you find another compatible desktop, please inform us so it can be added.

* GNOME
* Mate
* Xfce
* KDE Plasma
* Cinnamon

Bisq might not work properly if you switch from the original desktop environment of your Linux distribution to a different one.

Note: users with discrete GPUs may encounter issues launching Bisq in some desktop environments.

=== Arch Linux ===

The Bisq [https://bisq.network/downloads/ downloads page] includes a link to the Arch User Repository (AUR) page for the [https://aur.archlinux.org/packages/bisq/ bisq package].

# From the command line, clone the repository from AUR.
# Then from the cloned directory, run <code>makepkg -si</code>. This will read the PKGBUILD file to download, verify, build, and install the various tools necessary to install Bisq.

If the version found on AUR is not up to date, you can read [[Fix_Arch_release]].

Please be advised: when you're using AUR, you're responsible for your own safety. Be sure to verify the PKGBUILD file.

=== Gentoo ===

Use <code>eselect repository enable booboo</code> to use the 'booboo' overlay which carries the binaries, and then emerge <code>bisq</code>

=== Tails ===

Please see [[Running Bisq on Tails]] for details on downloading, installing, and configuring Bisq on Tails.

=== Qubes ===

Please see [[Running Bisq on Qubes]] for a detailed Qubes setup guide.

== Update Bisq ==

Installing a new Bisq version will update Bisq. More details at [[Updating Bisq]].

[[Category:Use Cases]]

US Postal Money Order

2026-05-29T16:29:18Z

SuddenWhipVapor: updated limits

'''US Postal Money Orders''' (USPMO) are one of the most private payment methods available on Bisq. Because they are bearer instruments, they can be purchased with cash and mailed, providing a path to Bitcoin without a digital bank trail.

* '''Region:''' United States only
* '''Maximum Trade Period:''' 8 days
* '''Maximum Trade Size:''' 0.0624 BTC

This guide provides a complete overview of how to safely and privately use this payment method for buying and selling bitcoin on Bisq.

__TOC__

= Critical Trading Requirements =

Before you create or take an offer using US Postal Money Orders, you '''must''' understand and agree to the following rules. Failure to comply will result in losing any trade dispute.

{{Admonition_Note |
* '''Avoid "Same-Name" Fields:''' Do NOT write the BTC Seller’s name in both the "From" and "To" fields. Many banks and automated systems now flag these as suspicious, which can lead to complications or account closures for the Seller.
* '''Video Proof is Required:''' Photos are no longer sufficient to prove a payment was sent. BTC buyers must record a continuous video of the USPMO being filled out, placed into the envelope, and sealed with the tracking label visible.
* '''Use Tracking:''' All USPMOs must be sent with a service that provides delivery confirmation (e.g., USPS Tracking).
* '''Burden of Proof:''' In a dispute, the sender (BTC buyer) bears 100% of the responsibility to provide the required mailing video and tracking information.

If you are not prepared to follow these rules, do not trade using USPMO on Bisq.}}

= A Step-by-Step Guide to Trading with USPMO =

== Step 1: Set Up Your Payment Account ==

First, you need to [[Create_a_payment_account|set up a USPMO payment account]] in the Bisq UI. It is important to distinguish between the '''Account Information''' used within the software and the '''Physical Information''' used on the money order and envelope.

=== Account Information in Bisq UI ===
Similar to "Cash by Mail," the name you enter into your Bisq payment account does not need to match your real identity.
* '''Name:''' You may use a pseudonym or a randomly generated name in the Bisq software. This name is only seen by your trading partner in the app.
* '''Address:'''
** '''BTC Buyers:''' Use a valid return address. For privacy, a PO Box or a trusted secondary address is recommended. If the mail is returned and your return address is invalid, the funds will be lost.
** '''BTC Sellers:''' Must provide a valid mailing address where you can physically receive the envelope.

=== Information on the Physical Money Order ===
While your Bisq UI profile can be anonymous, the physical instrument has strict requirements:
* '''Never Use Fake Info:''' Writing a fake name or a pseudonym on a US Postal Money Order is a federal offense.
* '''For the Seller:''' To cash the money order, the "To" field must match your legal photo ID.
* '''For the Buyer:''' You must decide between using your '''real name''' in the "From" field (best for seller's bank compliance) or leaving it '''blank''' (best for your privacy). Do '''not''' use your Bisq pseudonym on the physical document.

== Step 2: Purchase the Money Order ==

* '''Amount Limit:''' Up to '''$1,000''' per money order. Multiple orders are allowed for larger trades.
* '''Payment Method:''' It is '''highly recommended''' to use cash. Paying with a debit card creates a data trail; credit cards are not accepted.
* '''Fees:''' As of January 2026, the fees are:
{| class="wikitable"
|+ USPMO Issuing Fees
|-
! Dollar Amount !! Fee
|-
| $0.01 to $500.00 || $2.55
|-
| $500.01 to $1,000.00 || $3.60
|-
| Postal Military Money Orders || $0.84
|}
* '''Receipt:''' Keep your receipt in a safe place. It is essential for tracking and is required if the money order is lost or damaged.

== Step 3: Filling and Sending ==

Because many banks now flag "Same-to-Same" transfers (where the same name is in both fields), you must change how you fill out the "From" (Purchaser) section.

=== Filling out the "From" Section ===
The "To" field must always be the Seller's legal name. For the "From" field, you have two choices:
# '''Your Information:''' Most secure for the seller's bank deposits.
# '''Leave Blank:''' Provides maximum privacy for the buyer, but some banks may refuse to accept the deposit if the sender information is missing.

=== Mandatory Video Proof ===
To prevent "ghost shipping" disputes, record a single continuous video:
# Show the completed USPMO (matching the trade amount and Seller's name).
# Show the USPS purchase receipt.
# Place the MO inside a blank sheet of paper (privacy layer) and then into the envelope.
# Seal the envelope and show the tracking label clearly.

== Step 4: Verify the Money Order (2025/2026 Designs) ==

Sellers should verify the authenticity of the USPMO before releasing bitcoin.

=== Red, Blue, & Red Design (2025/2026 Standard) ===
[[File:Red, Blue, & Red Postal Money Order (July 2025).jpeg|thumb|left|350px|Current Design]]
* '''Watermarks:''' Hold to light to see a '''Pony Express® rider''' on the left and "United States Postal Service" in a box on the right.
* '''Security Thread:''' A vertical thread to the right of the rider watermark with "USPS" repeating in alternating directions.
* '''QR Code:''' A QR Code on the front links directly to the USPS "Check Money Order Status" tool for easy verification.
<br style="clear: both;" />

=== Green & Purple Design (Legacy) ===
[[File:Green & Purple Postal Money Order (Point-of-Sale Version).jpeg|thumb|left|350px|Legacy Design]]
* '''Watermarks:''' A U.S. Mail eagle in the center and Benjamin Franklin watermarks on the left side.
* '''Security Thread:''' A vertical, multicolored security thread weaving in and out of the paper.
<br style="clear: both;" />

== Step 5: Cashing the Money Order ==

It is recommended to cash the USPMO at a Post Office. You will need a valid photo ID that matches the name in the "To" field.

If you are depositing into a bank, be aware that many physical branches now require you to use a teller for money orders rather than an ATM or mobile deposit.

Revolut

2026-05-29T16:28:44Z

SuddenWhipVapor: updated limits

'''Revolut''' is a payment method that offers banking services, including instant Revolut-to-Revolut transfers. It is available in [https://www.revolut.com/help/getting-started/verifying-identity/what-countries-are-supported various countries] with [https://www.revolut.com/help/getting-started/adding-money-to-revolut various currencies], making it a popular option for EUR trades on Bisq and a good possibility for other international payments.

{{Admonition_Warn|'''Revolut-to-Revolut ONLY:''' Due to recurring issues with traditional bank transfers, you '''cannot''' use a Revolut IBAN for a SEPA trade or Revolut's bank details for a Faster Payments trade on Bisq. This payment method is strictly for instant transfers between two Revolut users.}}

{{Admonition_Note|'''Version Context:''' The details on this page, particularly regarding account signing, apply to trading on '''[[Bisq 1|Bisq v1]]'''.}}

__TOC__

== Revolut Characteristics ==

* '''Availability:''' Global (supports various currencies, heavily used in EUR market).
* '''Maximum Trade Duration:''' 1 day.
* '''Maximum BTC Limit (for a fully-signed account):''' 0.0624 BTC.
* '''[[Account_limits|Account Signing]] Required:''' Yes.

== Trading Limits ==
Because Revolut is a higher-risk payment method, it is subject to '''[[Account_limits|account signing]]''' to raise trade limits. Your selling limit is unaffected and is always the maximum for the payment method.

* '''Unsigned Accounts:''' When you first create a Revolut account in Bisq, your buy limit is restricted to '''0.002 BTC'''. This limit remains until the account is signed.
* '''Signed Accounts:''' To get your account signed, you must successfully complete a trade with a peer whose own account has been signed for at least 30 days. After your account is signed, your buy limit increases over time:
** '''First 30 days after signing:''' Your buy limit remains at '''0.002 BTC'''.
** '''30-60 days after signing:''' Your buy limit increases to 50% of the maximum ('''0.0312 BTC''').
** '''After 60 days of signing:''' Your buy limit increases to the full 100% ('''0.0624 BTC''').

== Setup ==

=== 1. Find Your Revolut Username (Revtag) ===

First, you need to find your Revolut username, which Revolut calls a '''Revtag'''. This is what your trading peer will use to pay you.

To find your Revtag in the current Revolut app:
# Open the Revolut app to the main '''Home''' screen.
# Tap on your '''profile icon or initials''' in the '''top-left corner'''.
# On your Profile screen, your Revtag is displayed under your name, formatted like `<code>@username</code>`.
# '''Revtags are case-sensitive.''' Note it down exactly as it appears in the Revolut app, '''including the `@` symbol'''.

=== 2. Create the Account in Bisq ===

{| class="wikitable" style="background-color: transparent; border: none;"
| style="vertical-align:top; border: none; padding: 0 1em 0 0;" |
To create a Revolut [[Create_a_payment_account|payment account]] in Bisq, you primarily need to input your '''Revolut username (Revtag)''' into the "User name" field. Be sure to enter the full Revtag exactly as it appears in your Revolut app, '''including the `@` symbol'''. You may also need to select the currencies you wish to trade.

Remember that ''none'' of this information can be modified after an account is created. [[Account_limits#Account_signing|Account signing]] data is tied to these details and can be lost if your data directory is not [[Backing_up_application_data#Back_up_payment_accounts|properly backed up]].
| style="vertical-align:top; border: none; padding: 0;" |
[[File:Revolut create account.png|thumb|400px|right|Setting up a Revolut account in Bisq v1.]]
|}

== Trading Process ==

=== Buying BTC with Revolut ===
# Make or take an offer to buy BTC using Revolut. If your account is unsigned, look for offers from sellers with a signed-account badge to get your account signed.
# Once the trade starts and the deposit confirms, view the seller's Revolut details (their Revtag) in the Bisq trade screen.
# Log in to your Revolut app and send the exact payment amount to the seller's Revtag. Revolut's help center explains [https://www.revolut.com/help/transfers/outbound-transfers/sending-money-to-another-revolut-user/how-do-i-pay-other-revolut-users/ how to pay other Revolut users].
# After sending the payment, click the '''Payment started''' button in Bisq.

=== Selling BTC with Revolut ===
# Make or take an offer to sell BTC using Revolut.
# Once the trade starts and the deposit confirms, the buyer will see your Revolut Revtag.
# Wait for the buyer to send the payment and click "Payment started" in Bisq.
# Log in to your Revolut account and '''verify''' you have received the correct amount.
# '''Verify''' the payment came from a sender whose name '''matches''' the BTC Buyer's name shown in the Bisq trade details. ''(Note: If the names do not match, do not confirm the payment. Open [[Dispute_Resolution_in_Bisq_1|dispute resolution]] immediately.)''
# Once payment is fully verified, click '''Confirm payment receipt''' in Bisq to release the BTC.

== Troubleshooting & Disputes ==

If you have trouble finding your trading peer by their Revtag, check Revolut's troubleshooting article: [https://www.revolut.com/help/transfers/outbound-transfers/sending-money-to-another-revolut-user/i-cant-find-my-friend-on-revolut/ I can't find my friend on Revolut]. A common reason is that you or your peer may need to enable the "Payments with friends" option in privacy settings.

For any other trade issues (e.g., payment not received, wrong amount), follow the [[Dispute_Resolution_in_Bisq_1|dispute resolution]] process, which may involve a [[Mediator]].

[[Category:Payment methods]]
[[Category:Guides]]

Frequently asked questions

2026-05-29T16:27:22Z

SuddenWhipVapor: /* What are trading limits? How much can I trade at once? */ updated limits

Below is a compilation of '''frequently-asked questions (FAQ)''' about Bisq, how to use it, and how to help the project.

{{Admonition_Note|'''Version Context:''' Bisq is evolving software. While many principles here are general, specific examples regarding trade mechanics, limits, and security often refer to the classic '''[[Bisq 1|Bisq v1]]''' trading protocol unless stated otherwise. The current platform is '''[[Bisq 2]]''', which supports multiple protocols including '''[[Bisq Easy]]''' (which may have different rules, e.g., using [[Reputation]] instead of [[Security deposit|security deposits]]).}}

Feel free to ask further questions on any of Bisq's many outreach channels linked at the bottom of this page.

__TOC__

== About ==

==== How is Bisq different from other decentralized exchanges? ====

Bisq is fundamentally different: it's a peer-to-peer trading network accessed via software you run on your own hardware, not a website or centralized service. It connects you directly to other users running the software to facilitate trades. It's open-source and community-driven via a [[Decentralized autonomous organization|DAO]].

Crucially, you can trade bitcoin directly for fiat currencies (like USD, EUR) or other cryptocurrencies.

Think of it like owning your home versus renting. With Bisq, you have full control over your funds and data; with centralized services (even DEX websites), you're subject to the platform's rules and risks.

With Bisq you're always the owner:

* Bisq does '''not''' hold your bitcoin. Trading funds (in the classic v1 protocol) are held in '''2-of-2 multisignature addresses''' controlled solely by you and your trading peer.
* Bisq does '''not''' hold your national currency. Fiat transfers happen directly between traders using external payment services.
* All data travels over Bisq's secure [[P2P Network|peer-to-peer network]] built on [[Tor]]—no central servers means '''no data honeypots''' vulnerable to large-scale hacks.
* Bisq requires '''no registration or KYC''', protecting your privacy. Data about who trades with whom is not stored.
* Bisq is code, not a company, governed by its [[Decentralized autonomous organization|DAO]].

See more in the [[Introduction]].

==== Is Bisq open-source software? ====

Yes. Bisq's software is free/libre open-source licensed under the GNU Affero General Public License (AGPLv3).

You can find the [https://github.com/bisq-network/bisq source code] and [https://github.com/bisq-network/bisq/blob/master/LICENSE license] on GitHub.

==== Is Bisq safe? ====

Bisq is designed with multiple layers of security, and strong incentives encourage fair trading, making the vast majority of trades proceed smoothly.

Key security mechanisms (particularly in the classic v1 protocol) include:

* Bitcoin secured in a 2-of-2 multisignature escrow address controlled only by the traders.
* Mandatory [[Security deposit|security deposits]] from both traders, refunded upon successful completion, deterring fraud.
* A [[Dispute_Resolution_in_Bisq_1|3-tier dispute resolution system]] (trader chat, mediation, arbitration) for handling issues.

However, trading fiat currencies always carries some inherent '''chargeback risk''', as banks can sometimes reverse payments. Bisq mitigates this by:

* Supporting mainly [[Payment methods|payment methods]] known to have lower chargeback risk (explicitly avoiding easily reversed methods like PayPal or credit cards).
* Employing an [[Account_limits#Account_signing|account signing mechanism]] in v1 for certain fiat methods, which limits trade sizes for new accounts until integrity is established through successful trades.

Newer protocols like [[Bisq Easy]] use different security models, such as relying on [[Reputation|seller reputation]] instead of security deposits.

== Getting started ==

==== I find Bisq very confusing initially! ====

You're not alone; some users find the interface takes getting used to, especially compared to simpler centralized exchanges.

* Check out the official [https://bisq.network/getting-started/ getting-started guide].
* Visual guides and tutorials may be available on the [https://bisq.network/ Bisk Network website] or community channels. (Note: Previous specific video links were outdated/broken).

Bisq is under continuous development, with ongoing efforts to improve the user interface and experience.

==== My currency market has few or no offers. What can I do? ====

Market liquidity varies. Some markets are very active, while others are less so, often due to the availability of suitable local payment methods or lack of initial bootstrapping.

{{Admonition_Note|An empty offer book doesn't always mean zero activity. Sometimes users are waiting for offers to appear. Try making your own offer (acting as a [[How to be a market maker on Bisq|market maker]]) - someone might take it! This is common in markets like CAD, AUD, and GBP.}}

You can check recent activity for your market via `Market` > `Trades` in the application.

To help grow a market:
* Ensure suitable local [[Payment methods]] are supported. You can [https://github.com/bisq-network/growth/issues/new/choose suggest new ones here].
* Spread the word in relevant local communities to attract both buyers/sellers and market makers. Bisq contributors can often offer support and resources for local outreach efforts.

==== Do I really need bitcoin to buy bitcoin on Bisq? How do I get started with none? ====

Yes, the classic Bisq v1 trading protocol requires a small amount of BTC for [[Security deposit|security deposits]] and [[mining fees]], creating a "chicken-and-egg" problem for complete beginners.

Here are ways to get your first small amount of BTC:
* See suggestions on the [[Funding_your_wallet#How_to_Obtain_Your_First_Bitcoin|Funding your wallet]] page (e.g., friends, Bitcoin ATMs, earning BTC).
* Visit the `Get your first BTC` room on [https://bisq.chat Matrix] to potentially arrange small, informal trades ([[Informal_Market_for_Small_BTC_Trades|details here]]).
* Use the '''[[Bisq Easy]]''' trading protocol available in [[Bisq 2]], which does '''not''' require a security deposit, making it ideal for first-time buyers.

== Trading (Classic v1 Protocol) ==

{{Admonition_Note|The following answers primarily describe the classic Bisq v1 protocol mechanics involving security deposits.}}

==== What are trading fees? ====

[[Trading fees]] are a percentage of the trade size. If paid in BTC, makers pay 0.1% and takers pay 0.7%. Fees are roughly halved if paid in BSQ tokens. Remember you also need BTC for on-chain [[mining fees]] (for deposit and payout transactions) and the [[Security deposit|security deposit]] itself (which is returned if the trade completes successfully).

==== Mining fees are high. How can I trade cost-effectively? ====

The classic protocol requires 4 on-chain transactions (3 paid by taker, 1 by maker). To minimize costs:
* Be an offer '''[[How to be a market maker on Bisq|maker]]''' rather than a taker (fewer transactions to pay for).
* Trade when network '''[[mining fees]] are lower'''.
* Make offers for '''larger BTC amounts''' (fees are fixed per transaction, less impactful on larger trades).
* '''Pay [[Trading fees|trading fees]] with BSQ''' for an approximate 50% discount.

==== Why require a security deposit in BTC? ====

[[Security deposit|Security deposits]] incentivize both parties to follow the [[Trading rules]]. They are locked in multisig escrow with the trade amount and returned upon successful completion. If rules are broken, the deposit can be partially or fully awarded to the counterparty via [[Dispute_Resolution_in_Bisq_1|dispute resolution]], deterring violations like non-payment or failing to confirm payment.

==== What are trading limits? How much can I trade at once? ====

Maximum BTC per trade varies by [[Payment methods|payment method]] based on perceived risk (especially chargeback risk). For example, methods like Zelle or SEPA often have lower limits (e.g., 0.0624 BTC) than less reversible methods. Altcoin trades generally have higher limits (0.25 BTC in v1) as chargebacks aren't possible. Check the [[Payment methods]] page for current limits per method. Also see [[Account_limits]] regarding initial limits for new accounts.

==== Which payment methods are available? ====

See the [[Payment methods]] page for the full list. You can [https://github.com/bisq-network/growth/issues/new/choose suggest new payment methods] via GitHub.

==== How does Bisq handle fiat (USD, EUR, etc.)? ====

Bisq '''never''' touches or holds fiat currency. Fiat payments are transferred directly between the buyer and seller using their agreed-upon external payment service (e.g., bank transfer, Zelle). Bisq's role is to provide the secure environment (escrow, deposits) and process for peers to coordinate this external transfer safely.

==== How long does a trade take? ====

Trade times vary greatly depending on the chosen payment method and trader responsiveness.
* Bisq requires the initial deposit transaction to confirm (usually ~10 minutes) before the buyer can send payment.
* Some [[Payment methods]] are near-instant (SEPA Instant, Faster Payments), allowing trades to complete quickly after the deposit confirms.
* Others take days (SEPA, Wire Transfers, ACH).
* Altcoin trades are typically faster (1 day or 1 hour for Instant).
Check the [[Payment methods]] page for the maximum trading period allowed for each method. Manual confirmation by both parties is always required.

==== How does Bisq protect my privacy? ====

* Bisq is standalone software, not a website logging your activity.
* Payment information is stored locally and only shared with your direct trading peer (and potentially dispute resolution agents if needed).
* All P2P network communication uses [[Tor]] for IP address anonymization.
* All data exchanged between users is end-to-end encrypted.
* No registration or KYC is required.

==== Do I need to keep Bisq online for my offers? ====

Yes. Since there are no central servers, your Bisq application must be running and online for your offers to be visible and available for others to take. If Bisq goes offline, your offers are removed from the distributed offer book but are automatically republished the next time you start Bisq. Once a trade *starts*, continuous connection isn't required, but you must come online periodically to perform necessary actions (send payment, confirm receipt).

==== Do I have to use the built-in Bisq wallet? ====

No. While convenient for holding trading funds (BTC, BSQ) and security deposits, you can choose to send funds *from* or receive funds *to* an external wallet address when initiating or completing trades.

==== Do I have to use the BSQ token? ====

No, using [[Introduction to the DAO|BSQ]] is optional. You can pay [[Trading fees]] in BTC. However, using BSQ provides a significant discount (around 50%) on trading fees and directly supports Bisq contributors through the [[Introduction_to_the_DAO|DAO]] mechanism.

==== Will my bank know I'm trading bitcoin? ====

Bisq itself doesn't interact with your bank. However, your trading peer will see your name associated with the payment. Some banks have been known to flag accounts involved in peer-to-peer crypto trading. To minimize potential issues:
* '''Never''' put Bitcoin-related terms ("BTC", "Bisq", etc.) in payment references/memos.
* Leave the reference field '''blank''' if possible.
* If a reference is required, use something neutral and innocuous, or just your name. Agree with your peer via [[Dispute_Resolution_in_Bisq_1|trader chat]] if unsure.
See [[Trading rules]] for details.

== Common Technical Niggles ==

{{Admonition_Note| If you encounter persistent issues, please seek help in the `#support` room on [https://bisq.chat Matrix] or open an issue on [https://github.com/bisq-network/bisq GitHub].}}

=== Startup / Connection Issues ===

==== Bisq on macOS won't open, or asks for keystroke recording permission! ====
* If it won't open, try right-clicking the app icon and selecting `Open`.
* The keystroke permission prompt is a known issue related to older Java versions sometimes bundled; Bisq does '''not''' record keystrokes. See [https://github.com/bisq-network/bisq/issues/3373 GitHub issue 3373] for historical context. Ensure you are using a recent Bisq version.

==== Bisq seems slow or uses high CPU/memory on startup. ====
This is often caused by Bisq synchronizing blockchain data (SPV sync). While newer releases include recent data to speed this up, it can still take time, especially if you haven't run Bisq recently. Let it finish syncing; performance should normalize afterwards. If issues persist on a current version, check [[Reducing_memory_usage]] or seek support.

==== On Linux with a high-resolution display, everything is tiny! ====
See [[Running_on_HiDPI_screen]] for solutions.

==== "Payment started" button won't stick / asks to send confirmation again. ====
This is a known issue related to P2P network conditions, often when the peer is offline. Try these steps:
* Send a message in [[Dispute_Resolution_in_Bisq_1|trader chat]].
* Click the "Payment started" button multiple times.
* Restart Bisq.
* Try `Settings` > `Network Info` > `Open Tor Settings` > `Delete Outdated Tor Files And Shutdown`, then restart Bisq.
* Wait while staying online (it sometimes resolves itself).
* If the trade period is ending, open mediation (`Ctrl+O` / `Cmd+O` on the trade) and explain the issue to the [[Mediator]], potentially providing screenshots.

=== Wallet / Sync Issues ===

==== "Offer cannot be taken due to counterparty trade restrictions". What does this mean? ====
This usually means information about the offer maker's account limits (based on age/signing status) hasn't fully propagated across the P2P network to your Bisq instance yet. Try restarting Bisq. The offer maker might also need to restart their Bisq client.

==== My SPV resync is taking forever or freezing! ====
This can happen with older wallets or wallets with many transactions.
* If it stalls, close and restart Bisq to resume the sync.
* Syncing is much faster if you [[Connecting_to_your_own_Bitcoin_node|connect Bisq to your own local Bitcoin full node]].
* After a very long resync completes, consider [[#How_can_I_get_a_fresh_Bisq_wallet_and_transfer_my_BSQ_balance_to_it.3F|switching to a fresh wallet]] to prevent future issues.

==== How can I get a fresh Bisq wallet and transfer my BSQ balance to it? ====
This involves carefully renaming directories while Bisq is '''closed'''. The wallet is in `btc_mainnet/wallet` inside your [[Data_directory]].
1. Ensure you have some BTC in your current wallet for transaction fees.
2. Close Bisq. Rename the `wallet` directory to `oldWallet`.
3. Start Bisq. It will create a new, empty `wallet` directory. Immediately go to `Account` > `Wallet Seed`, write down the new seed phrase securely offline, and note down your new BTC and BSQ receiving addresses.
4. Close Bisq. Rename the new `wallet` directory to `newWallet`. Rename `oldWallet` back to `wallet`.
5. Start Bisq (loading your original wallet). Send your BSQ and BTC funds to the new receiving addresses you saved in step 3.
6. Close Bisq. Rename `wallet` to `oldWallet` (or delete it if funds are confirmed sent and old seed backed up). Rename `newWallet` to `wallet`.
7. Start Bisq. You should see your funds in the fresh wallet.

=== DAO Sync Issues ===

==== "heightOfLastBlock must match chainHeight" error on startup ====
This indicates a DAO state mismatch. Try this fix:
1. Make a [[Backing up application data|backup]] of your data directory.
2. Close Bisq.
3. Navigate to your [[Data_directory]]. Delete the `DaoStateStore` directory and the `BsqBlocks` directory (usually found within `btc_mainnet/db/`).
4. Restart Bisq. It will resync the DAO state.
5. The resync should complete with in 10 minutes. To see the progress go to DAO > BSQ Wallet > Transactions. There is a status indicator at the bottom of the screen.

==== "Cannot take offer because snapshot height does not match..." error ====
This means your local DAO state is out of sync with your peer.
1. Try going to `Settings` > `Preferences` and click "Rebuild DAO state from resources".
2. Restart Bisq when prompted. Let the DAO sync fully (watch for "Synchronizing DAO" message at the bottom to disappear).
3. The resync should complete with in 10 minutes. To see the progress go to DAO > BSQ Wallet > Transactions. There is a status indicator at the bottom of the screen.
4. Try taking the offer again. If the error persists, the other trader likely needs to resync their DAO state.

=== Installation / Environment Issues ===

==== I want to install Bisq on a VPS or headless system. ====
Bisq requires a graphical desktop environment. Some users report success using tools like [https://www.xpra.org Xpra] to forward the GUI, but this is an advanced setup and not officially supported.

==== I receive a `Java heap space` error on Linux. ====
You may need to increase the memory allocated to Bisq. Edit the launch configuration file (often `/opt/bisq/lib/app/Bisq.cfg` or similar) and increase the value in `java-options=-XX:MaxRAM=Xg` (e.g., change `8g` to `16g` if you have sufficient RAM).

== Dispute resolution ==

==== How does dispute resolution work? ====

Bisq uses a 3-layer system: [[Dispute_Resolution_in_Bisq_1#Level_1:_Trader_chat|Trader chat]], [[Dispute_Resolution_in_Bisq_1#Level_2:_Mediation|Mediation]], and [[Arbitration]]. Most issues can be resolved directly via chat. If not, a [[Mediator]] can be called (Ctrl+O / Cmd+O on the trade) to propose a resolution based on [[Trading rules]]. [[Arbitration]] is a rare final step if mediation fails. (Note: The arbitrator role changed significantly in v1.2). See [[Dispute_Resolution_in_Bisq_1]] for full details.

==== How is collusion between mediators, arbitrators, and traders prevented? ====

Since Bisq v1.2, trade funds are held in 2-of-2 multisig addresses controlled *only* by the two traders. Mediators and arbitrators do *not* hold a key and cannot unilaterally release funds, preventing collusion risk involving escrow control. They are still bonded roles within the [[Introduction_to_the_DAO|DAO]] to ensure they act fairly and responsibly when investigating and proposing resolutions.

==== What happens if the buyer does a chargeback after BTC is released? ====

Bisq cannot reverse fiat chargebacks made through external banking systems. If a chargeback occurs after the trade is complete and BTC is released, the seller generally has no recourse *within Bisq*. This risk is why Bisq avoids easily reversible payment methods and uses [[Account_limits|account aging]] and [[Account_limits#Account_signing|account signing]] (in v1) to vet traders using riskier methods. Payment methods frequently used for chargebacks may be removed from Bisq.

==== Wouldn't a pure reputation system be better than dispute resolution? ====

Pure reputation systems are vulnerable to [https://en.wikipedia.org/wiki/Sybil_attack Sybil attacks] (creating fake identities) and [https://en.wikipedia.org/wiki/Confidence_trick long con] attacks. They can also compromise privacy (tying reputation to identity) and decentralization (requiring central storage). Bisq's model combines protocol incentives (like [[Security deposit|security deposits]] in v1 or [[Reputation]] in Bisq Easy) with human-based [[Dispute_Resolution_in_Bisq_1|dispute resolution]] for robustness.

==== How can I contact my trading peer? ====

Use the built-in, end-to-end encrypted [[Dispute_Resolution_in_Bisq_1#Level_1:_Trader_chat|trader chat]] available within the trade screen in the Bisq application. Avoid external communication methods.

== DAO ==

==== What is the Bisq DAO? ====

The Bisq DAO (Decentralized Autonomous Organization) is how the Bisq project governs itself and funds its development without relying on a traditional company structure. It's built on Bitcoin and ensures the project remains decentralized and censorship-resistant, aligning governance with the software's principles. Read the [[Introduction_to_the_DAO]].

==== How does the Bisq DAO work? ====

It primarily handles funding and strategy:
1. '''Funding:''' [[Trading fees]] paid by users (especially when paid in [[Introduction_to_the_DAO|BSQ]], Bisq's native token) are distributed to contributors whose work is approved by DAO voting.
2. '''Strategy:''' Project direction, parameter changes, and other decisions are made collectively through proposals and voting by BSQ stakeholders within the Bisq application.
Learn more in the [[Decentralized_autonomous_organization|DAO documentation]]. (Note: Previous specific video links were outdated/broken).

==== What do I need to know about the DAO as a trader? ====

Participation is '''optional'''. You don't need BSQ or DAO interaction to trade. However, using BSQ to pay [[Trading fees]] gives you a significant discount (~50%) and directly funds project contributors. When you buy BSQ, you typically buy it from a contributor; when you pay fees with BSQ, it's 'burned' (destroyed). [[Introduction_to_the_DAO#Overview|See more on this cycle here]].

==== Is BSQ just for fundraising? What's its issuance? ====

No, the DAO/BSQ system is primarily for decentralized '''distribution''' of existing trading fee revenue to contributors, not for initial fundraising. BSQ is 'issued' (created by coloring bitcoin) only when a contributor's compensation request is approved by DAO vote. It's 'destroyed' when used for fees. There's no pre-mine or fixed issuance schedule like many other tokens.

==== Can I use Bisq without BSQ and the DAO? ====

You can pay [[Trading fees]] with BTC instead of BSQ. However, since Bisq version 1.9.8, the DAO components are always active in the background as they are integral to how contributor roles and network parameters are managed. Using the DAO/BSQ provides benefits (lower fees) and supports the project's decentralized funding model, which avoids reliance on centralized wallets. Learn more about the DAO [[Decentralized_autonomous_organization|here]]. (Note: Previous specific video/blog links may be outdated).

== Other ==

==== This project is cool! How can I help out? ====

Check out the [[Contributor_checklist|Contributor Checklist]]! Help is welcome in many areas, from development and design to translation, support, and market bootstrapping.

==== I have a question that isn’t covered here...? ====

Please reach out to the community! Good places include:
* [https://bisq.chat Bisq Matrix] (especially the `#support` or relevant rooms)
* [https://bisq.network/contact Other community channels] listed on the website (Forum, Reddit, etc.)

Payment methods

2026-05-29T16:26:50Z

SuddenWhipVapor: updated limits

<languages/>
<translate>Bisq offers several '''payment methods''' to buy and sell bitcoin for fiat currencies or other cryptocurrencies.

{{Admonition_Note|'''Version Context:''' The details on this page, particularly regarding trade limits and account signing, primarily apply to trading on '''[[Bisq 1|Bisq v1]]'''.}}

Every offer on Bisq designates a payment method for traders to settle payments. The Bisq software does not actually integrate with any payment methods—'''all non-bitcoin fund transfers are made outside of Bisq software'''.

Unlike cryptocurrency transfers, many fiat payment transfers have limitations that require Bisq [[Bisq 1|v1]] to employ special measures like lower per-trade limits and [[Account_limits#Account_signing|account signing]] to encourage fair trades.

__TOC__

== Fiat payment methods ==

Fiat payment methods vary significantly in characteristics like chargeback risk, regional availability, transaction limits, fees, privacy, and verification speed. The primary consideration for supporting a method on Bisq is '''chargeback risk'''. Methods with easy chargebacks (like PayPal, Venmo, Cash App) are generally not supported.

Suggestions for new payment methods, especially those enabling new markets, are welcome. See the criteria and process for adding methods [https://github.com/bisq-network/growth/issues/new?assignees=&labels=re%3Apayment-method&template=add_payment_method.md&title= here on GitHub], or discuss them on [https://bisq.chat Matrix] in the #payment-methods channel.

Below is a list of fiat payment methods currently supported in Bisq v1.

'''Note on Signing Requirement:''' Methods marked with an asterisk (*) '''do not''' require [[Account_limits#Account_signing|account signing]] to lift the initial low buying limit. All other listed fiat methods generally require signing.

'''Note on Trade Limits:''' The maximum trade sizes listed below may not be available immediately for new payment accounts. Please refer to [[Account_limits]] for details on account aging and signing required to enable larger trade sizes.

{| class="wikitable sortable"
|+ Supported Fiat Payment Methods (Bisq v1)
|-
! Payment Method [* = Signing Not Required] !! Region !! Trading Period !! Per-Trade Limit (BTC) !! Notes
|-
| [[ACH]]* || USA || 5 days || 0.0624 ||
|-
| Advanced Cash* || Global (BRL, EUR, GBP, KZT, RUB, UAH, USD) || 1 day || 0.5 || Not available in the USA.
|-
| Alipay* || China || 1 day || 0.1252 ||
|-
| [[Amazon_eGift_card|Amazon eGift Card]]* || Global (AUD, CAD, EUR, GBP, INR, JPY, SAR, SEK, SGD, TRY, USD) || 1 day || 0.0624 || Check supported markets in [[Amazon_eGift_card|article]].
|-
| Australian PayID* || Australia || 1 day || 0.1252 ||
|-
| [[Bizum]]* || Spain|| 1 day || 0.02 || Bizum limits: ~1000 EUR/trade, ~2000 EUR/day.
|-
| [[Capitual]]* || Global (BRL, EUR, GBP, USD) || 1 day || 0.0624 ||
|-
| [[Cash by Mail]]* || Global || 8 days || 0.0624 || Follow [[Cash_by_Mail|instructions carefully]].
|-
| Cash Deposit* || Global || 4 days || 0.0624 || Check if payee bank allows 3rd party deposits.
|-
| [[CelPay]]* || Global (AUD, CAD, GBP, HKD, USD) || 1 day || 0.0624 || CelPay limit: ~$2,500/day.
|-
| Domestic Wire Transfer* || USA || 3 days || 0.0624 ||
|-
| [[Face-to-face_(payment_method)|Face-to-Face (F2F)]]* || Global || 4 days || 0.25 || See [[Face-to-face_(payment_method)|F2F article]] for guidance.
|-
| [[Faster Payments]]* || UK || 1 day || 0.0624 || See [[Faster_Payments|article]] for usage notes.
|-
| [[Faster_Payments_System_SBP|Faster Payments System (SBP)]]* || Russia || 1 day || 0.05 ||
|-
| HalCash* || Spain || 1 day || 0.25 ||
|-
| [[IMPS]]* || India || 1 day || 0.0624 || IMPS limit: ~1,000,000 INR/day.
|-
| Interac-e-Transfer || Canada || 1 day || 0.0624 || Interac Autodeposit is '''not''' supported.
|-
| Japan Zengin Furikomi* || Japan || 1 day || 0.25 ||
|-
| MercadoPago || Argentina || 1 day || 0.0624 ||
|-
| [[Monese]]* || Europe (GBP, EUR, RON) || 1 day || 0.0624 ||
|-
| MoneyBeam (N26) || Europe || 1 day || 0.0624 ||
|-
| MoneyGram* || Global || 4 days || 0.0832 ||
|-
| National Bank Transfer || Global || 4 days || 0.0624 ||
|-
| [[Nequi]]*|| Colombia || 1 day || 0.0624 || Nequi limit: ~7,000,000 COP/month.
|-
| [[NEFT]]* || India || 1 day || 0.10 || NEFT limit: ~50,000 INR/transaction.
|-
| [[Paxum]]* || Global || 1 day || 0.0624 ||
|-
| [[Paysera]]* || Global || 1 day || 0.0624 ||
|-
| [[PayTM]]* || India || 1 day || 0.0250 || PayTM limit: ~100,000 INR/transaction.
|-
| Perfect Money* || Global || 1 day || 0.25 ||
|-
| [[Pix]]*|| Brazil || 1 day || 0.0624 ||
|-
| Popmoney || USA || 1 day || 0.0624 ||
|-
| PromptPay* || Thailand || 1 day || 0.0624 ||
|-
| [[Revolut]] || Global || 1 day || 0.0624 || See [[Revolut|article]] for usage notes.
|-
| [[RTGS]]* || India || 1 day || 0.10 || RTGS limits: Min 200,000 INR, Max 1,000,000 INR/transaction.
|-
| [[Satispay]]* || Italy || 1 day || 0.0624 ||
|-
| [[SEPA]] || Europe || 6 days || 0.0624 ||
|-
| [[SEPA Instant]] || Europe || 1 day || 0.0624 ||
|-
| [[Strike]]* || USA || 1 day || 0.0624 || Non-KYC Strike users have lower limits.
|-
| [[SWIFT]]* || Global || 7 days || 0.0832 ||
|-
| Swish* || Sweden || 1 day || 0.1252 ||
|-
| [[Tikkie]]* || The Netherlands || 1 day || 0.0250 || Tikkie limit: ~2500 EUR/24 hours.
|-
| Transfer with Same Bank || Global || 2 days || 0.0624 ||
|-
| Transfer from Specific Banks || Global || 4 days || 0.0624 ||
|-
| [[US Postal Money Order]]* || USA || 8 days || 0.0624 || USPS limits: Max 1000 USD/order, check daily limits.
|-
| Uphold || Global || 1 day || 0.0624 ||
|-
| [[UPI]]* || India || 1 day || 0.0250 || UPI limit: ~100,000 INR/transaction.
|-
| WeChat Pay* || China || 1 day || 0.0832 ||
|-
| Western Union || Global || 4 days || 0.0832 ||
|-
| [[Wise]]* || Global ('''non-USD''' trades) || 4 days || 0.0624 ||
|-
| [[Wise-USD]]* || Global ('''USD''' trades) || 4 days || 0.0624 ||
|-
| [[Zelle]] || USA || 4 days || 0.0624 || Check your bank's Zelle support & limits.
|}
=== Payment method guides ===

<gallery mode="packed" heights="150px">
File:Payment-methods-advice-eur.png|EUR payment methods overview.
File:Payment-methods-advice-usd.png|USD payment methods overview.
</gallery>

== Altcoin payment methods ==

Bisq also supports trading Bitcoin against various cryptocurrencies, like XMR, ETH, ZEC, L-BTC or LTC. A full list is available on the [https://bisq.network/markets/ Bisq Network Markets page].

Because cryptocurrency transfers are generally irreversible and fast, altcoin trades usually have higher limits (up to 0.5 BTC) available immediately, without the need for account aging or signing required for many fiat methods.

{| class="wikitable"
|+ Supported Altcoin Payment Methods (Bisq v1)
|-
! Payment Method !! Trading Period !! Per-Trade Limit (BTC)
|-
| [[Altcoins]] || 1 day || 0.5
|-
| [[Altcoins Instant]] || 1 hour || 0.5
|}

'''Warning for Instant Trades:''' Altcoins Instant trades require quick confirmation (within 1 hour). Remember to disable any open Instant offers (via `Portfolio` > `My Open Offers`) if you might be unavailable to complete the trade promptly.

See the general Account setup process within Bisq for adding altcoin accounts.

[[Category:Features]]
</translate>

Account limits

2026-05-29T16:20:14Z

SuddenWhipVapor: updated altcoin limits

Elevated '''account limits''' apply to fiat payment accounts in order to limit damage a malicious user can do while allowing honest users to start trading immediately with no KYC and utmost privacy.

Altcoin accounts can trade 0.25 BTC right away (reduced from 0.5 BTC for security reasons), but all fiat payment account types have limits lower than 0.25 BTC to match their particular risk profiles (see [[Payment_methods#Fiat_payment_methods|this table]] for details). Some payment methods with chargeback risk implement a mechanism called ''account signing'' that restricts trading activity until a trader proves their integrity to further secure against foul play.

To reduce the size of trades entering arbitration Bisq also sets new users trade limits to be 0.1 BTC. This is an additional limit to account limits but users can opt out of this limit at any time.

__TOC__

== Which payment accounts are affected ==

Only fiat payment methods are affected by elevated account limits. Altcoin accounts are only affected by the new user limits which can be opted out if necessary for allow every altcoin account to trade up to 0.25 BTC right away upon creating a payment account in Bisq.

All fiat payment methods in all markets limit total trade size depending on the payment method's risk profile (see [[Payment_methods#Fiat_payment_methods|this table]] for details).

Despite these limitations, chargebacks can still be possible for certain payment methods. Bisq reduces this risk with a mechanism called '''account signing'''.

Account signing only applies to payment accounts that meet ''both'' of the following conditions:
* used in the following markets: USD, EUR, CAD, GBP, AUD, or BRL
* is subject to chargeback risk: SEPA, SEPA Instant, Interac e-Transfer, Zelle, Revolut, Chase QuickPay, Popmoney, MoneyBeam, Uphold, and any kind of bank transfer

This means that all payment accounts that deal in currencies not listed above do ''not'' require account signing, even if they are subject to chargeback risk.

== Account aging ==

[[File:See-account-age.png|400px|thumb|See account age in the offer book.]]

Account age is no longer used to determine trade size limits for most payment methods. It is still measured, however, and you can see a payment account's age in the offer book before taking an offer, but we caution against using it as a measure of integrity. Older accounts are not ''necessarily'' safer.

'''Practically, this means that all payment methods on Bisq have full selling capability from the moment they are created.''' Selling limits no longer phase in over time.

Some payment methods implement a variation of account aging called account signing whereby limits are increased in stages over a period of 60 days after signing. More about this below.

If you're interested, details on the <code>AccountAgeWitness</code> object that enables this aging mechanism are [https://docs.bisq.network/payment-account-age-witness.html here].

== Account signing ==

[[File:Account-signing-overview.png|thumb|right|A graphical overview of account signing.]]

Account signing limits ''buying'' limits of risky fiat payment methods to {{MaxTradeSizeUnsigned}} until the trader has bought bitcoin from a seller with a signed payment account, and then gradually phases in full buying limits. Selling limits are unaffected.

In a nutshell, this is how it works:
* Payment account is created in Bisq for risky payment method
** Buying is limited to {{MaxTradeSizeUnsigned}} BTC per trade until account is signed (see how [[#How_to_get_an_account_signed|below]])
* 30 days after signing, buying limits are increased to 50% of maximum
* 60 days after signing, maximum trade size is allowed

Let's see how this works in practice by looking at an example. SEPA has a maximum trade size of 0.0624 BTC, and it requires account signing in order for to enable full trade limits.

First let's observe what happens if a new SEPA account is never signed. Notice how buying limits never increase beyond {{MaxTradeSizeUnsigned}}, but selling 0.0624 BTC is allowed from day 0.

{| class="wikitable"
! Time Since Creating SEPA Payment Account (Never Signed)
! Maximum Trade Size (Buy)
! Maximum Trade Size (Sell)
|-
| Day 0
| {{MaxTradeSizeUnsigned}}
| 0.0624 BTC
|-
| Day 30
| {{MaxTradeSizeUnsigned}}
| 0.0624 BTC
|-
| Day 60
| {{MaxTradeSizeUnsigned}}
| 0.0624 BTC
|-
| Day 90
| {{MaxTradeSizeUnsigned}}
| 0.0624 BTC
|}

If that SEPA account manages to get signed on the same day it's created, it will see its {{MaxTradeSizeUnsigned}} limit increased on Day 30. Selling limits are unaffected.

{| class="wikitable"
! Time Since Creating SEPA Payment Account
! Maximum Trade Size (Buy)
! Maximum Trade Size (Sell)
|-
| Day 0 - Account Signed
| {{MaxTradeSizeUnsigned}}
| 0.0624 BTC
|-
| Day 30
| 0.03125 BTC
| 0.0624 BTC
|-
| Day 60
| 0.0624 BTC
| 0.0624 BTC
|-
| Day 90
| 0.0624 BTC
| 0.0624 BTC
|}

But if that SEPA account isn't signed until Day 30, it won't see its limits lifted until Day 60. Again, selling limits are unaffected.

{| class="wikitable"
! Time Since Creating SEPA Payment Account
! Maximum Trade Size (Buy)
! Maximum Trade Size (Sell)
|-
| Day 0
| {{MaxTradeSizeUnsigned}}
| 0.0624 BTC
|-
| Day 30 - Account Signed
| {{MaxTradeSizeUnsigned}}
| 0.0624 BTC
|-
| Day 60
| 0.0325 BTC
| 0.0624 BTC
|-
| Day 90
| 0.0624 BTC
| 0.0624 BTC
|}

=== How to get an account signed ===

Payment accounts that require signing cannot buy more than {{MaxTradeSizeUnsigned}} until 30 days ''after'' they are signed. Accounts can be signed with the following two methods.

==== Buying BTC ====
To sign your account you have to buy BTC following these requirements:
* trade amount is greater than or equal to {{MinTradeSizeToBeSigned}} BTC and lesser than or equal to {{MaxTradeSizeUnsigned}}
* offer must be in a market that requires signing (USD, EUR, CAD, GBP, AUD, BRL)
* seller's account must have been signed for over 30 days at the time of the signing trade

Through taking an offer you can make sure that the offer fulfills the requirements to sign your account. Making an offer could not sign your account, because taker could be unable to sign your account (signed since less than 30 days, or unsigned).

The Bisq interface makes it easy to determine if an offer can help you get signed: simply '''look for buy offers with a check mark badge''':

[[File:Good-bad-signing-asks.png|600px|thumb|left|Top offer won't get you signed. Bottom offer will get you signed.]]

<div style="clear: both;"></div>

In the image above, the offer on top does not have a check mark, but the offer on the bottom does. And it's a valid size (i.e., between {{MinTradeSizeToBeSigned}} BTC and {{MaxTradeSizeUnsigned}}), so taking that offer and successfully completing the trade will result in a signed account.

You can see your payment account's limits and signing status at <code>Accounts</code> > <code>National Currency Accounts</code>. Pick an account and look toward the bottom:

[[File:Payment-account-signing-status.png|600px|thumb|left|Where to see your payment account's limits and signing status.]]

<div style="clear: both;"></div>

==== With your own signed account ====

Once you have a signed and fully matured payment account, any new payment account you create after it, that requires signing, will be self-signed as long as it uses the '''exact same name''' as your previously signed account. The payment account can be of a different type (e.g. a signed SEPA account can self-sign a SEPA Instant account), but a payment account created with a name that is even slightly different will not be self-signed.

Payment account types that don't require your full name cannot be self-signed (e.g. Revolut, which only requires an email address) and they cannot self-sign other payment accounts.

Self-signed accounts are immediately signed, but limits are not immediately lifted. This is because they have an age of 0 days, so 30 days must pass for the {{MaxTradeSizeUnsigned}} limit to be lifted, and another 30 days must pass for full trading ability to take effect (see tables above).

== Backing up and restoring payment accounts ==

Once your payment accounts have accrued age and been signed, you won't want to give them up. With [[Backing_up_application_data|proper backups]], you won't have to—payment accounts can be restored if you ever have to remove/reinstall Bisq, move to another machine, etc.

== User opt-out limits ==

To reduce trades into arbitration for new users unfamiliar with Bisq, new users have a 0.1 BTC limit by default that can be opt-out of at any time.

To access this limit go to Settings > Preferences

[[File:Trade limits.png|frameless|left|Trade limit setting in Bisq that can opted out of or changed at any time]]

Shown above is the trade limit setting in Bisq that can opted out of or edited higher or lower at any time.

If you opt of of this limit you will be given a pop up message informing you...

{{Admonition_Warn|Trading limits are set to reduce risk of costly disputes and losing funds for new users. Raise trading limits at your own risk. Every trader has their own pace, but it's recommended to complete at least 5 trades before raising trade limits.

By raising trading limits you acknowledge to be familiar with the basic use of Bisq, like [[Backing_up_application_data|backing up your data]], [[rading_rules|trading rules]], [[Dispute_resolution|dispute resolution]], [[Table_of_penalties|penalties]] and [[User_support|where to find support]].}}

Account signing limits are still applied to buy BTC with most National Account payment methods to reduce chargeback risk.

Connecting to your own Bitcoin node

2026-05-26T21:30:28Z

SuddenWhipVapor: /* Connecting to another Bitcoin node */

Bisq will '''connect to [[Installing_your_own_Bitcoin_node|your local Bitcoin node]]''' if it finds it upon starting up. This article contains the requirements for this to work correctly.

You can also specify the addresses of particular Bitcoin nodes in <code>Settings</code> > <code>Network Info</code>.

__TOC__

= General node settings =

The <code>bitcoin.conf</code> file needs to contain the following settings. You can copy and paste this block directly into your configuration file:

<pre>
server=1
prune=0
peerbloomfilters=1
</pre>

* '''server=1''': enables the block server mode
* '''prune=0''': disables the pruning of old blocks
* '''peerbloomfilters=1''': allows Bisq to run its SPV wallet

Multiple reports have been received, where any declination of the Ronin node just won't work, or will work once, only to stop working after the next reboot, requiring a restore to network provided nodes. We are not able to suggest a workaround, except involving Ronin support.

= Connecting to a local Bitcoin node =

If you're running a Bitcoin full node on the same machine as Bisq, Bisq should connect to your node on startup—it will look for Bitcoin Core or <code>bitcoind</code> running on <code>localhost</code> on port 8333.

Just make sure to not be running any other Bitcoin-based altcoin nodes (like LTC) while starting Bisq.

= Connecting to another Bitcoin node =

By default, Bisq maximizes your privacy by connecting to nodes run by trusted Bisq contributors.

If you'd like to connect to another node, you can specify its address in <code>Settings</code> > <code>Network Info</code>. Bisq will validate the address and connect to the specified node the next time it starts.

Bisq supports connecting to Bitcoin nodes with Tor v3 addresses: this is the easiest path to take, since you only have to fill in your node's onion address in settings.<br>
If your node is on your local network, connecting directly to it rather than using Tor would reduce latency by a sensible degree. In order to do this:
* make sure the node's firewall allows incoming connections on port 8333 from the local network
* have Bitcoin daemon listen to <code>0.0.0.0</code> rather than <code>127.0.0.1</code> (add this line in bitcoin.conf: <code>bind=0.0.0.0</code>)
* uncheck "Use Tor for Bitcoin network" under Settings>Network in Bisq application
* fill in your node's local network <code>ipaddress:8333</code> in "Use custom bitcoin Core nodes" field

= Troubleshooting =

If you get into a state where Bisq is unable to connect, or stuck at SPV resync on the loading screen, you can revert to a provided node as follows.

For MacOS:
<pre>
/Applications/Bisq.app/Contents/MacOs/Bisq -btcNodes=ybryiy2k4p4pery4qseap4iu2rxput2akuvpvczwvg4eyfafcdsvyqid.onion:8333 -useTorForBtc=true
</pre>

For Linux:
<pre>
/opt/bisq/bin/Bisq -btcNodes=ybryiy2k4p4pery4qseap4iu2rxput2akuvpvczwvg4eyfafcdsvyqid.onion:8333 -useTorForBtc=true
</pre>

For Windows:
<pre>
%localappdata%\Bisq\Bisq.exe -btcNodes=ybryiy2k4p4pery4qseap4iu2rxput2akuvpvczwvg4eyfafcdsvyqid.onion:8333 -useTorForBtc=true
</pre>

After Bisq successfully started and synchronized by running it with that command, you should then go to Settings > Network info, and select again "Use provided Bitcoin Core nodes".

Contributor nodes can be seen [https://github.com/bisq-network/bisq/blob/8d345000ee22350ff6d203d4dee8c52285b6d302/core/src/main/java/bisq/core/btc/nodes/BtcNodes.java#L51-L67 here in the Bisq code].

[[Running_from_the_command_line|More info on running from the command line]].

[[Command_line_options|More info on command line options]].

Arbitration

2026-05-15T19:28:17Z

SuddenWhipVapor: improved wording

'''Arbitration''' refers to the last stage of the dispute resolution process—it's what takes place in case trader chat and [[Mediation|mediation]] fail to resolve a dispute.

This page first covers the arbitration process itself, in a practical sense, so that users can be made aware of what to expect when trading. Then it covers the process in more detail, including its motivations, how all the components work together, and how the process is expected to develop in the future.

{{ArbitrationCompensationTable}}

== Process ==

Bisq's arbitration process is a thoroughly decentralized approach to handling disputes between 2 strangers on the internet: one in which no user needs to trust a third party with authority over their funds, but one in which a user can still expect a satisfactory outcome if they have followed the Bisq [[trading rules]].

Arbitration is only available when:

* one or both traders reject a [[Mediation|mediator’s]] suggested payout
* the time-locked delayed payout transaction is published

A ''time-locked delayed payout transaction'' is signed (but not published) at the beginning of the trade process. Its purpose is to allow time for traders and mediators to work out a payout using the funds in the 2-of-2 multisig escrow, and to eliminate the [[#Avoiding_Fraud|possibility of fraud]] in case they can't.

Requesting arbitration publishes this time-locked transaction, sending all funds in the multisig escrow (i.e., those of both trading peers) to the Bisq "donation addresses" (which are owned by the [[Burning Men]], Bisq contributors who burn BSQ in advance). This transaction can only be published 10 days after the deposit transaction is confirmed (for altcoin trades) and 20 days after the deposit transaction is confirmed (for fiat trades), which means arbitration is only available after this time has passed.

[[Burning Men]] burn BSQ after estimating how many BTC from trading fees and delayed payouts will be during a cycle, and a filter controlled by the DAO distributes the BTC in proportion to how many BSQ have been burned. This keeps BSQ supply balanced, allowing for a corresponding amount of new BSQ to be issued to account for the BTC payouts made to traders as part of arbitration. As a result, BSQ supply is largely unaffected.

This dynamic essentially enables a sort of mutually assured destruction to drive dispute resolution on Bisq without trusted third parties.

'''In plain language, here's how the process works for traders:'''

# If you’re dissatisfied with the mediator’s suggestion and think you are entitled to a better outcome, request arbitration when it's available (doing so publishes the time-locked transaction and sends funds to the donation addresses owned by the BurningMen).
# Collaborate with an arbitrator to clarify the details of your case.
# If the arbitrator agrees you are owed BTC, they will pay it to you.
# The arbitrator will then request reimbursement from the Bisq DAO so they are not out of pocket.

Takeaway: if you are owed BTC after a dispute, you'll get it from an arbitrator who will refund you with their own funds. The arbitrator then requests reimbursement from the Bisq DAO usually once per DAO cycle and asks for the BSQ amount as a reimbursement for the BTC they have refunded Bisq traders. .

== Process, In Detail ==

To better understand arbitration, we need to first understand the new trade protocol, and how it improves upon the old trade protocol.

=== Pre v1.2 Trade Protocol ===

The previous model with 2-of-3 multisig deposit transactions (where an arbitrator was the 3rd key holder, and makes the payout to one of the traders in dispute cases) carried a significant risk: if the arbitrator was malicious (or was hacked), he could have taken all offers with a sockpuppet trader and made the payouts right back to his own sockpuppet.

This risk made it impossible to scale dispute resolution and find more arbitrators—we were limited to filling the role with a tiny number of Bisq contributors who could be 100% trusted to not be malicious and who had a good enough background in computer security to make getting hacked highly unlikely.

This element was the single most problematic element in Bisq’s old trade protocol, but since there weren’t any better solutions, we used it for as long as we had to.

=== Post 1.2 Trade Protocol ===

The new trade protocol, launched in [https://github.com/bisq-network/bisq/releases/tag/v1.2.0 Bisq v1.2], eliminates the risks described above to a large extent by separating functions and involving the DAO. It significantly improves censorship-resistance, security, and scalability of dispute resolution on Bisq.

[[File:Ntp-v12.png|thumb|right|Dispute resolution for trade protocol (v1.2+).]]

The basic change is that it uses a 2-of-2 multisig in the deposit transaction with only the traders’ keys.

On the happy path, the traders each sign the payout tx once the fiat or altcoin is transferred.

If anything goes wrong, there are 3 stages to resolve the issue:

# The traders can have a direct chat where they can try to find a solution to their problem.
# If that does not succeed either trader can open a mediation ticket and request help from a mediator. Mediators play a role similar to that of arbitrators in the old model, except they don’t have a 3rd key. They only can make a ''suggestion'' for the payout distribution, which either trader is free to accept or reject. If both traders accept, they create and sign the payout tx and the trade is completed. If either trader rejects, the dispute goes to stage 3. This escalation can only take place after a certain time period has passed. For altcoins, this period is 10 days, and for fiat it’s 20 days.
# An arbitrator will investigate the case, just like a mediator would, and decide how a payout should be distributed. The arbitrator role currently has 2 parts: supreme mediator and refund agent (this is where the term ''refund agent'' comes from, but ''arbitrator'' is a better term for the role, as we will soon see). The supreme mediator part of the role is similar in function to that of a regular mediator (i.e., investigate a dispute). The refund agent reimburses traders BTC for disputed trades without requiring them to undergo the complex and time-consuming process of making a reimbursement request in the DAO. The ultimate goal, however, is to make such extreme dispute cases so ''rare'' that requiring users to request reimbursement from the DAO on their own becomes feasible (e.g., by reducing bugs, UX improvements, increasing security deposits, etc). But we’re not there yet, so for now, an arbitrator simply decides on a payout ''and'' funds this payout from their own pocket, and later makes a reimbursement request to the DAO to be reimbursed for their reimbursement to the user. To avoid [[#Avoiding_Fraud|potential fraud]], and to keep the DAO from losing money in each arbitration case, we use the [[#Donation_Address|donation address]] to receive the funds from the trade via the time-locked delayed payout payout tx.

=== Time-Locked Delayed Payout Payout Transaction ===
Since [https://github.com/bisq-network/bisq/releases/tag/v1.9.8 v1.9.8], traders create a time-locked delayed payout payout tx where all the locked up funds (trade amount + both [[security deposit|security deposits]]) are sent to Bisq donation address owners, also known as burningmen. These addresses are defined in the DAO. The burningmen are Bisq contributors who burn their BSQ in order to get a portion of time-locked delayed payouts and trading fees paid in BTC.
From v1.2 to v1.9.8, this address was controlled by a single burningman who exchanged BTC for BSQ to burn them afterwards. That supposed a risk for the DAO as, although the burningman had to place a BSQ bond, the amount of the bond was lower than the amount of expected BTC to collect. Distributing the role into multiple burningman and requiring them to burn BSQ in advance, this risk has significantly decreased.

If a trade is not completed in 10 days (for altcoins) or 20 days (for fiat), either of the 2 traders have a chance (after mediation) to publish the time-locked payout tx where all deposit funds are sent to the donation address, requiring the aggrieved trader to request arbitration so they can receive a payout. With the preliminary solution we use now, the trader gets a payout from an arbitrator directly, '''but the eventual goal is that the arbitrator makes a suggestion which the DAO uses as a basis for voting on the reimbursement request made by the trader(s)'''.

=== Avoiding Fraud ===

The time-locked delayed payout payout tx is essential to avoid fraud. A trader could make a self-trade and then claim that his “peer” has not paid. Without the time-locked payout tx, he could go through the dispute process, make a reimbursement request, and receive BSQ for the equivalent “lost” funds in BTC. After that he could make the payout to himself from the trade, since he controls both “traders”—thereby scamming the DAO with the trade amount.

To avoid this fraud, we require that locked up funds in the 2-of-2 multisig deposit tx are spent before opening an arbitration ticket. Thus it is not possible for a trader to defraud the DAO in the way described above.

=== Donation Address Owners (burningmen) ===

Burningmen are current and past contributors who earned BSQ by contributing to Bisq who opt to to burn their BSQ to get BTC from time-locked delayed payout transactions and trading fees paid in BTC. A DAO filter distributes the BTC in proportion to their relative amount of BSQ burned. The amount of BSQ to be burned is limited for each contributor, to prevent that a single burningman could create self trades and take advantage from being refunded at arbitration and receiving BTC from the DAO filter as well. In order to keep this system safe, it is required that refund agent does not reimburse a security deposit from deposit transaction.
The amount of BSQ to be burned (burn target) is estimated from accumulated reimbursement requests, trade fees paid in BTC and burned BSQ from burningmen in the last 12 months.
The BSQ burned and BTC sent to burningmen should balance over time. Each one of the burningmen, according to their prefferences, could try to "charge" a discount rate for the risk assumed advancing their BSQ to the DAO by burning less than the burning target, or they could try to "pay" to avoid selling big volumes of BSQ to a low liquid market by overburning (up to 100.000 BSQ over the burning target). They could also under or overestimate the amount of BTC to be received over the next year, which is the period that burned amounts decay linearly: the burn target is an estimation with data from the past.
DAO contributors have another way to turn BSQ into BTC while contributing to remove the legacy burningman, which was a central point of failure for the Bisq DAO and created distorsion as a big BSQ buyer. Some burningmen will require to buy BSQ to be burned eventually. The impact for the market will be reduced as there will be multiple interested parties.

Let’s walk through a simplified example:

* Two traders enter into a 1 BTC trade.
* Each trader locks 0.15 BTC as a security deposit.
* In total, 1.3 BTC is locked in the 2-of-2 multisig deposit transaction (ignoring mining fees).
* Assume the BSQ/BTC exchange rate is 0.0001 BTC per BSQ for simplicity.

After the required time passes and mediation is unsuccessful, one trader opens an arbitration case. At that point, the pre-signed and time-locked delayed payout transaction becomes valid and broadcasts the full 1.3 BTC to donation addresses controlled by the burningmen.

The arbitrator investigates the dispute and determines that one trader should receive a payout of 1.15 BTC. Since the locked funds have already been redirected to the burningmen, the arbitrator pre-finances the reimbursement from their own wallet and sends 1.15 BTC directly to the winning trader.

Now assume there is only this single delayed payout event during the DAO cycle:

* Burningmen collectively burned 12,000 BSQ.
* They receive the 1.3 BTC according to their proportional burn shares.
* The arbitrator later submits a reimbursement request for 11,500 BSQ, corresponding to the 1.15 BTC payout they pre-financed.
* Once approved by the DAO, 11,500 BSQ is issued to the arbitrator.

In this example:

* The 0.15 BTC losing trader’s security deposit effectively subsidizes the system and offsets the reimbursement cost.
* Burningmen collectively retain a net gain of 0.1 BTC.
* The remaining value corresponds to a reduction in BSQ supply through the burn mechanism.

The arbitrator must then either burn or sell the reimbursed BSQ in order to recover BTC liquidity for future reimbursements and to reduce exchange-rate risk. Because arbitrators pre-finance payouts using their own funds, arbitration is intentionally designed to be rare and used only as a last resort.

=== Why We Cannot Merge the Arbitrator and BurningMan Roles ===

The separation of these roles is essential to keep the system flexible, censorship-resistant, and scalable.

'''Keep in mind that the current dual role of arbitrators (i.e., supreme mediator and refund agent) is not the ultimate goal'''. The refund agent part of the role should be delegated to traders once the trade process is improved to a level where such cases rarely happen. How to keep the burden for traders low, and how to compensate them for this extra work—these items are still up for discussion (e.g. the trader could get a slight bonus if he does the reimbursement himself). A preferred option is to keep trader-submitted reimbursement requests optional and still offer arbitrator-funded reimbursements for a fee. The role could even be split, such that a market of refund agents develops where each agent offers their pre-financing services at different prices. But before getting into any of these discussions, we need to reduce bugs and improve UX.

The role of the burningman has been distributed between different contributors and a part of their earnings come directly as BTC, but it could also disappear when we have very few dispute cases, and once trade fees in BTC do not add up to a large amount. We could use the donation address to support critical infrastructure we use like Tor. Or we could use it to fund Bisq projects like the mobile wallet. There are many possibilities for how we could use these funds—but if we merged the burningman role with the arbitrator role, we would lose this flexibility.

The risks of the 2 roles are very different. An arbitrator does not present any severe risk to the DAO, actually, he ''takes on'' a lot of risk. A single burningman, on the other hand, is a trusted role and there is an open problem that a malicious burningman could make many trades, go to the arbitrator, get payouts, and then run away with the funds he received from the donation address. The high bond is a partial protection, but ultimately, this is a trusted role and only highly trusted Bisq contributors can take it on. This problem has been mitigated by distributing the role between different contributors with a cap on how much BTC they can get. So scalability is a small issue with the distributed burningmen, but we cannot say the same about the arbitrator. With more traders, there will be more cases, and we might need more arbitrators. Furthermore, with more regional expansion, we will need arbitrators with particular language skills. When arbitrators and burningmen are not combined into one role, we can add arbitrators to support this growth without posing high risk to the Bisq network. If we merged both roles, we would not be able to do this. There is a risk arbitrators expose to the DAO: they could fake their reporting, but this is likely solvable (traders can provide evidence).

Another important aspect is that arbitrator reimbursement is not automated. DAO stakeholders have ultimate power. Sure, they would probably lose an arbitrator if they don’t reimburse him fairly, and it might be hard to find new arbitrators after unfair behaviour from DAO stakeholders. But it is highly important that stakeholders be able to exercise absolute power.

Another consideration: if the process to reimburse arbitrators were automated, the result would probably involve legal risks that we want to avoid. The role would then adopt elements of a custodial function, and that would likely trigger regulatory issues.

=== FAQ ===

'''What are the conditions that lead to a payout, for example, a dispute between Bob and Alice that is not resolved by normal mediation and gets escalated to arbitration?'''

After the time-lock period (10 days for altcoins and 20 days for fiat), and after mediation is completed, either trader can open an arbitration ticket. Doing so publishes the time-locked delayed payout transaction.

'''How are Bob and Alice's BTC funds paid out to the Bisq donation addresses?'''

The time-locked payout transaction is created and signed in the take-offer process and stored by both traders. The trade protocol requires this transaction to be in place before a trade is started.

'''How is the arbitrator responsible for deciding what the payout distribution should be? Are facts and circumstances of the case taken into account? And how is this similar to legacy arbitration?'''

In terms of determining what a payout should be, an arbitrator's role is the same as that of a mediator. They'll ask you for any additional information they need to determine the facts and circumstances of the case. The only practical difference between arbitration and legacy arbitration is that arbitrators use their own funds to pay trader(s) instead of funds from the trading escrow.

'''How, upon deciding a payout, does an arbitrator pay the BTC to Bob and Alice?'''

Arbitrators need to have enough BTC to cover potential payouts (up to 0.5 BTC per trade) — it's a requirement for anyone seeking to hold the role. An arbitration case can only be closed once an arbitrator makes a payout. Then, at the end of the DAO cycle, they'll get reimbursed with BSQ (which they can then sell for BTC).

'''Are there any trades the arbitrator will not pay out? '''

Arbitrators will only reimburse trades in which the multisig deposit has been sent to the Bisq donation addresses. For trades requiring large reimbursements (above 0.5 BTC) they should be aware the arbitrators will only [https://github.com/bisq-network/proposals/issues/296 partially reimburse traders up to 0.5 BTC]. Should a trader require a reimbursement over 0.5 BTC they can make a reimbursement request directly to the DAO on the [https://github.com/bisq-network/support support repository].

'''How does the arbitrator issue a reimbursement request for an amount of BSQ equivalent to the amount of BTC paid out-of-pocket to settle disputes?'''

This process is a work in progress. Currently we try to reduce volatility and exposure risk by converting pre-financed BTC to BSQ as fast as possible. Once it is BSQ there is no longer any volatility risk, and the arbitrator simply sums up all pre-financed BSQ and requests reimbursement. The public result of an arbitrator's work is a reimbursement request to the Bisq DAO.

'''How does the DAO issue this BSQ to reimburse arbitrators?'''

A reimbursement request is technically the same as a compensation request. DAO stakeholders vote on an arbitrator's request. The arbitrator needs to provide solid reporting to make their request transparent to the DAO. Currently there is some trust involved, since it cannot be proven that the arbitrator is not adding fake cases. This may be solvable by collecting data from traders, but this requires more thought.

'''Doesn't this dispute resolution mechanism incentivize Bisq to have more trades go to arbitration, since disputed BTC funds are sent to the burningmen, and thereby benefit BSQ holders and themselves?'''

It's the traders who open arbitration, the DAO can't start arbitration, although it could generate bugs and be unresponsive at mediation. In this case, traders will be fully reimbursed (which will generate a loss for the DAO, as arbitrator charges for every arbitration case) if they have done enough reporting the issue and trying to get [[User_support|support]] through Matrix or Github.
Bugs and requiring arbitration is a bad user experience, so the DAO is also incentivized to keep arbitration and mediation cases at the minimum.

'''How does an arbitrator spends their newly-issued BSQ?

The arbitrator sells BSQ for BTC from the market and burns BSQ as soon as reimbursement request is paid.

'''How does the burningman burn the BSQ they earn or buy?'''

Burning is done inside the Bisq software on <code>DAO / Burning / Burningmen</code>.

'''Why not simply combine the burningman and arbitrator roles?'''

[[#Why_We_Cannot_Merge_These_Roles|See longer explanation above]]. In short: to stay flexible, to be able to implement the target vision (reimbursement done by traders themselves), to avoid legal risks, to keep the arbitrator role scalable, and to address the trust/security issue with the current burningman model.

[[Category:Processes]]

Frequently asked questions

2026-05-15T19:12:52Z

SuddenWhipVapor: /* What are trading limits? How much can I trade at once? */ max trade amount

Below is a compilation of '''frequently-asked questions (FAQ)''' about Bisq, how to use it, and how to help the project.

{{Admonition_Note|'''Version Context:''' Bisq is evolving software. While many principles here are general, specific examples regarding trade mechanics, limits, and security often refer to the classic '''[[Bisq 1|Bisq v1]]''' trading protocol unless stated otherwise. The current platform is '''[[Bisq 2]]''', which supports multiple protocols including '''[[Bisq Easy]]''' (which may have different rules, e.g., using [[Reputation]] instead of [[Security deposit|security deposits]]).}}

Feel free to ask further questions on any of Bisq's many outreach channels linked at the bottom of this page.

__TOC__

== About ==

==== How is Bisq different from other decentralized exchanges? ====

Bisq is fundamentally different: it's a peer-to-peer trading network accessed via software you run on your own hardware, not a website or centralized service. It connects you directly to other users running the software to facilitate trades. It's open-source and community-driven via a [[Decentralized autonomous organization|DAO]].

Crucially, you can trade bitcoin directly for fiat currencies (like USD, EUR) or other cryptocurrencies.

Think of it like owning your home versus renting. With Bisq, you have full control over your funds and data; with centralized services (even DEX websites), you're subject to the platform's rules and risks.

With Bisq you're always the owner:

* Bisq does '''not''' hold your bitcoin. Trading funds (in the classic v1 protocol) are held in '''2-of-2 multisignature addresses''' controlled solely by you and your trading peer.
* Bisq does '''not''' hold your national currency. Fiat transfers happen directly between traders using external payment services.
* All data travels over Bisq's secure [[P2P Network|peer-to-peer network]] built on [[Tor]]—no central servers means '''no data honeypots''' vulnerable to large-scale hacks.
* Bisq requires '''no registration or KYC''', protecting your privacy. Data about who trades with whom is not stored.
* Bisq is code, not a company, governed by its [[Decentralized autonomous organization|DAO]].

See more in the [[Introduction]].

==== Is Bisq open-source software? ====

Yes. Bisq's software is free/libre open-source licensed under the GNU Affero General Public License (AGPLv3).

You can find the [https://github.com/bisq-network/bisq source code] and [https://github.com/bisq-network/bisq/blob/master/LICENSE license] on GitHub.

==== Is Bisq safe? ====

Bisq is designed with multiple layers of security, and strong incentives encourage fair trading, making the vast majority of trades proceed smoothly.

Key security mechanisms (particularly in the classic v1 protocol) include:

* Bitcoin secured in a 2-of-2 multisignature escrow address controlled only by the traders.
* Mandatory [[Security deposit|security deposits]] from both traders, refunded upon successful completion, deterring fraud.
* A [[Dispute_Resolution_in_Bisq_1|3-tier dispute resolution system]] (trader chat, mediation, arbitration) for handling issues.

However, trading fiat currencies always carries some inherent '''chargeback risk''', as banks can sometimes reverse payments. Bisq mitigates this by:

* Supporting mainly [[Payment methods|payment methods]] known to have lower chargeback risk (explicitly avoiding easily reversed methods like PayPal or credit cards).
* Employing an [[Account_limits#Account_signing|account signing mechanism]] in v1 for certain fiat methods, which limits trade sizes for new accounts until integrity is established through successful trades.

Newer protocols like [[Bisq Easy]] use different security models, such as relying on [[Reputation|seller reputation]] instead of security deposits.

== Getting started ==

==== I find Bisq very confusing initially! ====

You're not alone; some users find the interface takes getting used to, especially compared to simpler centralized exchanges.

* Check out the official [https://bisq.network/getting-started/ getting-started guide].
* Visual guides and tutorials may be available on the [https://bisq.network/ Bisk Network website] or community channels. (Note: Previous specific video links were outdated/broken).

Bisq is under continuous development, with ongoing efforts to improve the user interface and experience.

==== My currency market has few or no offers. What can I do? ====

Market liquidity varies. Some markets are very active, while others are less so, often due to the availability of suitable local payment methods or lack of initial bootstrapping.

{{Admonition_Note|An empty offer book doesn't always mean zero activity. Sometimes users are waiting for offers to appear. Try making your own offer (acting as a [[How to be a market maker on Bisq|market maker]]) - someone might take it! This is common in markets like CAD, AUD, and GBP.}}

You can check recent activity for your market via `Market` > `Trades` in the application.

To help grow a market:
* Ensure suitable local [[Payment methods]] are supported. You can [https://github.com/bisq-network/growth/issues/new/choose suggest new ones here].
* Spread the word in relevant local communities to attract both buyers/sellers and market makers. Bisq contributors can often offer support and resources for local outreach efforts.

==== Do I really need bitcoin to buy bitcoin on Bisq? How do I get started with none? ====

Yes, the classic Bisq v1 trading protocol requires a small amount of BTC for [[Security deposit|security deposits]] and [[mining fees]], creating a "chicken-and-egg" problem for complete beginners.

Here are ways to get your first small amount of BTC:
* See suggestions on the [[Funding_your_wallet#How_to_Obtain_Your_First_Bitcoin|Funding your wallet]] page (e.g., friends, Bitcoin ATMs, earning BTC).
* Visit the `Get your first BTC` room on [https://bisq.chat Matrix] to potentially arrange small, informal trades ([[Informal_Market_for_Small_BTC_Trades|details here]]).
* Use the '''[[Bisq Easy]]''' trading protocol available in [[Bisq 2]], which does '''not''' require a security deposit, making it ideal for first-time buyers.

== Trading (Classic v1 Protocol) ==

{{Admonition_Note|The following answers primarily describe the classic Bisq v1 protocol mechanics involving security deposits.}}

==== What are trading fees? ====

[[Trading fees]] are a percentage of the trade size. If paid in BTC, makers pay 0.1% and takers pay 0.7%. Fees are roughly halved if paid in BSQ tokens. Remember you also need BTC for on-chain [[mining fees]] (for deposit and payout transactions) and the [[Security deposit|security deposit]] itself (which is returned if the trade completes successfully).

==== Mining fees are high. How can I trade cost-effectively? ====

The classic protocol requires 4 on-chain transactions (3 paid by taker, 1 by maker). To minimize costs:
* Be an offer '''[[How to be a market maker on Bisq|maker]]''' rather than a taker (fewer transactions to pay for).
* Trade when network '''[[mining fees]] are lower'''.
* Make offers for '''larger BTC amounts''' (fees are fixed per transaction, less impactful on larger trades).
* '''Pay [[Trading fees|trading fees]] with BSQ''' for an approximate 50% discount.

==== Why require a security deposit in BTC? ====

[[Security deposit|Security deposits]] incentivize both parties to follow the [[Trading rules]]. They are locked in multisig escrow with the trade amount and returned upon successful completion. If rules are broken, the deposit can be partially or fully awarded to the counterparty via [[Dispute_Resolution_in_Bisq_1|dispute resolution]], deterring violations like non-payment or failing to confirm payment.

==== What are trading limits? How much can I trade at once? ====

Maximum BTC per trade varies by [[Payment methods|payment method]] based on perceived risk (especially chargeback risk). For example, methods like Zelle or SEPA often have lower limits (e.g., 0.0625 BTC) than less reversible methods. Altcoin trades generally have higher limits (0.125 BTC in v1) as chargebacks aren't possible. Check the [[Payment methods]] page for current limits per method. Also see [[Account_limits]] regarding initial limits for new accounts.

==== Which payment methods are available? ====

See the [[Payment methods]] page for the full list. You can [https://github.com/bisq-network/growth/issues/new/choose suggest new payment methods] via GitHub.

==== How does Bisq handle fiat (USD, EUR, etc.)? ====

Bisq '''never''' touches or holds fiat currency. Fiat payments are transferred directly between the buyer and seller using their agreed-upon external payment service (e.g., bank transfer, Zelle). Bisq's role is to provide the secure environment (escrow, deposits) and process for peers to coordinate this external transfer safely.

==== How long does a trade take? ====

Trade times vary greatly depending on the chosen payment method and trader responsiveness.
* Bisq requires the initial deposit transaction to confirm (usually ~10 minutes) before the buyer can send payment.
* Some [[Payment methods]] are near-instant (SEPA Instant, Faster Payments), allowing trades to complete quickly after the deposit confirms.
* Others take days (SEPA, Wire Transfers, ACH).
* Altcoin trades are typically faster (1 day or 1 hour for Instant).
Check the [[Payment methods]] page for the maximum trading period allowed for each method. Manual confirmation by both parties is always required.

==== How does Bisq protect my privacy? ====

* Bisq is standalone software, not a website logging your activity.
* Payment information is stored locally and only shared with your direct trading peer (and potentially dispute resolution agents if needed).
* All P2P network communication uses [[Tor]] for IP address anonymization.
* All data exchanged between users is end-to-end encrypted.
* No registration or KYC is required.

==== Do I need to keep Bisq online for my offers? ====

Yes. Since there are no central servers, your Bisq application must be running and online for your offers to be visible and available for others to take. If Bisq goes offline, your offers are removed from the distributed offer book but are automatically republished the next time you start Bisq. Once a trade *starts*, continuous connection isn't required, but you must come online periodically to perform necessary actions (send payment, confirm receipt).

==== Do I have to use the built-in Bisq wallet? ====

No. While convenient for holding trading funds (BTC, BSQ) and security deposits, you can choose to send funds *from* or receive funds *to* an external wallet address when initiating or completing trades.

==== Do I have to use the BSQ token? ====

No, using [[Introduction to the DAO|BSQ]] is optional. You can pay [[Trading fees]] in BTC. However, using BSQ provides a significant discount (around 50%) on trading fees and directly supports Bisq contributors through the [[Introduction_to_the_DAO|DAO]] mechanism.

==== Will my bank know I'm trading bitcoin? ====

Bisq itself doesn't interact with your bank. However, your trading peer will see your name associated with the payment. Some banks have been known to flag accounts involved in peer-to-peer crypto trading. To minimize potential issues:
* '''Never''' put Bitcoin-related terms ("BTC", "Bisq", etc.) in payment references/memos.
* Leave the reference field '''blank''' if possible.
* If a reference is required, use something neutral and innocuous, or just your name. Agree with your peer via [[Dispute_Resolution_in_Bisq_1|trader chat]] if unsure.
See [[Trading rules]] for details.

== Common Technical Niggles ==

{{Admonition_Note| If you encounter persistent issues, please seek help in the `#support` room on [https://bisq.chat Matrix] or open an issue on [https://github.com/bisq-network/bisq GitHub].}}

=== Startup / Connection Issues ===

==== Bisq on macOS won't open, or asks for keystroke recording permission! ====
* If it won't open, try right-clicking the app icon and selecting `Open`.
* The keystroke permission prompt is a known issue related to older Java versions sometimes bundled; Bisq does '''not''' record keystrokes. See [https://github.com/bisq-network/bisq/issues/3373 GitHub issue 3373] for historical context. Ensure you are using a recent Bisq version.

==== Bisq seems slow or uses high CPU/memory on startup. ====
This is often caused by Bisq synchronizing blockchain data (SPV sync). While newer releases include recent data to speed this up, it can still take time, especially if you haven't run Bisq recently. Let it finish syncing; performance should normalize afterwards. If issues persist on a current version, check [[Reducing_memory_usage]] or seek support.

==== On Linux with a high-resolution display, everything is tiny! ====
See [[Running_on_HiDPI_screen]] for solutions.

==== "Payment started" button won't stick / asks to send confirmation again. ====
This is a known issue related to P2P network conditions, often when the peer is offline. Try these steps:
* Send a message in [[Dispute_Resolution_in_Bisq_1|trader chat]].
* Click the "Payment started" button multiple times.
* Restart Bisq.
* Try `Settings` > `Network Info` > `Open Tor Settings` > `Delete Outdated Tor Files And Shutdown`, then restart Bisq.
* Wait while staying online (it sometimes resolves itself).
* If the trade period is ending, open mediation (`Ctrl+O` / `Cmd+O` on the trade) and explain the issue to the [[Mediator]], potentially providing screenshots.

=== Wallet / Sync Issues ===

==== "Offer cannot be taken due to counterparty trade restrictions". What does this mean? ====
This usually means information about the offer maker's account limits (based on age/signing status) hasn't fully propagated across the P2P network to your Bisq instance yet. Try restarting Bisq. The offer maker might also need to restart their Bisq client.

==== My SPV resync is taking forever or freezing! ====
This can happen with older wallets or wallets with many transactions.
* If it stalls, close and restart Bisq to resume the sync.
* Syncing is much faster if you [[Connecting_to_your_own_Bitcoin_node|connect Bisq to your own local Bitcoin full node]].
* After a very long resync completes, consider [[#How_can_I_get_a_fresh_Bisq_wallet_and_transfer_my_BSQ_balance_to_it.3F|switching to a fresh wallet]] to prevent future issues.

==== How can I get a fresh Bisq wallet and transfer my BSQ balance to it? ====
This involves carefully renaming directories while Bisq is '''closed'''. The wallet is in `btc_mainnet/wallet` inside your [[Data_directory]].
1. Ensure you have some BTC in your current wallet for transaction fees.
2. Close Bisq. Rename the `wallet` directory to `oldWallet`.
3. Start Bisq. It will create a new, empty `wallet` directory. Immediately go to `Account` > `Wallet Seed`, write down the new seed phrase securely offline, and note down your new BTC and BSQ receiving addresses.
4. Close Bisq. Rename the new `wallet` directory to `newWallet`. Rename `oldWallet` back to `wallet`.
5. Start Bisq (loading your original wallet). Send your BSQ and BTC funds to the new receiving addresses you saved in step 3.
6. Close Bisq. Rename `wallet` to `oldWallet` (or delete it if funds are confirmed sent and old seed backed up). Rename `newWallet` to `wallet`.
7. Start Bisq. You should see your funds in the fresh wallet.

=== DAO Sync Issues ===

==== "heightOfLastBlock must match chainHeight" error on startup ====
This indicates a DAO state mismatch. Try this fix:
1. Make a [[Backing up application data|backup]] of your data directory.
2. Close Bisq.
3. Navigate to your [[Data_directory]]. Delete the `DaoStateStore` directory and the `BsqBlocks` directory (usually found within `btc_mainnet/db/`).
4. Restart Bisq. It will resync the DAO state.
5. The resync should complete with in 10 minutes. To see the progress go to DAO > BSQ Wallet > Transactions. There is a status indicator at the bottom of the screen.

==== "Cannot take offer because snapshot height does not match..." error ====
This means your local DAO state is out of sync with your peer.
1. Try going to `Settings` > `Preferences` and click "Rebuild DAO state from resources".
2. Restart Bisq when prompted. Let the DAO sync fully (watch for "Synchronizing DAO" message at the bottom to disappear).
3. The resync should complete with in 10 minutes. To see the progress go to DAO > BSQ Wallet > Transactions. There is a status indicator at the bottom of the screen.
4. Try taking the offer again. If the error persists, the other trader likely needs to resync their DAO state.

=== Installation / Environment Issues ===

==== I want to install Bisq on a VPS or headless system. ====
Bisq requires a graphical desktop environment. Some users report success using tools like [https://www.xpra.org Xpra] to forward the GUI, but this is an advanced setup and not officially supported.

==== I receive a `Java heap space` error on Linux. ====
You may need to increase the memory allocated to Bisq. Edit the launch configuration file (often `/opt/bisq/lib/app/Bisq.cfg` or similar) and increase the value in `java-options=-XX:MaxRAM=Xg` (e.g., change `8g` to `16g` if you have sufficient RAM).

== Dispute resolution ==

==== How does dispute resolution work? ====

Bisq uses a 3-layer system: [[Dispute_Resolution_in_Bisq_1#Level_1:_Trader_chat|Trader chat]], [[Dispute_Resolution_in_Bisq_1#Level_2:_Mediation|Mediation]], and [[Arbitration]]. Most issues can be resolved directly via chat. If not, a [[Mediator]] can be called (Ctrl+O / Cmd+O on the trade) to propose a resolution based on [[Trading rules]]. [[Arbitration]] is a rare final step if mediation fails. (Note: The arbitrator role changed significantly in v1.2). See [[Dispute_Resolution_in_Bisq_1]] for full details.

==== How is collusion between mediators, arbitrators, and traders prevented? ====

Since Bisq v1.2, trade funds are held in 2-of-2 multisig addresses controlled *only* by the two traders. Mediators and arbitrators do *not* hold a key and cannot unilaterally release funds, preventing collusion risk involving escrow control. They are still bonded roles within the [[Introduction_to_the_DAO|DAO]] to ensure they act fairly and responsibly when investigating and proposing resolutions.

==== What happens if the buyer does a chargeback after BTC is released? ====

Bisq cannot reverse fiat chargebacks made through external banking systems. If a chargeback occurs after the trade is complete and BTC is released, the seller generally has no recourse *within Bisq*. This risk is why Bisq avoids easily reversible payment methods and uses [[Account_limits|account aging]] and [[Account_limits#Account_signing|account signing]] (in v1) to vet traders using riskier methods. Payment methods frequently used for chargebacks may be removed from Bisq.

==== Wouldn't a pure reputation system be better than dispute resolution? ====

Pure reputation systems are vulnerable to [https://en.wikipedia.org/wiki/Sybil_attack Sybil attacks] (creating fake identities) and [https://en.wikipedia.org/wiki/Confidence_trick long con] attacks. They can also compromise privacy (tying reputation to identity) and decentralization (requiring central storage). Bisq's model combines protocol incentives (like [[Security deposit|security deposits]] in v1 or [[Reputation]] in Bisq Easy) with human-based [[Dispute_Resolution_in_Bisq_1|dispute resolution]] for robustness.

==== How can I contact my trading peer? ====

Use the built-in, end-to-end encrypted [[Dispute_Resolution_in_Bisq_1#Level_1:_Trader_chat|trader chat]] available within the trade screen in the Bisq application. Avoid external communication methods.

== DAO ==

==== What is the Bisq DAO? ====

The Bisq DAO (Decentralized Autonomous Organization) is how the Bisq project governs itself and funds its development without relying on a traditional company structure. It's built on Bitcoin and ensures the project remains decentralized and censorship-resistant, aligning governance with the software's principles. Read the [[Introduction_to_the_DAO]].

==== How does the Bisq DAO work? ====

It primarily handles funding and strategy:
1. '''Funding:''' [[Trading fees]] paid by users (especially when paid in [[Introduction_to_the_DAO|BSQ]], Bisq's native token) are distributed to contributors whose work is approved by DAO voting.
2. '''Strategy:''' Project direction, parameter changes, and other decisions are made collectively through proposals and voting by BSQ stakeholders within the Bisq application.
Learn more in the [[Decentralized_autonomous_organization|DAO documentation]]. (Note: Previous specific video links were outdated/broken).

==== What do I need to know about the DAO as a trader? ====

Participation is '''optional'''. You don't need BSQ or DAO interaction to trade. However, using BSQ to pay [[Trading fees]] gives you a significant discount (~50%) and directly funds project contributors. When you buy BSQ, you typically buy it from a contributor; when you pay fees with BSQ, it's 'burned' (destroyed). [[Introduction_to_the_DAO#Overview|See more on this cycle here]].

==== Is BSQ just for fundraising? What's its issuance? ====

No, the DAO/BSQ system is primarily for decentralized '''distribution''' of existing trading fee revenue to contributors, not for initial fundraising. BSQ is 'issued' (created by coloring bitcoin) only when a contributor's compensation request is approved by DAO vote. It's 'destroyed' when used for fees. There's no pre-mine or fixed issuance schedule like many other tokens.

==== Can I use Bisq without BSQ and the DAO? ====

You can pay [[Trading fees]] with BTC instead of BSQ. However, since Bisq version 1.9.8, the DAO components are always active in the background as they are integral to how contributor roles and network parameters are managed. Using the DAO/BSQ provides benefits (lower fees) and supports the project's decentralized funding model, which avoids reliance on centralized wallets. Learn more about the DAO [[Decentralized_autonomous_organization|here]]. (Note: Previous specific video/blog links may be outdated).

== Other ==

==== This project is cool! How can I help out? ====

Check out the [[Contributor_checklist|Contributor Checklist]]! Help is welcome in many areas, from development and design to translation, support, and market bootstrapping.

==== I have a question that isn’t covered here...? ====

Please reach out to the community! Good places include:
* [https://bisq.chat Bisq Matrix] (especially the `#support` or relevant rooms)
* [https://bisq.network/contact Other community channels] listed on the website (Forum, Reddit, etc.)

Account limits

2026-05-15T19:07:03Z

SuddenWhipVapor: new trade amount limit set to 0.12btc

Elevated '''account limits''' apply to fiat payment accounts in order to limit damage a malicious user can do while allowing honest users to start trading immediately with no KYC and utmost privacy.

Altcoin accounts can trade 0.125 BTC right away (reduced from 0.5 BTC for security reasons), but all fiat payment account types have limits lower than 0.125 BTC to match their particular risk profiles (see [[Payment_methods#Fiat_payment_methods|this table]] for details). Some payment methods with chargeback risk implement a mechanism called ''account signing'' that restricts trading activity until a trader proves their integrity to further secure against foul play.

To reduce the size of trades entering arbitration Bisq also sets new users trade limits to be 0.1 BTC. This is an additional limit to account limits but users can opt out of this limit at any time.

__TOC__

== Which payment accounts are affected ==

Only fiat payment methods are affected by elevated account limits. Altcoin accounts are only affected by the new user limits which can be opted out if necessary for allow every altcoin account to trade up to 0.125 BTC right away upon creating a payment account in Bisq.

All fiat payment methods in all markets limit total trade size depending on the payment method's risk profile (see [[Payment_methods#Fiat_payment_methods|this table]] for details).

Despite these limitations, chargebacks can still be possible for certain payment methods. Bisq reduces this risk with a mechanism called '''account signing'''.

Account signing only applies to payment accounts that meet ''both'' of the following conditions:
* used in the following markets: USD, EUR, CAD, GBP, AUD, or BRL
* is subject to chargeback risk: SEPA, SEPA Instant, Interac e-Transfer, Zelle, Revolut, Chase QuickPay, Popmoney, MoneyBeam, Uphold, and any kind of bank transfer

This means that all payment accounts that deal in currencies not listed above do ''not'' require account signing, even if they are subject to chargeback risk.

== Account aging ==

[[File:See-account-age.png|400px|thumb|See account age in the offer book.]]

Account age is no longer used to determine trade size limits for most payment methods. It is still measured, however, and you can see a payment account's age in the offer book before taking an offer, but we caution against using it as a measure of integrity. Older accounts are not ''necessarily'' safer.

'''Practically, this means that all payment methods on Bisq have full selling capability from the moment they are created.''' Selling limits no longer phase in over time.

Some payment methods implement a variation of account aging called account signing whereby limits are increased in stages over a period of 60 days after signing. More about this below.

If you're interested, details on the <code>AccountAgeWitness</code> object that enables this aging mechanism are [https://docs.bisq.network/payment-account-age-witness.html here].

== Account signing ==

[[File:Account-signing-overview.png|thumb|right|A graphical overview of account signing.]]

Account signing limits ''buying'' limits of risky fiat payment methods to {{MaxTradeSizeUnsigned}} until the trader has bought bitcoin from a seller with a signed payment account, and then gradually phases in full buying limits. Selling limits are unaffected.

In a nutshell, this is how it works:
* Payment account is created in Bisq for risky payment method
** Buying is limited to {{MaxTradeSizeUnsigned}} BTC per trade until account is signed (see how [[#How_to_get_an_account_signed|below]])
* 30 days after signing, buying limits are increased to 50% of maximum
* 60 days after signing, maximum trade size is allowed

Let's see how this works in practice by looking at an example. SEPA has a maximum trade size of 0.0624 BTC, and it requires account signing in order for to enable full trade limits.

First let's observe what happens if a new SEPA account is never signed. Notice how buying limits never increase beyond {{MaxTradeSizeUnsigned}}, but selling 0.0624 BTC is allowed from day 0.

{| class="wikitable"
! Time Since Creating SEPA Payment Account (Never Signed)
! Maximum Trade Size (Buy)
! Maximum Trade Size (Sell)
|-
| Day 0
| {{MaxTradeSizeUnsigned}}
| 0.0624 BTC
|-
| Day 30
| {{MaxTradeSizeUnsigned}}
| 0.0624 BTC
|-
| Day 60
| {{MaxTradeSizeUnsigned}}
| 0.0624 BTC
|-
| Day 90
| {{MaxTradeSizeUnsigned}}
| 0.0624 BTC
|}

If that SEPA account manages to get signed on the same day it's created, it will see its {{MaxTradeSizeUnsigned}} limit increased on Day 30. Selling limits are unaffected.

{| class="wikitable"
! Time Since Creating SEPA Payment Account
! Maximum Trade Size (Buy)
! Maximum Trade Size (Sell)
|-
| Day 0 - Account Signed
| {{MaxTradeSizeUnsigned}}
| 0.0624 BTC
|-
| Day 30
| 0.03125 BTC
| 0.0624 BTC
|-
| Day 60
| 0.0624 BTC
| 0.0624 BTC
|-
| Day 90
| 0.0624 BTC
| 0.0624 BTC
|}

But if that SEPA account isn't signed until Day 30, it won't see its limits lifted until Day 60. Again, selling limits are unaffected.

{| class="wikitable"
! Time Since Creating SEPA Payment Account
! Maximum Trade Size (Buy)
! Maximum Trade Size (Sell)
|-
| Day 0
| {{MaxTradeSizeUnsigned}}
| 0.0624 BTC
|-
| Day 30 - Account Signed
| {{MaxTradeSizeUnsigned}}
| 0.0624 BTC
|-
| Day 60
| 0.0325 BTC
| 0.0624 BTC
|-
| Day 90
| 0.0624 BTC
| 0.0624 BTC
|}

=== How to get an account signed ===

Payment accounts that require signing cannot buy more than {{MaxTradeSizeUnsigned}} until 30 days ''after'' they are signed. Accounts can be signed with the following two methods.

==== Buying BTC ====
To sign your account you have to buy BTC following these requirements:
* trade amount is greater than or equal to {{MinTradeSizeToBeSigned}} BTC and lesser than or equal to {{MaxTradeSizeUnsigned}}
* offer must be in a market that requires signing (USD, EUR, CAD, GBP, AUD, BRL)
* seller's account must have been signed for over 30 days at the time of the signing trade

Through taking an offer you can make sure that the offer fulfills the requirements to sign your account. Making an offer could not sign your account, because taker could be unable to sign your account (signed since less than 30 days, or unsigned).

The Bisq interface makes it easy to determine if an offer can help you get signed: simply '''look for buy offers with a check mark badge''':

[[File:Good-bad-signing-asks.png|600px|thumb|left|Top offer won't get you signed. Bottom offer will get you signed.]]

<div style="clear: both;"></div>

In the image above, the offer on top does not have a check mark, but the offer on the bottom does. And it's a valid size (i.e., between {{MinTradeSizeToBeSigned}} BTC and {{MaxTradeSizeUnsigned}}), so taking that offer and successfully completing the trade will result in a signed account.

You can see your payment account's limits and signing status at <code>Accounts</code> > <code>National Currency Accounts</code>. Pick an account and look toward the bottom:

[[File:Payment-account-signing-status.png|600px|thumb|left|Where to see your payment account's limits and signing status.]]

<div style="clear: both;"></div>

==== With your own signed account ====

Once you have a signed and fully matured payment account, any new payment account you create after it, that requires signing, will be self-signed as long as it uses the '''exact same name''' as your previously signed account. The payment account can be of a different type (e.g. a signed SEPA account can self-sign a SEPA Instant account), but a payment account created with a name that is even slightly different will not be self-signed.

Payment account types that don't require your full name cannot be self-signed (e.g. Revolut, which only requires an email address) and they cannot self-sign other payment accounts.

Self-signed accounts are immediately signed, but limits are not immediately lifted. This is because they have an age of 0 days, so 30 days must pass for the {{MaxTradeSizeUnsigned}} limit to be lifted, and another 30 days must pass for full trading ability to take effect (see tables above).

== Backing up and restoring payment accounts ==

Once your payment accounts have accrued age and been signed, you won't want to give them up. With [[Backing_up_application_data|proper backups]], you won't have to—payment accounts can be restored if you ever have to remove/reinstall Bisq, move to another machine, etc.

== User opt-out limits ==

To reduce trades into arbitration for new users unfamiliar with Bisq, new users have a 0.1 BTC limit by default that can be opt-out of at any time.

To access this limit go to Settings > Preferences

[[File:Trade limits.png|frameless|left|Trade limit setting in Bisq that can opted out of or changed at any time]]

Shown above is the trade limit setting in Bisq that can opted out of or edited higher or lower at any time.

If you opt of of this limit you will be given a pop up message informing you...

{{Admonition_Warn|Trading limits are set to reduce risk of costly disputes and losing funds for new users. Raise trading limits at your own risk. Every trader has their own pace, but it's recommended to complete at least 5 trades before raising trade limits.

By raising trading limits you acknowledge to be familiar with the basic use of Bisq, like [[Backing_up_application_data|backing up your data]], [[rading_rules|trading rules]], [[Dispute_resolution|dispute resolution]], [[Table_of_penalties|penalties]] and [[User_support|where to find support]].}}

Account signing limits are still applied to buy BTC with most National Account payment methods to reduce chargeback risk.

Template:ArbitrationCompensationTable

2026-05-10T08:10:19Z

SuddenWhipVapor: further improvements

{{Admonition_Warn|All trades starting from 1st January 2023 use a new trade protocol ([[Burning Men|Burning Men Protocol]]) that is designed to further improve the decentralization of Bisq. The new protocol is a result of the proposal [https://github.com/bisq-network/proposals/issues/390 Distribute Burningman role to contributors who burned BSQ] which was voted in Bisq DAO cycle 41 with 100% approval.

The protocol change means trades placed from 1st January 2023 will be treated differently in arbitration, as a result of the accepted proposal [https://github.com/bisq-network/proposals/issues/386 do not pay out the security deposit of the trade peer to the arbitration case winner], with further improvements from [https://github.com/bisq-network/proposals/issues/411 Security deposit compensation table] that allows limited compensation under certain conditions.

If a dispute escalates to arbitration, the RefundAgent will pay out the trade amount plus one deposit and, in some cases, a limited portion of the losing user's security deposit. Previously they paid out the trade amount plus both users' security deposits. Therefore, traders in arbitration will notice the following:

* The arbitration winning party will be compensated with the trade amount, their own deposit, and, depending on the deposit %, may also receive a limited portion of the losing peer's deposit.
* The arbitration losing party may lose only part of their deposit, rather than the full amount.

This change is necessary for the security of the new protocol.

'''Arbitration should be seen as a last resort'''. All efforts should be made by traders to come to an agreement during mediation.}}

Template:ArbitrationCompensationTable

2026-05-10T08:08:48Z

SuddenWhipVapor:

{{Admonition_Warn|All trades starting from 1st January 2023 use a new trade protocol ([[Burning Men|Burning Men Protocol]]) that is designed to further improve the decentralization of Bisq. The new protocol is a result of the proposal [https://github.com/bisq-network/proposals/issues/390 Distribute Burningman role to contributors who burned BSQ] which was voted in Bisq DAO cycle 41 with 100% approval.

The protocol change means trades placed from 1st January 2023 will be treated differently in arbitration, as a result of the accepted proposal [https://github.com/bisq-network/proposals/issues/386 do not pay out the security deposit of the trade peer to the arbitration case winner], with further improvements from [https://github.com/bisq-network/proposals/issues/411 Security deposit compensation table] that allows limited compensation under certain conditions.

If a dispute escalates to arbitration, the RefundAgent will pay out the trade amount plus, in some cases, a limited portion of the losing user's security deposit. Previously they paid out the trade amount plus both user's security deposits. Therefore, traders in arbitration will notice the following:

* The arbitration winning party will be compensated with the trade amount, their own deposit, and, depending on the deposit %, may also receive a limited portion of the losing peer's deposit.
* The arbitration losing party may lose only part of their deposit, rather than the full amount.

This change is necessary for the security of the new protocol.

'''Arbitration should be seen as a last resort'''. All efforts should be made by traders to come to an agreement during mediation.}}

Template:ArbitrationCompensationTable

2026-05-10T08:08:21Z

SuddenWhipVapor: Improved wording

{{Admonition_Warn|All trades placed from 1st January 2023 will use a new trade protocol ([[Burning Men|Burning Men Protocol]]) that is designed to further improve the decentralization of Bisq. The new protocol is a result of the proposal [https://github.com/bisq-network/proposals/issues/390 Distribute Burningman role to contributors who burned BSQ] which was voted in Bisq DAO cycle 41 with 100% approval.

The protocol change means trades placed from 1st January 2023 will be treated differently in arbitration, as a result of the accepted proposal [https://github.com/bisq-network/proposals/issues/386 do not pay out the security deposit of the trade peer to the arbitration case winner], with further improvements from [https://github.com/bisq-network/proposals/issues/411 Security deposit compensation table] that allows limited compensation under certain conditions.

If a dispute escalates to arbitration, the RefundAgent will pay out the trade amount plus, in some cases, a limited portion of the losing user's security deposit. Previously they paid out the trade amount plus both user's security deposits. Therefore, traders in arbitration will notice the following:

* The arbitration winning party will be compensated with the trade amount, their own deposit, and, depending on the deposit %, may also receive a limited portion of the losing peer's deposit.
* The arbitration losing party may lose only part of their deposit, rather than the full amount.

This change is necessary for the security of the new protocol.

'''Arbitration should be seen as a last resort'''. All efforts should be made by traders to come to an agreement during mediation.}}

Arbitration

2026-05-10T07:57:00Z

SuddenWhipVapor: Deduplicate arbitration snippet

'''Arbitration''' refers to the last stage of the dispute resolution process—it's what takes place in case trader chat and [[Mediation|mediation]] fail to resolve a dispute.

This page first covers the arbitration process itself, in a practical sense, so that users can be made aware of what to expect when trading. Then it covers the process in more detail, including its motivations, how all the components work together, and how the process is expected to develop in the future.

{{ArbitrationCompensationTable}}

== Process ==

Bisq's arbitration process is a thoroughly decentralized approach to handling disputes between 2 strangers on the internet: one in which no user needs to trust a third party with authority over their funds, but one in which a user can still expect a satisfactory outcome if they have followed the Bisq [[trading rules]].

Arbitration is only available when:

* one or both traders reject a [[Mediation|mediator’s]] suggested payout
* the time-locked delayed payout transaction is published

A ''time-locked delayed payout transaction'' is signed (but not published) at the beginning of the trade process. Its purpose is to allow time for traders and mediators to work out a payout using the funds in the 2-of-2 multisig escrow, and to eliminate the [[#Avoiding_Fraud|possibility of fraud]] in case they can't.

Requesting arbitration publishes this time-locked transaction, sending all funds in the multisig escrow (i.e., those of both trading peers) to the Bisq "donation addresses" (which are owned by the [[Burning Men]], Bisq contributors who burn BSQ in advance). This transaction can only be published 10 days after the deposit transaction is confirmed (for altcoin trades) and 20 days after the deposit transaction is confirmed (for fiat trades), which means arbitration is only available after this time has passed.

[[Burning Men]] burn BSQ after estimating how many BTC from trading fees and delayed payouts will be during a cycle, and a filter controlled by the DAO distributes the BTC in proportion to how many BSQ have been burned. This keeps BSQ supply balanced, allowing for a corresponding amount of new BSQ to be issued to account for the BTC payouts made to traders as part of arbitration. As a result, BSQ supply is largely unaffected.

This dynamic essentially enables a sort of mutually assured destruction to drive dispute resolution on Bisq without trusted third parties.

'''In plain language, here's how the process works for traders:'''

# If you’re dissatisfied with the mediator’s suggestion and think you are entitled to a better outcome, request arbitration when it's available (doing so publishes the time-locked transaction and sends funds to the donation addresses owned by the Burning Men).
# Collaborate with an arbitrator to clarify the details of your case.
# If the arbitrator agrees you are owed BTC, they will pay it to you.
# The arbitrator will then request reimbursement from the Bisq DAO so they are not out of pocket.

Takeaway: if you are owed BTC after a dispute, you'll get it from an arbitrator who will refund you with their own funds. The arbitrator then requests reimbursement from the Bisq DAO usually once per DAO cycle and asks for the BSQ amount as a reimbursement for the BTC they have refunded Bisq traders. .

== Process, In Detail ==

To better understand arbitration, we need to first understand the new trade protocol, and how it improves upon the old trade protocol.

=== Pre v1.2 Trade Protocol ===

The previous model with 2-of-3 multisig deposit transactions (where an arbitrator was the 3rd key holder, and makes the payout to one of the traders in dispute cases) carried a significant risk: if the arbitrator was malicious (or was hacked), he could have taken all offers with a sockpuppet trader and made the payouts right back to his own sockpuppet.

This risk made it impossible to scale dispute resolution and find more arbitrators—we were limited to filling the role with a tiny number of Bisq contributors who could be 100% trusted to not be malicious and who had a good enough background in computer security to make getting hacked highly unlikely.

This element was the single most problematic element in Bisq’s old trade protocol, but since there weren’t any better solutions, we used it for as long as we had to.

=== Post 1.2 Trade Protocol ===

The new trade protocol, launched in [https://github.com/bisq-network/bisq/releases/tag/v1.2.0 Bisq v1.2], eliminates the risks described above to a large extent by separating functions and involving the DAO. It significantly improves censorship-resistance, security, and scalability of dispute resolution on Bisq.

[[File:Ntp-v12.png|thumb|right|Dispute resolution for trade protocol (v1.2+).]]

The basic change is that it uses a 2-of-2 multisig in the deposit transaction with only the traders’ keys.

On the happy path, the traders each sign the payout tx once the fiat or altcoin is transferred.

If anything goes wrong, there are 3 stages to resolve the issue:

# The traders can have a direct chat where they can try to find a solution to their problem.
# If that does not succeed either trader can open a mediation ticket and request help from a mediator. Mediators play a role similar to that of arbitrators in the old model, except they don’t have a 3rd key. They only can make a ''suggestion'' for the payout distribution, which either trader is free to accept or reject. If both traders accept, they create and sign the payout tx and the trade is completed. If either trader rejects, the dispute goes to stage 3. This escalation can only take place after a certain time period has passed. For altcoins, this period is 10 days, and for fiat it’s 20 days.
# An arbitrator will investigate the case, just like a mediator would, and decide how a payout should be distributed. The arbitrator role currently has 2 parts: supreme mediator and refund agent (this is where the term ''refund agent'' comes from, but ''arbitrator'' is a better term for the role, as we will soon see). The supreme mediator part of the role is similar in function to that of a regular mediator (i.e., investigate a dispute). The refund agent reimburses traders BTC for disputed trades without requiring them to undergo the complex and time-consuming process of making a reimbursement request in the DAO. The ultimate goal, however, is to make such extreme dispute cases so ''rare'' that requiring users to request reimbursement from the DAO on their own becomes feasible (e.g., by reducing bugs, UX improvements, increasing security deposits, etc). But we’re not there yet, so for now, an arbitrator simply decides on a payout ''and'' funds this payout from their own pocket, and later makes a reimbursement request to the DAO to be reimbursed for their reimbursement to the user. To avoid [[#Avoiding_Fraud|potential fraud]], and to keep the DAO from losing money in each arbitration case, we use the [[#Donation_Address|donation address]] to receive the funds from the trade via the time-locked delayed payout payout tx.

=== Time-Locked Delayed Payout Payout Transaction ===
Since [https://github.com/bisq-network/bisq/releases/tag/v1.9.8 v1.9.8], traders create a time-locked delayed payout payout tx where all the locked up funds (trade amount + both [[security deposit|security deposits]]) are sent to Bisq donation address owners, also known as burningmen. These addresses are defined in the DAO. The burningmen are Bisq contributors who burn their BSQ in order to get a portion of time-locked delayed payouts and trading fees paid in BTC.
From v1.2 to v1.9.8, this address was controlled by a single burning man who exchanged BTC for BSQ to burn them afterwards. That supposed a risk for the DAO as, although the burningman had to place a BSQ bond, the amount of the bond was lower than the amount of expected BTC to collect. Distributing the role into multiple burningman and requiring them to burn BSQ in advance, this risk has significantly decreased.

If a trade is not completed in 10 days (for altcoins) or 20 days (for fiat), either of the 2 traders have a chance (after mediation) to publish the time-locked payout tx where all deposit funds are sent to the donation address, requiring the aggrieved trader to request arbitration so they can receive a payout. With the preliminary solution we use now, the trader gets a payout from an arbitrator directly, '''but the eventual goal is that the arbitrator makes a suggestion which the DAO uses as a basis for voting on the reimbursement request made by the trader(s)'''.

=== Avoiding Fraud ===

The time-locked delayed payout payout tx is essential to avoid fraud. A trader could make a self-trade and then claim that his “peer” has not paid. Without the time-locked payout tx, he could go through the dispute process, make a reimbursement request, and receive BSQ for the equivalent “lost” funds in BTC. After that he could make the payout to himself from the trade, since he controls both “traders”—thereby scamming the DAO with the trade amount.

To avoid this fraud, we require that locked up funds in the 2-of-2 multisig deposit tx are spent before opening an arbitration ticket. Thus it is not possible for a trader to defraud the DAO in the way described above.

=== Donation Address Owners (burningmen) ===

Burningmen are current and past contributors who earned BSQ by contributing to Bisq who opt to to burn their BSQ to get BTC from time-locked delayed payout transactions and trading fees paid in BTC. A DAO filter distributes the BTC in proportion to their relative amount of BSQ burned. The amount of BSQ to be burned is limited for each contributor, to prevent that a single burningman could create self trades and take advantage from being refunded at arbitration and receiving BTC from the DAO filter as well. In order to keep this system safe, it is required that refund agent does not reimburse a security deposit from deposit transaction.
The amount of BSQ to be burned (burn target) is estimated from accumulated reimbursement requests, trade fees paid in BTC and burned BSQ from burningmen in the last 12 months.
The BSQ burned and BTC sent to burningmen should balance over time. Each one of the burningmen, according to their prefferences, could try to "charge" a discount rate for the risk assumed advancing their BSQ to the DAO by burning less than the burning target, or they could try to "pay" to avoid selling big volumes of BSQ to a low liquid market by overburning (up to 100.000 BSQ over the burning target). They could also under or overestimate the amount of BTC to be received over the next year, which is the period that burned amounts decay linearly: the burn target is an estimation with data from the past.
DAO contributors have another way to turn BSQ into BTC while contributing to remove the legacy burningman, which was a central point of failure for the Bisq DAO and created distorsion as a big BSQ buyer. Some burningmen will require to buy BSQ to be burned eventually. The impact for the market will be reduced as there will be multiple interested parties.

Let’s make a simple example to clarify:

* Two traders are engaged in a 1 BTC trade, with 0.15 BTC each locked in a security deposit
* 1.3 BTC is locked in the 2-of-2 multisig deposit tx (ignoring miner fees)
* Assume BSQ/BTC is trading at 0.0001 (for easy calculations)

After the required time passes, and the mediation process is closed, one of the traders opens an arbitration case. By doing so, the 1.3 BTC is sent to donation addresses (controlled by the burning men). This transaction was signed by both traders at the time the offer was taken, but was time-locked so it was invalid until the required time had passed. The arbitrator investigates the case and makes a 1.15 BTC payout to the winning trader. He pays this sum from his personal wallet (pre-financing).

We assume that burningmen know there will be only one delayed payout during a cycle: burningmen burned 12,000 BSQ and received the 1.3 BTC into different addresses (which generates a 0.1 BTC profit), each one receiving a % based on the amount they've burned.
The arbitrator then makes a reimbursement request of 11,500 BSQ to settle his pre-financing. When approved, the DAO issues 11,500 BSQ to the arbitrator. The 0.1 BTC profit for burningmen was subsidized with the 0.15 BTC from the unpaid security deposit. The DAO keeps the other 0.5 BTC in form of reduction in BSQ supply of 0.05 BTC.
Arbitrator will have to burn or sell the BSQ the reimbursed BSQ to get BTC for new payments and reduce volatility risk, which is taking a high risk as they pre-finance the reimbursement. Bisq tries to make arbitration rare as reimbursing traders has a big cost.

=== Why We Cannot Merge the Arbitrator and Burning Man Roles ===

The separation of these roles is essential to keep the system flexible, censorship-resistant, and scalable.

'''Keep in mind that the current dual role of arbitrators (i.e., supreme mediator and refund agent) is not the ultimate goal'''. The refund agent part of the role should be delegated to traders once the trade process is improved to a level where such cases rarely happen. How to keep the burden for traders low, and how to compensate them for this extra work—these items are still up for discussion (e.g. the trader could get a slight bonus if he does the reimbursement himself). A preferred option is to keep trader-submitted reimbursement requests optional and still offer arbitrator-funded reimbursements for a fee. The role could even be split, such that a market of refund agents develops where each agent offers their pre-financing services at different prices. But before getting into any of these discussions, we need to reduce bugs and improve UX.

The role of the burning man has been distributed between different contributors and a part of their earnings come directly as BTC, but it could also disappear when we have very few dispute cases, and once trade fees in BTC do not add up to a large amount. We could use the donation address to support critical infrastructure we use like Tor. Or we could use it to fund Bisq projects like the mobile wallet. There are many possibilities for how we could use these funds—but if we merged the burning man role with the arbitrator role, we would lose this flexibility.

The risks of the 2 roles are very different. An arbitrator does not present any severe risk to the DAO, actually, he ''takes on'' a lot of risk. A single burning man, on the other hand, is a trusted role and there is an open problem that a malicious burning man could make many trades, go to the arbitrator, get payouts, and then run away with the funds he received from the donation address. The high bond is a partial protection, but ultimately, this is a trusted role and only highly trusted Bisq contributors can take it on. This problem has been mitigated by distributing the role between different contributors with a cap on how much BTC they can get. So scalability is a small issue with the distributed burningmen, but we cannot say the same about the arbitrator. With more traders, there will be more cases, and we might need more arbitrators. Furthermore, with more regional expansion, we will need arbitrators with particular language skills. When arbitrators and burningmen are not combined into one role, we can add arbitrators to support this growth without posing high risk to the Bisq network. If we merged both roles, we would not be able to do this. There is a risk arbitrators expose to the DAO: they could fake their reporting, but this is likely solvable (traders can provide evidence).

Another important aspect is that arbitrator reimbursement is not automated. DAO stakeholders have ultimate power. Sure, they would probably lose an arbitrator if they don’t reimburse him fairly, and it might be hard to find new arbitrators after unfair behaviour from DAO stakeholders. But it is highly important that stakeholders be able to exercise absolute power.

Another consideration: if the process to reimburse arbitrators were automated, the result would probably involve legal risks that we want to avoid. The role would then adopt elements of a custodial function, and that would likely trigger regulatory issues.

=== FAQ ===

'''What are the conditions that lead to a payout, for example, a dispute between Bob and Alice that is not resolved by normal mediation and gets escalated to arbitration?'''

After the time-lock period (10 days for altcoins and 20 days for fiat), and after mediation is completed, either trader can open an arbitration ticket. Doing so publishes the time-locked delayed payout transaction.

'''How are Bob and Alice's BTC funds paid out to the Bisq donation addresses?'''

The time-locked payout transaction is created and signed in the take-offer process and stored by both traders. The trade protocol requires this transaction to be in place before a trade is started.

'''How is the arbitrator responsible for deciding what the payout distribution should be? Are facts and circumstances of the case taken into account? And how is this similar to legacy arbitration?'''

In terms of determining what a payout should be, an arbitrator's role is the same as that of a mediator. They'll ask you for any additional information they need to determine the facts and circumstances of the case. The only practical difference between arbitration and legacy arbitration is that arbitrators use their own funds to pay trader(s) instead of funds from the trading escrow.

'''How, upon deciding a payout, does an arbitrator pay the BTC to Bob and Alice?'''

Arbitrators need to have enough BTC to cover potential payouts (up to 0.5 BTC per trade) — it's a requirement for anyone seeking to hold the role. An arbitration case can only be closed once an arbitrator makes a payout. Then, at the end of the DAO cycle, they'll get reimbursed with BSQ (which they can then sell for BTC).

'''Are there any trades the arbitrator will not pay out? '''

Arbitrators will only reimburse trades in which the multisig deposit has been sent to the Bisq donation addresses. For trades requiring large reimbursements (above 0.5 BTC) they should be aware the arbitrators will only [https://github.com/bisq-network/proposals/issues/296 partially reimburse traders up to 0.5 BTC]. Should a trader require a reimbursement over 0.5 BTC they can make a reimbursement request directly to the DAO on the [https://github.com/bisq-network/support support repository].

'''How does the arbitrator issue a reimbursement request for an amount of BSQ equivalent to the amount of BTC paid out-of-pocket to settle disputes?'''

This process is a work in progress. Currently we try to reduce volatility and exposure risk by converting pre-financed BTC to BSQ as fast as possible. Once it is BSQ there is no longer any volatility risk, and the arbitrator simply sums up all pre-financed BSQ and requests reimbursement. The public result of an arbitrator's work is a reimbursement request to the Bisq DAO.

'''How does the DAO issue this BSQ to reimburse arbitrators?'''

A reimbursement request is technically the same as a compensation request. DAO stakeholders vote on an arbitrator's request. The arbitrator needs to provide solid reporting to make their request transparent to the DAO. Currently there is some trust involved, since it cannot be proven that the arbitrator is not adding fake cases. This may be solvable by collecting data from traders, but this requires more thought.

'''Doesn't this dispute resolution mechanism incentivize Bisq to have more trades go to arbitration, since disputed BTC funds are sent to the burningmen, and thereby benefit BSQ holders and themselves?'''

It's the traders who open arbitration, the DAO can't start arbitration, although it could generate bugs and be unresponsive at mediation. In this case, traders will be fully reimbursed (which will generate a loss for the DAO, as arbitrator charges for every arbitration case) if they have done enough reporting the issue and trying to get [[User_support|support]] through Matrix or Github.
Bugs and requiring arbitration is a bad user experience, so the DAO is also incentivized to keep arbitration and mediation cases at the minimum.

'''How does an arbitrator spends their newly-issued BSQ?

The arbitrator sells BSQ for BTC from the market and burns BSQ as soon as reimbursement request is paid.

'''How does the burningman burn the BSQ they earn or buy?'''

Burning is done inside the Bisq software on <code>DAO / Burning / Burningmen</code>.

'''Why not simply combine the burning man and arbitrator roles?'''

[[#Why_We_Cannot_Merge_These_Roles|See longer explanation above]]. In short: to stay flexible, to be able to implement the target vision (reimbursement done by traders themselves), to avoid legal risks, to keep the arbitrator role scalable, and to address the trust/security issue with the current burning man model.

[[Category:Processes]]

Dispute Resolution in Bisq 1

2026-05-10T07:56:18Z

SuddenWhipVapor: Deduplicate arbitration snippet

Sometimes Bisq trades don't go smoothly, and '''dispute resolution''' is required to determine an outcome.

Dispute resolution on Bisq has three formal levels: trader chat, [[Mediation|medition]], and [[Arbitration|arbitration]].

Most issues on Bisq are minor and easily resolved when traders communicate with each other. [[Mediation]] is intended to resolve the vast majority of remaining issues. [[Arbitration]] is a rare last resort measure for extreme scenarios.

__TOC__

= Level 1: Trader chat =

If you're having any issues completing a trade, or if you just want to keep your counterparty informed (e.g., in case you're delayed completing your end of the deal), you can send your counterparty a message through Bisq's end-to-end encrypted chat mechanism. This allows traders to communicate with each other throughout the course of a trade to resolve potential trade issues quickly without involving a third party like a [[Mediator|mediator]] or [[Arbitrator|arbitrator]].

[[File:Start-trader-chat.png|600px|thumb|left|Click this icon to start trader chat.]]

<div style="clear: both;"></div>

== Trader chat rules ==

Hopefully, by following these rules you can work directly with your trading peer to solve issues quickly and amicably.

=== Good Communication is Key ===

Good communication between traders can resolve most disputes. It's recommended for traders to communicate any issues they're having to keep their peer informed.

However, '''responding to chat messages is always optional'''. If you’re not comfortable responding, don’t. You have no obligation to communicate over this medium with traders. You must, however, respond to [[Mediator|mediators]] and [[Arbitrator|arbitrators]] when needed.

=== Respect a Peer’s Decision to Avoid Responding ===

If a peer seems unresponsive or has signaled their intention to refrain from chatting, please respect it and don’t pressure them.

=== Do Not Send Links of Any Kind ===

For safety reasons, sending links is prohibited. If you want to share a link, describe it instead.

''Not allowed:''

<nowiki>https://blockstream.info/tx/4b5417ec5ab6112bedf539c3b4f5a806ed539542d8b717e1c4470aa3180edce5</nowiki>

''Allowed:''

Hey, could you look up txid 4b5417ec5ab6112bedf539c3b4f5a806ed539542d8b717e1c4470aa3180edce5 in your favorite block explorer?

=== Do Not Encourage Trading Away from Bisq ===

Trades away from Bisq lack Bisq’s security mechanisms. If something goes wrong with an off-Bisq trade, you’re on your own.

=== Do Not Share Sensitive Information ===

Such information is '''never''' wise to share in general and is never needed to solve trade disputes on Bisq. This includes passwords, seed words and private keys.

=== Do Not Engage in Foul Play ===

Any attempts to exploit counterparties with social engineering scams, etc., are prohibited.

=== Keep Conversation Scope Limited to the Trade ===

Please don’t use Bisq’s trader chat as a general-purpose messenger. Unnecessary exchanges add unnecessary strain to Bisq’s peer-to-peer network.

=== Keep Conversation Friendly and Respectful ===

Because friendlier traders resolve disputes quicker, and no one wants to deal with a jerk.

= Level 2: Mediation =

If issues persist after discussing them with the counterparty, you may need to involve a [[Mediator|mediator]].

'''[[Mediation]] can be initiated at any point during or after the trade period. To do this, select the trade from the 'Open Trades' list and press 'Ctrl' + 'O'.
'''
[[File:Start-mediation.png|400px|thumb|left|Engage a mediator. This button only appears after the trade period has ended.]]

== How Mediation Works ==

[[Mediator|Mediators]] assess a trade situation between two users and propose a payout suggestion. They don't hold a key in the multisig escrow, so their proposal isn't authoritative.

=== Trading Peer Expectations ===
* Cooperate with the [[mediator]], providing requested information (quality proof will be asked for payments or bank issues)
* Respond to messages within 48 hours. Non-response might result in [[Table of penalties|penalties]].

=== Mediator Response Time ===

[[Mediator|Mediators]] may take up to 48 hours to respond. '''Please be patient'''.

=== Payout Suggestion ===
* If both peers agree, the payout is completed, and the trade is closed.
* If one or both disagree, a peer can engage an [[Arbitrator|arbitrator]] to reassess the situation (see [[#Level_3:_Arbitration|arbitration]] below).

== When are you eligible for a penalty? ==

If a trader does not follow the [[trading rules]], they risk being [[Table of penalties|penalized]]. Any [[Table of penalties|penalties]] will be taken from the trader's BTC [[security deposit]].

The trader at fault will be charged the [[Table of penalties|penalty]], and their [[security deposit]] will be deducted a BTC amount.

The trader that is wronged will receive the [[Table of penalties|BTC penalty]] as compensation. The payout transaction for the trade will include funds from the other trader's [[security deposit]].

For more information about what to expect, you can see the [[table of penalties]]. This table acts as a guideline for traders, [[Mediator|mediators]], and [[Arbitrator|arbitrators]] to ensure [[Table of penalties|penalty]] are applied in a fair and impartial way.

== Who are mediators? ==

[[Mediator]] roles are [https://docs.bisq.network/user-dao-intro.html#ensure-honesty-in-high-trust-roles bonded roles] in the [[DAO_user_reference#Bisq_DAO|Bisq DAO]]. Anyone can propose to become a [[mediator]], but approval will depend on the candidate's familiarity with Bisq [[Trading rules|trading rules]] and the network’s need for more [[mediator|mediators]] at the time a proposal is made.

Once a proposal to become a [[mediator]] is approved by [[DAO_user_reference#Voting_Cycle|DAO voting]], the [[mediator]] must lock a 10,000 BSQ bond to become active. This bond helps to ensure their continued availability and performance in the role, and can be confiscated by [[DAO_user_reference#Voting_Cycle|DAO voting]] in extreme circumstances (negligence, foul play, prolonged absence, etc).

You can see more details (current role owners, regular updates, etc) on the [https://github.com/bisq-network/roles/issues/83|mediator role issue].

== Where to communicate with mediators? ==

You can communicate with your [[mediator]] directly in the Bisq app. When you initiate a trade and open a [[mediation]], a support ticket is automatically created within the app. You can find this in the 'Support' > 'Mediation' section.

Communicating with [[Mediator|mediators]] inside the app is preferred.

In case you're unable to communicate within the Bisq app for any reason, you can also reach out to them on [[Matrix bisq.chat|Matrix]].

Find more information on [[finding your mediator|finding your mediator here]].

== How to find your mediators? ==

Your [[mediator|mediator's]] name should be visible when you open a mediation ticket. Look for it under the 'support agent' column.

If, however, you have a trade not in mediation but would like to know your assigned mediator's name, please refer to [[Finding your mediator]].

= Level 3: Arbitration =

[[File:Engage-arbitrator-v116.png|400px|thumb|left|Reject mediator's suggestion in order to start arbitration.]]
[[Arbitration]] is the final tier of dispute resolution on Bisq. It's designed to be rare, and its measures are intended for extreme situations. [[Arbitration]] is only available when:
* One or both traders reject a [[mediator|mediator's]] proposed solution.
* The [[Arbitration#Time-Locked_Payout_Transaction|time-locked transaction]] (the delayed payout transaction created at the trade's start) is published by one of the traders.

This transaction sends '''all''' funds in the multisig escrow (both traders' funds) to the [[Burning Men]].

The delayed payout transaction can only be published 10 days after the deposit transaction is confirmed for altcoin trades, or 20 days for fiat trades.

Consider this transaction as a safeguard or fallback option, to be used only when other options have failed.

{{Admonition_Warn|[[Mediation]] is expected to be the best resolution for both traders. If a trade goes to [[arbitration]], the [[arbitrator]] will pay out the trade amount plus one peer's [[security deposit]]. This means the total [[arbitration]] payout will be less than the [[mediation]] payout. Both traders agreeing to the [[mediator|mediator's]] suggestion is the preferred outcome. Requesting [[arbitration]] should be reserved for exceptional circumstances, such as one peer not responding, or if a trader believes the [[mediator]] did not make a fair payout suggestion.

This dynamic enables a form of mutually assured destruction, driving dispute resolution on Bisq without relying on trusted third parties.}}

Practically, here's how [[arbitration]] works:

# If you're trading with an unresponsive peer or feel the [[mediator|mediator's]] suggestion was unfair, publish the time-locked transaction as soon as possible and request [[arbitration]].
# Collaborate with the [[arbitrator]] to clarify your case's details.
# If the [[arbitrator]] sides with you, they will personally reimburse you.
# The [[arbitrator]] will then request reimbursement from the [[DAO_user_reference#Bisq_DAO|Bisq DAO]] for the reimbursements they've paid. This isn't something you need to worry about as a trader, but it's good to know how the process works on both sides.
# [[arbitrator|Arbitrators]] are required to respond to messages within 5 days, so it may take a bit longer for them to respond than mediators (you should still respond to messages within 2 days).

{{ArbitrationCompensationTable}}

== How to find your arbitrator ?==
Your arbitrator's name should be visible when you open a arbitration ticket. Look for it under the 'support agent' column.

If, however, you have a trade not in arbitration but would like to know your assigned arbitrator's name, please refer to [[Finding your arbitrator]].

= If all else fails =

One advantage of a flat, decentralized governance structure that encourages user involvement is that no user should ever feel hindered from receiving a fair trade outcome because of a single individual's decision. Bisq isn't a black-box corporation with inscrutable processes. It's an open software project that is governed openly.

Therefore, for whatever reason, if the process above doesn't work for you, you can make a [[Making_a_reimbursement_request|make a reimbursement request]] yourself in the [[DAO_user_reference#Bisq_DAO|Bisq DAO]]. The [[DAO_user_reference#Bisq_DAO|Bisq DAO]] '''not any single individual is the ultimate arbiter of policy and decision-making for all things Bisq'''.

In fact, this is how [[arbitration]] will eventually be handled anyway.

Arbitrator

2026-05-10T07:54:30Z

SuddenWhipVapor: Deduplicate arbitration snippet

An '''arbitrator''' resolves disputes that could not be resolved by traders on their own or with a [[Mediator|mediator]]'s help.

Arbitrators investigate disputes, just like mediators. But unlike mediators, whose suggestions encourage traders to make payouts from their own escrowed funds, an arbitrator's findings lead to a payout from the arbitrator themselves.

__TOC__

{{ArbitrationCompensationTable}}

== Role Notes ==

=== Arbitrator's Role in Dispute Resolution ===

Currently, the arbitrator makes BTC payouts to aggrieved traders out of their own pocket and gets refunded by the Bisq DAO (hence the term ''refund agent'' used sometimes). But this arrangement is intended as a convenience so that traders can avoid making a reimbursement request to the DAO on their own.

The arbitrator role is one element of Bisq's decentralized dispute resolution process. Please see more details at [[Arbitration|arbitration]].

=== Arbitrator versus Legacy Arbitrator ===

Although arbitrators have been a component of dispute resolution on Bisq since its early days, the v1.2 update wholly changed the nature of the role.

Before the update, trade funds were secured in a 2-of-3 multisig escrow, in which arbitrators held the third key. They would evaluate disputes and then sign funds to traders as they saw fit. Since these arbitrators (which we now refer to as ''legacy arbitrators'') had some element of control over users' funds, those who filled the role had to be ''very'' highly trusted.

The v1.2 update enabled trade funds to be secured in a 2-of-2 multisig escrow, in which arbitrators have '''no involvement'''. Mediators handle most disputes, but if an arbitrator does get involved, payouts either come from the arbitrator's own pocket or from the Bisq DAO. Arbitrators are still trusted to conduct their role with integrity and consistency, but this is a wholly different kind of trust, one that is unrelated to the handling of users' funds, and thus one that doesn't even require a bond.

== Issue ==
https://github.com/bisq-network/roles/issues/93

== Team ==
[https://github.com/orgs/bisq-network/teams/refund-agents @bisq-network/refund-agents]

== Duties ==
* Investigate trader disputes and determine how payout should be made (must respond to traders within 5 days)
* Do payouts to traders as appropriate with BTC
* Request BSQ reimbursement from the Bisq DAO

== Rights ==
* Write access to the <code>Support - Private</code> Matrix room

== Bonding ==
Not required.

== Finding your arbitrator ==
To find your arbitrator see [[Finding your arbitrator|here]].

[[Category:Roles]]

Template:ArbitrationCompensationTable

2026-05-10T07:53:35Z

SuddenWhipVapor: Created page with "{{Admonition_Warn|All trades placed from 1st January 2023 will use a new trade protocol (Burning Men Protocol) that is designed to further improve the decentra..."

{{Admonition_Warn|All trades placed from 1st January 2023 will use a new trade protocol ([[Burning Men|Burning Men Protocol]]) that is designed to further improve the decentralization of Bisq. The new protocol is a result of the proposal [https://github.com/bisq-network/proposals/issues/390 Distribute Burningman role to contributors who burned BSQ] which was vote on in Bisq DAO cycle 41 with 100% approval.

The protocol change means trades placed from 1st January 2023 will have an important difference should the trade end in arbitration. This is as a result of the accepted proposal [https://github.com/bisq-network/proposals/issues/386 do not pay out the security deposit of the trade peer to the arbitration case winner], with further clarification from [https://github.com/bisq-network/proposals/issues/411 Security deposit compensation table] that allows limited compensation under certain conditions.

What this means in practice is IF a trade ends in arbitration the arbitrator will pay out the trade amount plus, in some cases, a limited portion of the losing user's security deposit. Previously they paid out the trade amount plus both user's security deposits. Therefore, traders ending in arbitration will notice the following:

* The arbitration 'winner' will be compensated for the trade amount and, depending on the deposit %, may also receive a limited portion of the losing peer's deposit.
* The arbitration 'loser' may lose only part of their deposit, rather than the full amount.

This change is necessary for the security of the new protocol.

Remember arbitration should be seen as the last resort. All efforts should be made for traders to come to an agreement with themselves or via the mediator.}}

ACH Transfer

2026-04-29T22:11:19Z

SuddenWhipVapor: /* How do I buy BTC with my ACH Transfer account? */

'''ACH Transfer''', or Automated Clearing House Trasnfer, is a payment method introduced in Bisq v1.8.0. It is primarily used for domestic, low-value payments between participating financial institutions. ACH transfers are one of the two main bank transfer payment methods in the United States, the other being [[Domestic_Wire_Transfer|domestic Wire transfers]].

== What countries offer ACH Transfer? ==

ACH is only available in the United States.

== What currencies are available for ACH Transfer? ==

ACH only supports transfers of USD.

== What is the maximum trading duration for ACH Transfer? ==

The maximum trade time is 5 days, but most are completed within 2 business days. Financial institutions send ACH transfers in batches. Depending on when the transfer is initiated, it will be received the next business day, by the end of the current day, or in real time.

== What is the maximum BTC limit for ACH Transfer? ==

{{MaxTradeSizeBisq1}}.

== Is ACH Transfer a payment method that can be signed? ==

No, ACH accounts do not require signing.

== How do I set up a ACH Transfer account? ==

Please note that not all banks offer ACH transfers to third parties. It's crucial to verify if your bank supports this service. Most banks allow ACH transfers to accounts you own at other institutions. However, they may ask you to confirm three micro-deposits they initiate. This process is not the same as a third-party transfer, and Bisq sellers are instructed not to confirm these micro-deposits. Confirming micro-deposits enables your bank to send and receive money from that account, but this isn't a third-party transfer. If your bank fully supports third-party ACH transfers, they won't ask for micro-deposit verification. ACH transfers are typically provided at a low cost, so be sure to check with your bank about any fees.

== How do I add ACH Transfer as a payment method in Bisq? ==

To add your ACH account to Bisq:

# Head to the top menu and select ''Account''.
# Then, choose ''National Currency Accounts''.
# Click on ''Add new account''.
# Select ''ACH''.
# Fill in the necessary details.
# If you'd like, choose to use a custom account name. This can help you manage multiple payment methods in Bisq. It will be visible only to you, like "ACH - Chase Bank - USD - Jane Doe".
# Once done, click save new account.
# If you have more than one ACH account you wish to add to Bisq you can create different accounts for each.

Ensure all the details are accurate when you add them. Sellers can only confirm payment if the name associated with the incoming ACH transfer matches the account name listed in Bisq.

== How do I buy BTC with my ACH Transfer account? ==

You can buy BTC with ACH on Bisq in 2 ways:

# Make an offer to buy BTC on the USD market.
# Take an offer to buy BTC on the USD market.

When the offer is confirmed, Bisq will provide you with the BTC seller's ACH details for you to complete the payment. You should send the payment immediately and confirm you have done so in Bisq by clicking 'payment started'.

If you have the option to include a payment reference, please leave it blank. If your bank requires one, please just use your name that matches your bank account.

Once the BTC seller receives your payment, they will confirm in Bisq, and your security deposit and your purchased trade amount will be available in your wallet.

'''Important:''' When sending an ACH payment, ensure it is a standard ACH transfer. Some banks allow you to set up an ACH Direct Deposit, which involves sending three micropayments to your trading partner's account for verification. Do not accept '''ACH Direct Deposits for Bisq trades''' nor communicate to the buyer the amounts of the microdeposits, as a linked ACH account will be exposed to funds withdrawal by your peer.

== How do I sell BTC with my ACH Transfer account? ==

You can sell BTC with ACH on Bisq in 2 waysː

# Make an offer on the USD market to sell your BTC.
# Take an existing offer on the USD market to sell your BTC.

After the offer is confirmed, Bisq will provide the BTC Buyer with your ACH details. The Buyer should send the payment at their earliest convenience and confirm it in Bisq by clicking 'Payment Started'.

'''Important:''' When receiving an ACH payment, ensure it is a standard ACH transfer. Some banks allow the recipient to set up an ACH Direct Deposit, which involves sending two micropayments to your account for verification. '''If you receive micropayments from a buyer, do not verify them.''' Setting up ACH Direct Deposits for Bisq trades allows the buyer to debit the seller's account without further authorization.

== Are there any limits for me to be aware of when sending an ACH transfer ==

Your bank may impose limits on the amounts you can send or receive. You should check if your bank has any such limits.

== Are there any fees for me to be aware of when sending an ACH transfer? ==

Fees charged by your bank for sending an ACH transfer can vary and it's best to check with them. Fees can also be different depending on the speed of the transfer as some banks offer expedited processing.

Generally, banks will not charge for receiving ACH transfers, but again, it's best to check with your bank since some do charge.

== How does dispute resolution work with ACH transfers? ==

If a dispute occurs, the mediator may ask the buyer to send them information showing that they made the payment of the correct amount to the BTC Seller within the correct time frame. The mediator may also ask the seller to send them information to prove their account details are correct, or in the case of the BTC Buyer making a payment late, or of the wrong amount.

For more information see [[dispute resolution]].

ACH Transfer

2026-04-29T22:08:55Z

SuddenWhipVapor: /* How do I buy BTC with my ACH Transfer account? */

'''ACH Transfer''', or Automated Clearing House Trasnfer, is a payment method introduced in Bisq v1.8.0. It is primarily used for domestic, low-value payments between participating financial institutions. ACH transfers are one of the two main bank transfer payment methods in the United States, the other being [[Domestic_Wire_Transfer|domestic Wire transfers]].

== What countries offer ACH Transfer? ==

ACH is only available in the United States.

== What currencies are available for ACH Transfer? ==

ACH only supports transfers of USD.

== What is the maximum trading duration for ACH Transfer? ==

The maximum trade time is 5 days, but most are completed within 2 business days. Financial institutions send ACH transfers in batches. Depending on when the transfer is initiated, it will be received the next business day, by the end of the current day, or in real time.

== What is the maximum BTC limit for ACH Transfer? ==

{{MaxTradeSizeBisq1}}.

== Is ACH Transfer a payment method that can be signed? ==

No, ACH accounts do not require signing.

== How do I set up a ACH Transfer account? ==

Please note that not all banks offer ACH transfers to third parties. It's crucial to verify if your bank supports this service. Most banks allow ACH transfers to accounts you own at other institutions. However, they may ask you to confirm three micro-deposits they initiate. This process is not the same as a third-party transfer, and Bisq sellers are instructed not to confirm these micro-deposits. Confirming micro-deposits enables your bank to send and receive money from that account, but this isn't a third-party transfer. If your bank fully supports third-party ACH transfers, they won't ask for micro-deposit verification. ACH transfers are typically provided at a low cost, so be sure to check with your bank about any fees.

== How do I add ACH Transfer as a payment method in Bisq? ==

To add your ACH account to Bisq:

# Head to the top menu and select ''Account''.
# Then, choose ''National Currency Accounts''.
# Click on ''Add new account''.
# Select ''ACH''.
# Fill in the necessary details.
# If you'd like, choose to use a custom account name. This can help you manage multiple payment methods in Bisq. It will be visible only to you, like "ACH - Chase Bank - USD - Jane Doe".
# Once done, click save new account.
# If you have more than one ACH account you wish to add to Bisq you can create different accounts for each.

Ensure all the details are accurate when you add them. Sellers can only confirm payment if the name associated with the incoming ACH transfer matches the account name listed in Bisq.

== How do I buy BTC with my ACH Transfer account? ==

You can buy BTC with ACH on Bisq in 2 ways:

# Make an offer to buy BTC on the USD market.
# Take an offer to buy BTC on the USD market.

When the offer is confirmed, Bisq will provide you with the BTC seller's ACH details for you to complete the payment. You should send the payment immediately and confirm you have done so in Bisq by clicking 'payment started'.

If you have the option to include a payment reference, please leave it blank. If your bank requires one, please just use your name that matches your bank account.

Once the BTC seller receives your payment, they will confirm in Bisq, and your security deposit and your purchased trade amount will be available in your wallet.

'''Important:''' When sending an ACH payment, ensure it is a standard ACH transfer. Some banks allow you to set up an ACH Direct Deposit, which involves sending three micropayments to your trading partner's account for verification. Do not use '''ACH Direct Deposits for Bisq trades''', as these payments made by ACH direct debit can be charged back.

== How do I sell BTC with my ACH Transfer account? ==

You can sell BTC with ACH on Bisq in 2 waysː

# Make an offer on the USD market to sell your BTC.
# Take an existing offer on the USD market to sell your BTC.

After the offer is confirmed, Bisq will provide the BTC Buyer with your ACH details. The Buyer should send the payment at their earliest convenience and confirm it in Bisq by clicking 'Payment Started'.

'''Important:''' When receiving an ACH payment, ensure it is a standard ACH transfer. Some banks allow the recipient to set up an ACH Direct Deposit, which involves sending two micropayments to your account for verification. '''If you receive micropayments from a buyer, do not verify them.''' Setting up ACH Direct Deposits for Bisq trades allows the buyer to debit the seller's account without further authorization.

== Are there any limits for me to be aware of when sending an ACH transfer ==

Your bank may impose limits on the amounts you can send or receive. You should check if your bank has any such limits.

== Are there any fees for me to be aware of when sending an ACH transfer? ==

Fees charged by your bank for sending an ACH transfer can vary and it's best to check with them. Fees can also be different depending on the speed of the transfer as some banks offer expedited processing.

Generally, banks will not charge for receiving ACH transfers, but again, it's best to check with your bank since some do charge.

== How does dispute resolution work with ACH transfers? ==

If a dispute occurs, the mediator may ask the buyer to send them information showing that they made the payment of the correct amount to the BTC Seller within the correct time frame. The mediator may also ask the seller to send them information to prove their account details are correct, or in the case of the BTC Buyer making a payment late, or of the wrong amount.

For more information see [[dispute resolution]].

ACH Transfer

2026-04-29T22:08:14Z

SuddenWhipVapor: /* How do I set up a ACH Transfer account? */

'''ACH Transfer''', or Automated Clearing House Trasnfer, is a payment method introduced in Bisq v1.8.0. It is primarily used for domestic, low-value payments between participating financial institutions. ACH transfers are one of the two main bank transfer payment methods in the United States, the other being [[Domestic_Wire_Transfer|domestic Wire transfers]].

== What countries offer ACH Transfer? ==

ACH is only available in the United States.

== What currencies are available for ACH Transfer? ==

ACH only supports transfers of USD.

== What is the maximum trading duration for ACH Transfer? ==

The maximum trade time is 5 days, but most are completed within 2 business days. Financial institutions send ACH transfers in batches. Depending on when the transfer is initiated, it will be received the next business day, by the end of the current day, or in real time.

== What is the maximum BTC limit for ACH Transfer? ==

{{MaxTradeSizeBisq1}}.

== Is ACH Transfer a payment method that can be signed? ==

No, ACH accounts do not require signing.

== How do I set up a ACH Transfer account? ==

Please note that not all banks offer ACH transfers to third parties. It's crucial to verify if your bank supports this service. Most banks allow ACH transfers to accounts you own at other institutions. However, they may ask you to confirm three micro-deposits they initiate. This process is not the same as a third-party transfer, and Bisq sellers are instructed not to confirm these micro-deposits. Confirming micro-deposits enables your bank to send and receive money from that account, but this isn't a third-party transfer. If your bank fully supports third-party ACH transfers, they won't ask for micro-deposit verification. ACH transfers are typically provided at a low cost, so be sure to check with your bank about any fees.

== How do I add ACH Transfer as a payment method in Bisq? ==

To add your ACH account to Bisq:

# Head to the top menu and select ''Account''.
# Then, choose ''National Currency Accounts''.
# Click on ''Add new account''.
# Select ''ACH''.
# Fill in the necessary details.
# If you'd like, choose to use a custom account name. This can help you manage multiple payment methods in Bisq. It will be visible only to you, like "ACH - Chase Bank - USD - Jane Doe".
# Once done, click save new account.
# If you have more than one ACH account you wish to add to Bisq you can create different accounts for each.

Ensure all the details are accurate when you add them. Sellers can only confirm payment if the name associated with the incoming ACH transfer matches the account name listed in Bisq.

== How do I buy BTC with my ACH Transfer account? ==

You can buy BTC with ACH on Bisq in 2 ways:

# Make an offer to buy BTC on the USD market.
# Take an offer to buy BTC on the USD market.

When the offer is confirmed, Bisq will provide you with the BTC seller's ACH details for you to complete the payment. You should send the payment immediately and confirm you have done so in Bisq by clicking 'payment started'.

If you have the option to include a payment reference, please leave it blank. If your bank requires one, please just use your name that matches your bank account.

Once the BTC seller receives your payment, they will confirm in Bisq, and your security deposit and your purchased trade amount will be available in your wallet.

'''Important:''' When sending an ACH payment, ensure it is a standard ACH transfer. Some banks allow you to set up an ACH Direct Deposit, which involves sending two micropayments to your trading partner's account for verification. Do not use '''ACH Direct Deposits for Bisq trades''', as these payments made by ACH direct debit can be charged back.

== How do I sell BTC with my ACH Transfer account? ==

You can sell BTC with ACH on Bisq in 2 waysː

# Make an offer on the USD market to sell your BTC.
# Take an existing offer on the USD market to sell your BTC.

After the offer is confirmed, Bisq will provide the BTC Buyer with your ACH details. The Buyer should send the payment at their earliest convenience and confirm it in Bisq by clicking 'Payment Started'.

'''Important:''' When receiving an ACH payment, ensure it is a standard ACH transfer. Some banks allow the recipient to set up an ACH Direct Deposit, which involves sending two micropayments to your account for verification. '''If you receive micropayments from a buyer, do not verify them.''' Setting up ACH Direct Deposits for Bisq trades allows the buyer to debit the seller's account without further authorization.

== Are there any limits for me to be aware of when sending an ACH transfer ==

Your bank may impose limits on the amounts you can send or receive. You should check if your bank has any such limits.

== Are there any fees for me to be aware of when sending an ACH transfer? ==

Fees charged by your bank for sending an ACH transfer can vary and it's best to check with them. Fees can also be different depending on the speed of the transfer as some banks offer expedited processing.

Generally, banks will not charge for receiving ACH transfers, but again, it's best to check with your bank since some do charge.

== How does dispute resolution work with ACH transfers? ==

If a dispute occurs, the mediator may ask the buyer to send them information showing that they made the payment of the correct amount to the BTC Seller within the correct time frame. The mediator may also ask the seller to send them information to prove their account details are correct, or in the case of the BTC Buyer making a payment late, or of the wrong amount.

For more information see [[dispute resolution]].

ACH Transfer

2026-04-29T22:07:15Z

SuddenWhipVapor: /* How do I sell BTC with my ACH Transfer account? */

'''ACH Transfer''', or Automated Clearing House Trasnfer, is a payment method introduced in Bisq v1.8.0. It is primarily used for domestic, low-value payments between participating financial institutions. ACH transfers are one of the two main bank transfer payment methods in the United States, the other being [[Domestic_Wire_Transfer|domestic Wire transfers]].

== What countries offer ACH Transfer? ==

ACH is only available in the United States.

== What currencies are available for ACH Transfer? ==

ACH only supports transfers of USD.

== What is the maximum trading duration for ACH Transfer? ==

The maximum trade time is 5 days, but most are completed within 2 business days. Financial institutions send ACH transfers in batches. Depending on when the transfer is initiated, it will be received the next business day, by the end of the current day, or in real time.

== What is the maximum BTC limit for ACH Transfer? ==

{{MaxTradeSizeBisq1}}.

== Is ACH Transfer a payment method that can be signed? ==

No, ACH accounts do not require signing.

== How do I set up a ACH Transfer account? ==

Please note that not all banks offer ACH transfers to third parties. It's crucial to verify if your bank supports this service. Most banks allow ACH transfers to accounts you own at other institutions. However, they may ask you to confirm two micro-deposits they initiate. This process is not the same as a third-party transfer and Bisq sellers usually won't confirm these micro-deposits. Confirming micro-deposits enables your bank to send and receive money from that account, but this isn't a third-party transfer. If your bank fully supports third-party ACH transfers, they won't ask for micro-deposit verification. ACH transfers are typically provided at a low cost, so be sure to check with your bank about any fees.

== How do I add ACH Transfer as a payment method in Bisq? ==

To add your ACH account to Bisq:

# Head to the top menu and select ''Account''.
# Then, choose ''National Currency Accounts''.
# Click on ''Add new account''.
# Select ''ACH''.
# Fill in the necessary details.
# If you'd like, choose to use a custom account name. This can help you manage multiple payment methods in Bisq. It will be visible only to you, like "ACH - Chase Bank - USD - Jane Doe".
# Once done, click save new account.
# If you have more than one ACH account you wish to add to Bisq you can create different accounts for each.

Ensure all the details are accurate when you add them. Sellers can only confirm payment if the name associated with the incoming ACH transfer matches the account name listed in Bisq.

== How do I buy BTC with my ACH Transfer account? ==

You can buy BTC with ACH on Bisq in 2 ways:

# Make an offer to buy BTC on the USD market.
# Take an offer to buy BTC on the USD market.

When the offer is confirmed, Bisq will provide you with the BTC seller's ACH details for you to complete the payment. You should send the payment immediately and confirm you have done so in Bisq by clicking 'payment started'.

If you have the option to include a payment reference, please leave it blank. If your bank requires one, please just use your name that matches your bank account.

Once the BTC seller receives your payment, they will confirm in Bisq, and your security deposit and your purchased trade amount will be available in your wallet.

'''Important:''' When sending an ACH payment, ensure it is a standard ACH transfer. Some banks allow you to set up an ACH Direct Deposit, which involves sending two micropayments to your trading partner's account for verification. Do not use '''ACH Direct Deposits for Bisq trades''', as these payments made by ACH direct debit can be charged back.

== How do I sell BTC with my ACH Transfer account? ==

You can sell BTC with ACH on Bisq in 2 waysː

# Make an offer on the USD market to sell your BTC.
# Take an existing offer on the USD market to sell your BTC.

After the offer is confirmed, Bisq will provide the BTC Buyer with your ACH details. The Buyer should send the payment at their earliest convenience and confirm it in Bisq by clicking 'Payment Started'.

'''Important:''' When receiving an ACH payment, ensure it is a standard ACH transfer. Some banks allow the recipient to set up an ACH Direct Deposit, which involves sending two micropayments to your account for verification. '''If you receive micropayments from a buyer, do not verify them.''' Setting up ACH Direct Deposits for Bisq trades allows the buyer to debit the seller's account without further authorization.

== Are there any limits for me to be aware of when sending an ACH transfer ==

Your bank may impose limits on the amounts you can send or receive. You should check if your bank has any such limits.

== Are there any fees for me to be aware of when sending an ACH transfer? ==

Fees charged by your bank for sending an ACH transfer can vary and it's best to check with them. Fees can also be different depending on the speed of the transfer as some banks offer expedited processing.

Generally, banks will not charge for receiving ACH transfers, but again, it's best to check with your bank since some do charge.

== How does dispute resolution work with ACH transfers? ==

If a dispute occurs, the mediator may ask the buyer to send them information showing that they made the payment of the correct amount to the BTC Seller within the correct time frame. The mediator may also ask the seller to send them information to prove their account details are correct, or in the case of the BTC Buyer making a payment late, or of the wrong amount.

For more information see [[dispute resolution]].

Trading rules

2026-04-15T12:30:19Z

SuddenWhipVapor: /* Do not confirm payments with mismatching details */ requirement to open mediation when payment details don't match

Both Bisq traders must follow these '''trading rules''' to ensure smooth and successful trades.

To trade on Bisq, you assume one of two roles, no matter what national currency or cryptocurrency you’re trading: you either ''buy bitcoin'' or ''sell bitcoin''.

The rules below are '''default''' rules for every transaction. Offer makers sometimes specify their own additional terms for handling payments. For example, a seller using cash deposits might require a picture of a receipt torn in half with "NO REFUND" written on it. Face-to-face traders often specify terms about where and how to meet.

Make sure you’re okay with an offer-maker’s terms '''before''' you accept an offer!

Trade rules also help with the following:

* Promoting good behavior from traders
* Penalizing bad behavior from traders
* Promoting good payment accounts of traders
* Penalizing bad payment accounts of traders
* Put the 'wrong doer' in a worse position and the person 'not at fault' in a better position

= Common rules =

=== Match Bisq account details with real data ===

The data you enter during fiat account creation in Bisq must match with the real data associated to the fiat account (for example, but not limited to, filling in your full account holder name instead of placing just your initials).

=== No requirement to reply in trader chat ===

While using the available trade chat can be helpful to resolve issues directly among traders without the overhead of mediation, and being communicative is a good way to ease the process for new traders, there is no obligation to reply to a peer's messages.

=== Do not communicate with your peer away from Bisq ===

Using email addresses, phone numbers, and other means to contact traders is strongly discouraged. The trader chat feature built into Bisq should be used instead: not only is it more private, but the chat record can more easily be made available to mediators and arbitrators (useful in case a trader’s chat messages indicate they broke a rule). This includes advertising offers to sell BTC with a way to contact you, for example a website, Telegram user name, or email.

In any case, it is forbidden to contact the peer using contacts obtained from their payment details, without their prior consent, or missing a compelling reason to do so.

=== Be responsive during a dispute ===

Traders are expected to reply within 48hrs to either mediators or arbitrators, and could lose the dispute based on unresponsiveness.

Mediators may take up to 48 hours to respond to messages, and arbitrators may take up to 5 days to respond to messages.

=== Do not change payment details once trade is in progress ===

Once the deposit transaction is published, the trade is in progress, and its terms cannot be changed. Traders agreed to use the payment details specified in the trade contract.

In the event of an unexpected circumstance (e.g. hitting a bank-imposed transfer limit, or a payment institution interfering with the transaction), traders can propose alternatives through trader chat or mediation, but the peer is not required to comply. It is each trader's responsibility to ensure that the payment account in their offer will work before an offer is taken.

= Rules for bitcoin sellers =

Whether making or taking an offer, bitcoin sellers put all the bitcoin they’re selling in the multisig escrow, so there’s less for them to do and fewer rules they need to follow.

=== Click <code>Confirm payment</code> after receiving payment ===

Sellers have until the end of the maximum trade period to do so.

[[Account_limits#Account_signing|Account signing]], introduced in Bisq v1.2, enables a seller with a signed payment account to sign a buyer’s payment account when they successfully receive a payment. For such trades, it is recommended that the seller take as long as possible (i.e., wait until close to the end of the trade period) to confirm receipt of payment to reduce the chance of a chargeback.

=== Do not confirm payments with mismatching details ===

Payer name, account numbers, payment method, institution, and other details of a payment should match the details in the trade contract. If there are any concerns that buyer's payment details do not match (e.g. wrong name, account number etc) mediation should be opened immediately, using the key combination <code>Ctrl-O</code> while on the trade panel.'''

{{Admonition_Warn|This is especially relevant for trades in which a signed seller trades with an unsigned buyer, because confirmation of payment receipt signs the buyer’s payment account. In case of such an issue, a dispute should be opened.}}

= Rules for bitcoin buyers =

{{Admonition_Warn|To avoid unexpected issues, make sure you can actually carry out a payment with the payment method you’ve set up in Bisq. Examples: Wells Fargo doesn’t allow cash deposits into bank accounts not owned by the depositor, and Zelle has weekly and monthly transfer maximums that are easy to overlook. The software will warn you about known issues, but cannot possibly keep up with all the newest banking and money transfer rules.}}

=== Make payment reasonably early within trade period ===

Buyer should complete at a time such that the seller has enough time to acknowledge receipt of the payment before the trade period is over. Waiting until the very end of the trade period to make a payment is not advised, as then the seller cannot reasonably act in time to acknowledge receipt (also, it’s annoying). The lengths of trade periods vary based on [[Payment methods|payment method]].

This is especially important for buyers with unsigned payment accounts trading with sellers with signed payment accounts. A seller will not want to confirm receipt of a payment made at the last minute from an untrusted account, so if you’re a buyer looking to get your payment account signed, you should make the payment ''as soon as possible''.

Some payment methods include an option to cancel a payment after you have sent it eg Revolut and Interac e-Transfer. If you cancel payment without agreement with the seller or mediator you might end up being penalized for cancelling the trade.

=== Click Payment started after sending payment ===

Seller cannot mark payment as received until buyer confirms that they have sent it.

Don’t forget to do this!

=== Leave the "reason for payment" field empty ===

{{Admonition_Warn|Before 1.5.5, it was required to put the trade ID in the 'reason for payment' field of a payment. As of 1.5.5, reason for payment should be left BLANK.}}

Some payments offer a way to specify a reason for payment (some payment methods call it "Message" or "Information for recipient" or similar). '''Leave this field BLANK.''' Do not put the trade ID, any mentions of "Bisq" or "Bitcoin" or "crypto", or any other text whatsoever.

If you are required to fill in a reason, use your account name eg "Joe Bloggs" alternatively enter something non-descriptive like a dash "-". If you would prefer to use other text please agree this with your peer in trader chat. Please remember your peer is not obligated to agree anything and may not want to agree to anything other than leaving the description blank, your name or a dash.

Violating this rule will likely result in a [[Table of penalties|trade penalty]].

Many banks don’t like anything related to Bitcoin, and may take draconian measures if they sense such a transaction.

Many users trade from personal accounts and may object to using anything that looks like it could be a commercial transaction.

=== Pay any transaction fees ===

Any fees incurred to make the payment via the agreed payment method (e.g., bank fees for bank transfer, money-order fees for money orders, etc) are the buyer’s responsibility to pay.

The seller should receive the exact amount of the trade. The only exception to this rule is if the receiving institution imposes a fee on incoming payments—these fees are borne by the seller.

= What happens when things go wrong? =

Sometimes trades do not go to plan for whatever reason.

It is prudent for all traders to know when entering into the trade what will happen when things go wrong. Traders would be wise to make themselves aware of the [[dispute resolution]] process to ensure there are no surprises.

Bisq 2 mobile applications

2026-04-11T16:53:26Z

SuddenWhipVapor: SuddenWhipVapor moved page Bisq 2 mobile to Bisq 2 mobile applications: more appropriate and descriptive

The mobile ecosystem of Bisq 2 allows access to the [[Bisq Easy]] protocol from a smartphone, via two applications:

* Bisq Easy Mobile (Android only)
* Bisq Connect (Android and iOS)

== Bisq Easy Mobile ==

Bisq Easy Mobile is a full Bisq Easy node running on your Android device. It features the complete p2p network stack and connects with its own onion address.

It provides the same privacy and security as the Bisq 2 desktop application.

It is primarily suited for buyers who:
* want to buy their first sats
* prefer not to use a desktop computer

Pros:
* Runs a full Bisq Easy node
* Does not require a separate device

Cons:
* Available for Android only
* Higher battery, bandwidth, and resource usage
* App may lose connectivity when moved to background, and reconnection can take time
* No synchronization or interoperability with a desktop instance
* Users must manually manage backups

== Bisq Connect ==

Bisq Connect is a lightweight companion app that allows you to remotely access and control a Bisq 2 node running elsewhere.

It is available for both Android and iOS (via TestFlight).

Instead of running a node locally, the app connects to a backend node, which can be:

* your own Bisq 2 desktop application
* a Bisq 2 node running on a headless machine or VPS
* a node operated by a trusted third party

The mobile app acts as a remote interface, allowing you to monitor and manage your node from your phone.

Features:
* Pairing via QR code
* Real-time market data
* Push notifications
* Private P2P messaging
* Built-in Tor support
* Open-source and auditable

Pros:
* Available on both Android and iOS
* Low resource and battery usage
* Seamless access to the same data across devices when self-hosted
* No need for mobile backups (data is stored on the backend node)
* Mobile app can be closed without affecting node operation

Cons:
* Requires a running backend node
* Using a third-party node requires trust in the operator, as all data is hosted on that node

== Notes ==

On iOS, Bisq Connect is currently distributed via Apple TestFlight and requires iOS 16.0 or higher.

TestFlight builds expire after 90 days, but updates are released regularly.

== Future Development ==

Bisq Easy Mobile will not support the upcoming MuSig protocol.

Bisq Connect is the likely platform for supporting new protocols, depending on development priorities and user demand.

Bisq 2 mobile

2026-04-11T16:53:26Z

SuddenWhipVapor: SuddenWhipVapor moved page Bisq 2 mobile to Bisq 2 mobile applications: more appropriate and descriptive

#REDIRECT [[Bisq 2 mobile applications]]

Bisq 2 mobile applications

2026-04-11T16:52:04Z

SuddenWhipVapor: Rework

MuSig-tradelimits

2026-04-09T07:58:00Z

SuddenWhipVapor: Include limit simulator reference

== Why are trade limits necessary? ==

Most fiat payment methods carry a risk of bank chargebacks.
To reduce this risk, Bisq applies both trade amount limits and trade rate limits to Bitcoin buyers, since buyers are the ones who could initiate a chargeback.

=== Fiat trades – Bitcoin buyers ===

Trade limits depend on:

* The chargeback risk of the selected payment method
* Whether the buyer has imported a signed account age witness from Bisq 1
* The age of the payment account

=== Fiat trades – Bitcoin sellers ===

For sellers, trade limits depend only on the selected payment method.

=== Cryptocurrency trades ===

A maximum trade amount limit equivalent to 10,000 USD applies.

== How are trade limits applied? ==

Trade limits are calculated based on these rules:

* Each fiat payment method has a chargeback risk level. Depending on that level, the maximum trade amount of 10,000 USD can be reduced by up to 50%.
* If a user imports a previously signed Bisq 1 account, all limits are removed.
* If a payment account is older than 90 days, limits are removed. For newer accounts, limits increase gradually until reaching that age.

=== Trade rate limit ===

The trade rate limit (number of trades allowed per day) is based on the trade amount limit:

* It is calculated as: trade amount limit ÷ 1,000
* The minimum value is 1 trade per day
* Once the maximum trade amount limit is reached, the trade rate limit no longer applies

You can import accounts from Bisq 1 and keep their account age.

== Trade limit calculator ==

Use the simulator to see which limits apply to you based on:

* Your selected payment method
* The age of your payment account
* Whether you have imported a signed Bisq 1 account

MuSig-tradelimits

2026-04-09T07:52:31Z

SuddenWhipVapor: Substasntial stub

MuSig-tradelimits

2026-04-08T08:17:09Z

SuddenWhipVapor: First stub

== WIP ==

Setting a higher limit for trade amounts is an effective way to reduce security risk when dealing with new users.

Bisq Easy

2026-03-19T20:38:36Z

SuddenWhipVapor: /* Trade Rules */ updated payment reason rule

Bisq Easy is a trade protocol for Bisq 2, designed to facilitate the acquisition of bitcoin with zero trade fees and without the requirement of a security deposit. Bisq Easy is a social trade protocol intended for novice bitcoin buyers seeking a non-KYC option and aiming to be efficiently onboarded by experienced and knowledgeable sellers that are familiar with the Bisq platform.

Bisq Easy is currently the only trade protocol for [[Bisq 2]]. More [[Trade_Protocols|trade protocols]] are planned for the future.

== Bisq Easy Trade Protocol Specifics ==

=== Trade fees ===

There are no trade fees for buyers or sellers for trading on Bisq Easy.

=== Mining fees ===

Buyers will not have to pay any mining fees when they trade on Bisq Easy.

Sellers will need to pay any fees required to send the bitcoin to the buyer after receiving their payment. For on chain transactions the seller is responsible for paying mining fees needed to send the bitcoin to the buyer's waller. For lighting transactions the seller is responsible for paying any routing fees needed to pay the buyer's ln invoice.

=== Security mechanisms ===

The security of the trade is proportional to the reputation of the seller.

As Bisq Easy is [[reputation based]], and reputation provides a fairly low security model, it means traders on Bisq Easy are suited only to rather small amounts of bitcoin.

By default buyers can only exchange messages with sellers that have a certain level of reputation, however, buyers can opt-out from that protection.

Trading with sellers without reputation, or very low reputation, carries significant risks and should be only done if the risks are well understood and managed.

=== Currencies / Payment Methods ===

Bisq Easy buyers and sellers can trade bitcoin for any type of fiat.

Fiat buyers and sellers can choose whatever type of payment method they agree upon for fiat transfer.

=== Dispute mechanisms ===

Buyers and sellers trading on Bisq Easy can access mediation support should anything go wrong with their trade.

Mediators will be able to:

* Help facilitate the successful completion of the trade
* Confirm fiat / altcoin and bitcoin payments
* Help cancel trade if needed
* Report a trader who severely violated the trade rules to the moderator who can ban the user.

Depending on the form of reputation used, a fraudulent seller can get their bonded BSQ confiscated by the DAO or their Bisq 1 onion address banned. As all reputation is linked to the user profile, a banned user profile disables their reputation.

=== Security deposit requirements ===

Bisq Easy trades do not require any security deposits from either the buyer or seller.

=== Privacy benefits / trade-offs ===

As no security deposits are required buyers and sellers using fiat will be revealing their bank account details to users that might end up backing out of the trade. If a user backs out of a trade there is less possibility to penalize them than if they had to trade using a security deposit. The seller can report a buyer who cancelled the trade after the payment account data has been transmitted to the moderator, who can ban the buyer.

== Identity ==

Buyers and sellers on Bisq Easy can create multiple identities.

Find out more about managing your [[Identity]] on Bisq 2.

== Reputation ==

The security mechanism of Bisq Easy is based on the reputation of the seller. Buyers on Bisq Easy do not need to have a reputation as they will always send the payment first.

Find out more about [[Reputation]] for Bisq Easy.

== Using Bisq Easy to buy bitcoin ==

Users of Bisq Easy can buy bitcoin using fiat or altcoins with no fees and no security deposits.

== Using Bisq Easy to sell bitcoin ==

Users of Bisq Easy can sell bitcoin for fiat or altcoins with no fees and no security deposits.

Sellers of Bisq Easy will however have to build up their [[reputation]] in order to get buyers.

== How to buy bitcoin on Bisq Easy ==

Buying Bitcoin with Bisq Easy is recommended for small fiat amounts, or as a starting point if you still have no Bitcoin that you can use for the security deposits of other trade protocols.

You can opt for two ways to find a trading partner to get some Bitcoin: taking an existing offer or creating one.

=== Creating an offer ===
Creating an offer is a great way to establish your own terms and simply wait for someone to match what you are after. It is also the right option if you don't find any offers with the right premium or payment methods in the market you want to trade in. Follow along to learn how to navigate to your preferred market and create a new offer in it:

Begin by opening up Bisq 2. Once the application has started, you should select ''Bisq Easy'' on the left panel, and ''Offerbook'' on the top tab.

[[File:Create buy offers screenshot 1.png|frameless]]

Each different national currency has its own market. You can click on the displayed pair to open a selector where you can choose the currency you would like to trade in. In this example, we are interested in buying some Bitcoin by paying with Euros, so we will select the ''BTC/EUR'' pair, but you should select whatever currency you are using. Afterward, click on the ''Create offer'' button on the right-hand side.

[[File:Create buy offers screenshot 2.png|frameless]]

You will now enter the offer creation wizard. The first step will be to choose between buying or selling Bitcoin. Select ''Buy Bitcoin'' and click on ''Next''.

[[File:Create buy offers screenshot 3.png|frameless]]

On the following screen, you will be asked for confirmation on which currency you want to pay your Bitcoin with. The selected currency will be the one you selected in the previous ''Offerbook'' screen. You can change your mind here if needed. Since for this example we want to move forward with Euros, we don't need to change anything on this screen, and we can simply click ''Next''.

[[File:Create buy offers screenshot 4.png|frameless]]

On the next screen, you will have to select which Payment Methods are you willing to use. You should select at least one, but you can also select multiple of them. The more Payment Methods you add, the more chances you will have of finding a willing trade peer. In this example, we initially select ''SEPA'' and ''Revolut''.

[[File:Create buy offers screenshot 5.png|frameless]]

Besides the presented Payment Methods, you can also add customized Payment Methods to your offer. For instance, for this offer, I would be happy to make a cash deposit at a Rabobank physical branch. I can use the bottom input to add this method to my offer.

[[File:Create buy offers screenshot 6.png|frameless]]

Once you are done selecting Payment Methods, you can move on by clicking ''Next''.

On the next screen, you will have to set how much Bitcoin you want to buy or, putting it the other way around, how much fiat currency you want to sell. The minimum trade amount on Bisq easy is the equivalent of 6 USD and the maximum amount is {{MaxBisqEasyTrade}}. You can write the fiat amount, the BTC amount, or simply move the slider around.

[[File:Create buy offers screenshot 9.png|frameless]]

You also have the option of defining a range instead of a fixed value for the trade amount. By doing that, you set a minimum and maximum amount, and you signal to the market that you are willing to trade any amount between those two numbers. For this example, we will create an offer with a range between 100€ and 200€. Once you have set your fixed value or a range, click ''Next'' to move on.

[[File:Create buy offers screenshot 10.png|frameless]]

With this, you will reach the final step of the offer creation wizard. The final screen shows a summary of all the details you have defined. Now is the time for you to review whether everything is fine. This is important because, once you click on ''Create offer'', the offer will be available for anyone to take and, once that happens, it will be binding. So, make sure you are happy with the details you see. Once you are sure, click on ''Create offer'' and your offer will be added to the market.

[[File:Create buy offers screenshot 11.png|frameless]]

Your order is finally ready. Now, you will have to wait until another peer takes it. If your offer remains unpicked for longer than you would like to, consider modifying it to add additional payment methods or adding a more flexible range of values that could attract different users.

[[File:Create buy offers screenshot 12.png|frameless]]

Once a peer takes your offer, you will receive a notification and be able to see the started trade in the ''Open Trades'' panel of Bisq Easy. Also, keep in mind that offers remain open until you close them. If you only want to transact once, you should close it after it gets taken, or more peers could keep taking it!

=== Taking an offer ===

Taking an existing offer is the fastest and simplest way to find a partner and start trading. Follow along to learn how to navigate to your preferred market and pick an existing offer in it.

Begin by opening up Bisq 2. Once the application has started, you should select ''Bisq Easy'' on the left panel, and ''Getting started'' on the top tab.

[[File:Taking offer to buy 1.png|frameless]]

On this page, click on the ''Start trade wizard''. This is the easiest way to get started. A small note: once you become more experienced, you might prefer to use the ''Offerbook'' page to do your trades. But for the first trades, we advise using the trade wizard.

[[File:Taking offer to buy 2.png|frameless]]

With this, you will enter the trade wizard, which will guide you step by step through the process of taking an existing offer to buy some Bitcoin. In the first screen, select ''Buy Bitcoin'' and click on ''Next''.

[[File:Taking offer to buy 3.png|frameless]]

In the following screen, you need to indicate which national currency you want to use to pay your trading partner. Since we want to use Euros for this trade, we select that currency in the list. Once you have selected your currency, click on ''Next'' to move on.

[[File:Taking offer to buy 4.png|frameless]]

On the next screen, you will have to select which Payment Methods you are willing to use. You should select at least one, but you can also select multiple of them. The more Payment Methods you add, the more chances you will have of finding a willing trade peer. In this example, we initially select ''SEPA'' and ''Revolut''.

[[File:Create buy offers screenshot 5.png|frameless]]

Once you are done selecting Payment Methods, you can move on by clicking ''Next''.

On the next screen, you will have to set how much Bitcoin you want to buy or, putting it the other way around, how much fiat currency you want to sell. The minimum trade amount on Bisq Easy is the equivalent of 6 USD and the maximum amount is {{MaxBisqEasyTrade}}. You can write the fiat amount, the BTC amount, or simply move the slider around.

[[File:Taking offer to buy 5.png|frameless]]

For this example, let's imagine we would like to buy 150€ worth of Bitcoin. We set the value and click on ''Next'' to move on.

In the following screen, you will be presented a list of offers that match your needs. You can select any of the offers presented, but we advise taking the first offer. By default, offers will be presented by decreasing reputation, so the most trusted trades will be on the top of the list. You can check other offers that might have more interesting prices, but be aware that the lower the reputation of the trader, the higher the risk you will face. If you want to keep things safe and simple, simply pick the first offer that you see. Once you have settled for an offer, click on ''Next'' to move on.

[[File:Taking offer to buy 6.png|frameless]]

The final screen will allow you to review all the details. Make sure you are happy with all the details of the trade, since once you move on, you will effectively commit to doing the trade. If there's anything you want to change, you can always navigate back and modify any of the trade details. Once you are ready, click on ''Confirm trade''.

[[File:Taking offer to buy 7.png|frameless]]

Once you have done this, the offer is taken and you can begin the trade process. You can read more about the trade process here: [[Bisq_Easy#Trade_Process|Trade Process]].

Remember that when you take an offer, you commit to follow through. Be aware that, once you take it, you can't simply back down without consequences.

Note that there is also a chance that no offers are found matching your needs. If this is the case, you will see a screen like the one below. You can wait some time and try again later, or you can instead create your own offer. You can read more about creating an offer here [[Bisq_Easy#Bisq_Easy#Creating_an_offer|Creating a buy offer]].

[[File:Taking offer to buy 8.png|frameless]]

== How to sell bitcoin on Bisq Easy ==

Users of Bisq Easy can both make an offer to sell bitcoin, or take an offer from a user looking to buy bitcoin.

Seller's on Bisq Easy will usually be experienced Bisq users. It is expected they will be helpful and supportive to buyers who are new to Bitcoin and/or Bisq. Bisq Easy seller's should be passionate about helping new Bisq users smoothly acquire no KYC bitcoin in a peer to peer manner.

As building reputation incurs costs for the bitcoin sellers. It is expected that they will sell bitcoin at a premium of about 10-15%. The premium reflects the additional costs and compensates sellers for the on-boarding service they provide.

== Trade Process ==

Trade process for Bisq Easy is as follows:

* The offer maker defines the trade terms, if this was not already defined in the maker's user profile.
* Once the traders have agreed on the trade terms (e.g. payment method and trade price) the trade starts.
* The seller transmits the payment account details to the buyer (e.g. bank account number). The buyer sends the BTC address to the seller.
* The buyer starts the Fiat payment to the seller's account and sends the seller a message that the payment is in transit.
* Once the seller has received the Fiat payment they send the Bitcoin to the buyer's address.
* After the buyer receives the Bitcoin the trade is completed.

== Trade Rules ==

Bisq Easy trading rules are as follows:

* Before the payment details are exchanged the trade can be canceled by any party without justification.
* After the payment details are exchanged, not fulfilling the trade obligations is considered a breach of the trade contract and can lead to getting banned from the network.
* When sending the Fiat, the buyer MUST leave the payment reason field blank, or, if that is not possible, fill it with their own name, and MUST NOT use any term related to 'Bitcoin', 'Bisq' or 'Trade'.
* If the trade cannot be completed instantly because the Fiat transfer takes longer, both traders have to be online at least once a day to follow up the trade process.
* If there are any open questions or problems the traders can use the support chat, invite a mediator into their trade chat or get in touch with Bisq support team on the [[Matrix_bisq.chat|Matrix channel]].

== Chat Rules ==

Bisq Easy has the following chat rules it expects traders to follow:

* Be respectful: Always treat others with kindness and respect. Avoid offensive language, personal attacks, and harassment. Remember that behind every screen is a real person with feelings.
* No spamming: Please refrain from flooding the chat with repetitive or irrelevant messages. Keeping the conversation meaningful and on-topic helps everyone engage in a more constructive manner.
* No advertising: We kindly ask you to avoid promoting products, services, or posting external links. This ensures that the focus remains on meaningful discussions rather than promotional content.
* No hate speech: We have zero tolerance for content that promotes discrimination, hate speech, or violence against any individual or group. Let's foster an inclusive and supportive community.
* No trolling: Disruptive behavior, trolling, or intentionally provoking others disrupts the positive atmosphere we aim to maintain. Let's all strive for respectful and constructive interactions.
* Keep it safe: Protect your privacy and that of others by not sharing personal information such as phone numbers, addresses or any other sensitive data in the chat. Safety first!
* Respect privacy: Do not share private conversations or screenshots without consent. Respecting each other's privacy is a cornerstone of trust.
* Report misconduct: If you witness any violations of these rules or encounter inappropriate behavior, please report it to the moderator. Your vigilance helps maintain a friendly and safe community.
* Follow moderator's Instructions: Our moderators are here to ensure a positive environment. Please comply with any instructions or guidelines they provide to maintain order and respect.
* Enjoy the chat: Above all, we encourage you to engage in meaningful discussions, make friends, and have fun in a positive and inclusive environment. Let's create a community we can all be proud to be a part of.

Remember, by participating in the chat, you agree to abide by these rules. Failure to comply may result in warnings, temporary mute, or ban from the Bisq network.

== How to stay safe on Bisq Easy ==

Here are some tips for keeping safe when trading on Bisq Easy and avoiding any scams.

=== Tips for bitcoin buyers ===

Bitcoin buyers send the fiat payment before sending any bitcoin. For this reason they should take steps to ensure their trades are successful.

# Start with a small amount as a test trade
# Start chatting with the seller before sending the fiat payment to check that they are still active
# Choose a seller with a high reputation. The higher the reputation of the seller the better. Sellers need a minimum reputation score of 30,000, ideally you should be choosing to trade with someone higher than this. Look at the star system for guidance. It will be safer to trade with a 5 star rated seller than a 1 star rated seller.
# Send payment as soon as possible once you have the seller's account details.
# Only send payment to the account details provided by the Seller in the trade chat window. If the seller is trying to change the account they want you to send payment to, it would be better to cancel the trade and open a new trade with another seller.
# Place the trade ID from Bisq Easy in the payment reason.
# Send the payment from the same account you share the information with in trader chat. For example if you are having problems with the payment do not send payment from your partners, business, friends etc account. Instead try and resolve the issue so you can send payment from the correct account and failing that open mediation to get additional support.
# Keep the trade chat limited to using Bisq 2. Do not communicate with the seller via WhatsApp, Matrix etc as it will make mediation much harder if there is an issue.
# Avoid trading off platform with any Bisq sellers.

=== Tips for bitcoin sellers ===

Although bitcoin buyers send the fiat payment before bitcoin sellers send them any bitcoin, sellers should still be aware of buyers attempting any charge-back scams. There is almost no cost for a bitcoin buyer to create an account and start making trades, therefore, there is little for a buyer to lose by attempting a scam. Almost all buyers on Bisq Easy will be honest but it is still good to be cautious.

For this reason they should take steps to ensure their trades are successful.

# Be careful when dealing with buyers with brand new accounts (the buyer's account age is shown in their profile).
# Avoid payment methods that have a high possibility of charge-backs eg; PayPal, Venmo
# Make sure the payment you receive matches the buyers account details. Avoid sending bitcoin to buyer's with mis-matching account details. It would be better to refund the payment to the account you received the payment from and cancel the trade.
# Keep the trade chat limited to using Bisq 2. Do not communicate with the buyer via WhatsApp, Matrix etc as it will make mediation much harder if there is an issue.
# Avoid trading off platform with any Bisq sellers.
# If you have any concerns about a trade open mediation.

Cash by mail

2026-03-06T11:03:31Z

SuddenWhipVapor: additional measures

'''Cash by mail''' (CBM) is one of the most private payment methods on Bisq.

This payment method has special requirements you should be aware of, so please read this article carefully before doing any cash by mail trades.

__TOC__

= Setting up a CBM account in Bisq =

When setting up cash-by-mail payment account in Bisq, you will be asked to enter the following information:

* Name or nym the package should be addressed to
* Postal address
* Currency
* Additional information

If selling BTC, the name/nym and address fields should be the name you would like to buyer to address the package to. If buying BTC, the name/nym and address fields should be the name the seller or postal service to return the package to in case of any issues.

You can only select one currency for a single cash-by-mail account. If you would like to trade with more than one currency, please create separate accounts for each currency.

Define any special terms, conditions, or details you would like to be displayed with your offers in the 'Additional Information' field. '''Users can see this field ''before'' taking the offer by clicking the info icon of the offer.'''

{{Admonition_Note|Consider setting up separate cash-by-mail accounts for buying and selling so you can specify special instructions for each.}}

{{Admonition_Note|You might want to use a PO Box and a name which is not your real one, instead of registering an account to your own house under your real identity.}}

= Making a CBM offer =

Make sure to state any special terms or conditions in the 'Additional Information' field of the payment account before making an offer. The person taking the offer will be accepting these terms and conditions by taking the offer.

Please note it is against Bisq rules to use the 'Additional Information' field to include advertising offers with a way to contact you prior to the trade (e.g. website, phone, email, or Matrix/Keybase/Telegram user name). Doing this can result in a penalty, should someone take your offer and request for you to be penalized.

= Taking a CBM offer =

'''Make sure to check the offer maker's terms and conditions before taking a CBM offer.''' If you cannot fulfill the terms, do not take the the offer. If you have specific terms you would prefer, consider making your own offer instead.

= Sending cash in the mail =

Please see the Bisq trade protocol for [[Trading_rules|general trading rules]].

In addition, buyers should:

* follow any special requirements and conditions set by the seller
* package cash in a tamper-evident cash bag
* place tamper-evident cash bag inside a parcel. AVOID using an envelope where a postal worker would be able to feel a wad of cash as this can lead to stolen cash
* address the package to the name and address in the seller's cash-by-mail payment account
* put a return address in case the package cannot be delivered
* use inner and outer packaging addressed the same in case the outer one gets ripped open or damaged by water
* seal all packages well, with tape
* film or take high-resolution photos of the cash packaging process with the address and tracking number already affixed to packaging
* send the cash package to the BTC seller with a courier service that requires receipt of delivery to be confirmed by the seller
* if it's available, consider using a courier service that has appropriate insurance in place for any issues with delivery (i.e. USPS Registered Mail, insuring packages up to $50,000)

'''Please make sure you have all the necessary items arranged ''before'' taking an offer (tamper-evident cash bags, other packaging, courier and insurance picked out, etc).'''

Additional measures to ensure safer trades:

* to help prove package integrity before and after shipping, both parties should ideally also take high-definition photos, or preferably a video, when handing the package to or collecting it from the postal office, this helps verify whether the package remains in the same condition as during preparation
* packaging should be as inconspicuous as possible, a flat envelope can reveal likely contents and invite theft, while using a hollowed paperback book or another ordinary object can better conceal the cash

= Receiving cash in the mail =

When receiving cash in the mail, you should:

* Film the opening of the package, making sure that the tracking number provided by the sender is visible in the video.
* Follow any special requirements and conditions set by the buyer.
* Communicate with buyer's courier service as required.

= Dispute resolution =

Cash-by-mail trades are less verifiable than other fiat trades. This makes handling disputes much harder, so the onus to act honestly is squarely on both peers.

It is highly recommended for peers to make use of Bisq's trader chat to communicate directly with one another. This is the most promising way to resolve any issues that may arise during the trade.

Regarding dispute resolution, please note:

* Mediators can consider your case and make a suggestion, but they are NOT guaranteed to help.
* If a mediator is engaged, and if either peer rejects the mediator's suggestion, both peers' funds will be sent to a [https://bisq.wiki/Arbitration#Time-Locked_Payout_Transaction Bisq 'donation' address], and the trade will effectively be completed.
* If a trader rejects a mediation suggestion and opens arbitration, it could lead to lose both trading and deposit funds.
* Arbitrators will make a decision based on the evidence provided to them. Therefore, please follow and document the above processes to have evidence in case of dispute. For cash-by-mail trades, arbitrator decisions are final, meaning reimbursement requests to the Bisq DAO for any funds lost in cash-by-mail trades will NOT be considered.

Verse

2026-02-17T11:23:59Z

SuddenWhipVapor: notice about Verse having been discontinued.

{{Admonition_Note|'''Verse has been DISCONTINUED as a service. This article has been kept for historical purposes, but the link from [[Payment methods]] has been removed.'''}}

'''Verse''' is a payment method added in Bisq v1.7.5.

Verse is a mobile payment app based in Europe owned by Square. Users can pay and request money from your friends. Payments are immediate and free. It is easy to use.

Verse is multi currency, easy to use and payments are instant and free.

Verse is designed for small payments between friends and family members. Fiat money you receive is stored in your Verse balance. From there you can send it to your friends’ digital wallets. When you want that money to be in your real world wallet, all you have to do is transfer it to your bank account. Withdrawals from Verse (sending to own account) take anywhere from a few seconds to two business days.

Verse allows users to:

* Send money to their contacts listed in the contacts list on their mobile device.
* Request money from their contacts listed in the contacts list on their mobile device.
* Receive and withdraw payments made by other Users that have your mobile phone number saved in their contacts list.
* Payments via Verse card (if they have one)
* Withdraw cash using Verse card via ATM network (if they have one)

Money can be added by debit / credit card. Verse accepts VISA and MasterCard. Withdrawals are made to your linked debit / credit card.

Why
Verse is like the European Cash App. It is multi currency, easy to use and payments are instant and free.

== Where can I find out more about Verse? ==

Here is a list of Verse resources:

* [https://verse.me/ Verse website]
* [https://twitter.com/joinverse/ Verse Twitter]
* [https://verse.me/en/terms Verse T&Cs]
* [https://verse.me/en/faq/ Verse FAQs]

== What countries are available for Verse? ==

Verse operates in the following countries: Austria, Belgium, Denmark, Finland, France, Germany, Greece, Ireland, Italy, Poland, Portugal, Slovakia, Spain, Sweden, and The Netherlands.

== What currencies are available for Verse? ==

Verse supports the following currencies; EUR, SEK, HUF, DKK, PLN

You can change between currencies in the your Verse account. Your default currency is decided by your phone number's country code. You can switch currencies every time you make a payment (the currency menu is right above the amount you are paying) and the change will be made immediately.

There are no commissions when changing of currency, the current exchange rate (Visa mid-market) will be applied.

== What is the maximum trading duration for Verse? ==

The maximum trade time is 1 day. Generally Verse transfers will be completed instantly.

Users making withdrawals from Verse (sending funds to their bank account) should expect to wait anywhere from a few seconds to two business days (it depends on their bank).

== What is the maximum BTC limit for an Verse trade? ==

{{MaxTradeSizeBisq1}}.

== Is Verse a payment method that can be signed? ==

No, Verse accounts do not require signing.

== How do I set up a Verse account? ==

Get the app from https://verse.me

== How do I add Verse as a payment method in Bisq? ==

It is easy to add your Verse account to Bisq.

# Go to the top menu in Bisq and select Account.
# Then select National Currency Accounts.
# Click add new account
# Select Verse
# Complete the details
# Choose to use a custom account name this helps makes it easier for you to manage multiple payment methods in Bisq (this will be visible only to you, for example: Verse - Jan Janssen)
# Click save new account

To send payment to someone you need there verse user name (similar to [[Revolut]], it is created for you based on first and last name, some users have the option to change their username).

If you have more than one Verse account you wish to add to Bisq you can create different accounts for each.

Make sure all the details are correct when you add.

{{Admonition_Warn|Verse is a multiple currency payment method that can send and receive payment in EUR, SEK, HUF, DKK, PLN.

When setting up your Verse account in Bisq please make sure to include the username that matches your username in your Verse account. This will ensure that when you send funds they show from the correct account and when you receive funds they will be credited to your account.

Verse users are limited to sending or receiving €10,000 per year (or equivalent foreign currency amount) for accumulated payments made from or received into their payment account. This can be increased by Verse on request.}}

== How do I buy BTC with my Verse account? ==

You can buy BTC with Verse on Bisq in 2 waysː

# Make an offer to buy BTC on the EUR, SEK, HUF, DKK, or PLN market.
# Take an offer to buy BTC on the EUR, SEK, HUF, DKK, or PLN market.

When the offer is confirmed Bisq will provide you with the BTC Sellers Verse details for you to complete the payment. You should send payment immediately and confirm you have done so in Bisq by clicking 'payment started'.

If you have the option to include a payment reference please leave it blank. If your bank requires one, please just use your name that matches your bank account.

Once the BTC Seller receives your payment they will confirm in Bisq and your security deposit and your purchased trade amount will be available in your wallet.

{{Admonition_Warn|Please send payment only to the username provided by the BTC Seller in their Bisq account. Please leave the payment description blank.

Verse users are limited to sending or receiving €10,000 per year (or equivalent foreign currency amount) for accumulated payments made from or received into their payment account. This can be increased by Verse on request.}}

== How do I sell BTC with my Verse account? ==

You can sell BTC with Verse on Bisq in 2 waysː

# Make an offer to sell BTC on the EUR, SEK, HUF, DKK, or PLN market.
# Take an offer to sell BTC on the EUR, SEK, HUF, DKK, or PLN market.

When the offer is confirmed Bisq will provide with the BTC Buyer with your Verse details for you to complete the payment. They should send payment at their first opportunity and confirm they have done so in Bisq by clicking 'payment started'.

Once you receive payment from the BTC Buyer you should confirm payment has been received in Bisq. One you have done this the BTC Buyer will receive their funds and you will receive your security deposit back.

{{Admonition_Warn|BTC Sellers should expect to receive payment from the username shown in the BTC Buyer's Bisq account.

Verse users are limited to sending or receiving €10,000 per year (or equivalent foreign currency amount) for accumulated payments made from or received into their payment account. This can be increased by Verse on request.}}

== Are there any limits for me to be aware of when using my Verse account? ==

€10,000 per year (or equivalent foreign currency amount) for accumulated payments made from or received into their payment account. Can be increased on request.

== Are there any fees for me to be aware of when using my Verse account? ==

Free. For payment operations that involve currency conversion and currency exchange services, the exchange rate will be calculated based on the currency sale or purchase rates, as applicable, by Visa International

== How does dispute resolution when trading with Verse? ==

If a dispute occurs the mediator may ask the buyer to send them information showing that they made the payment of the correct amount to the BTC Seller within the correct time frame.

The mediator may ask the seller to send them information to prove their account details are correct, or in the case of the BTC Buyer making a payment late, or of the wrong amount.

For more information see [[dispute resolution]].

Payment methods

2026-02-17T11:21:01Z

SuddenWhipVapor: /* Fiat payment methods */ removed Verse, as it is discontinued

<languages/>
<translate>Bisq offers several '''payment methods''' to buy and sell bitcoin for fiat currencies or other cryptocurrencies.

{{Admonition_Note|'''Version Context:''' The details on this page, particularly regarding trade limits and account signing, primarily apply to trading on '''[[Bisq 1|Bisq v1]]'''.}}

Every offer on Bisq designates a payment method for traders to settle payments. The Bisq software does not actually integrate with any payment methods—'''all non-bitcoin fund transfers are made outside of Bisq software'''.

Unlike cryptocurrency transfers, many fiat payment transfers have limitations that require Bisq [[Bisq 1|v1]] to employ special measures like lower per-trade limits and [[Account_limits#Account_signing|account signing]] to encourage fair trades.

__TOC__

== Fiat payment methods ==

Fiat payment methods vary significantly in characteristics like chargeback risk, regional availability, transaction limits, fees, privacy, and verification speed. The primary consideration for supporting a method on Bisq is '''chargeback risk'''. Methods with easy chargebacks (like PayPal, Venmo, Cash App) are generally not supported.

Suggestions for new payment methods, especially those enabling new markets, are welcome. See the criteria and process for adding methods [https://github.com/bisq-network/growth/issues/new?assignees=&labels=re%3Apayment-method&template=add_payment_method.md&title= here on GitHub], or discuss them on [https://bisq.chat Matrix] in the #payment-methods channel.

Below is a list of fiat payment methods currently supported in Bisq v1.

'''Note on Signing Requirement:''' Methods marked with an asterisk (*) '''do not''' require [[Account_limits#Account_signing|account signing]] to lift the initial low buying limit. All other listed fiat methods generally require signing.

'''Note on Trade Limits:''' The maximum trade sizes listed below may not be available immediately for new payment accounts. Please refer to [[Account_limits]] for details on account aging and signing required to enable larger trade sizes.

{| class="wikitable sortable"
|+ Supported Fiat Payment Methods (Bisq v1)
|-
! Payment Method [* = Signing Not Required] !! Region !! Trading Period !! Per-Trade Limit (BTC) !! Notes
|-
| [[ACH]]* || USA || 5 days || 0.0625 ||
|-
| Advanced Cash* || Global (BRL, EUR, GBP, KZT, RUB, UAH, USD) || 1 day || 0.5 || Not available in the USA.
|-
| Alipay* || China || 1 day || 0.25 ||
|-
| [[Amazon_eGift_card|Amazon eGift Card]]* || Global (AUD, CAD, EUR, GBP, INR, JPY, SAR, SEK, SGD, TRY, USD) || 1 day || 0.0625 || Check supported markets in [[Amazon_eGift_card|article]].
|-
| Australian PayID* || Australia || 1 day || 0.25 ||
|-
| [[Bizum]]* || Spain|| 1 day || 0.02 || Bizum limits: ~1000 EUR/trade, ~2000 EUR/day.
|-
| [[Capitual]]* || Global (BRL, EUR, GBP, USD) || 1 day || 0.0625 ||
|-
| [[Cash by Mail]]* || Global || 8 days || 0.0625 || Follow [[Cash_by_Mail|instructions carefully]].
|-
| Cash Deposit* || Global || 4 days || 0.0625 || Check if payee bank allows 3rd party deposits.
|-
| [[CelPay]]* || Global (AUD, CAD, GBP, HKD, USD) || 1 day || 0.0625 || CelPay limit: ~$2,500/day.
|-
| Domestic Wire Transfer* || USA || 3 days || 0.0625 ||
|-
| [[Face-to-face_(payment_method)|Face-to-Face (F2F)]]* || Global || 4 days || 0.25 || See [[Face-to-face_(payment_method)|F2F article]] for guidance.
|-
| [[Faster Payments]]* || UK || 1 day || 0.0625 || See [[Faster_Payments|article]] for usage notes.
|-
| [[Faster_Payments_System_SBP|Faster Payments System (SBP)]]* || Russia || 1 day || 0.05 ||
|-
| HalCash* || Spain || 1 day || 0.25 ||
|-
| [[IMPS]]* || India || 1 day || 0.0625 || IMPS limit: ~1,000,000 INR/day.
|-
| Interac-e-Transfer || Canada || 1 day || 0.0625 || Interac Autodeposit is '''not''' supported.
|-
| Japan Zengin Furikomi* || Japan || 1 day || 0.25 ||
|-
| MercadoPago || Argentina || 1 day || 0.0625 ||
|-
| [[Monese]]* || Europe (GBP, EUR, RON) || 1 day || 0.0625 ||
|-
| MoneyBeam (N26) || Europe || 1 day || 0.0625 ||
|-
| MoneyGram* || Global || 4 days || 0.125 ||
|-
| National Bank Transfer || Global || 4 days || 0.0625 ||
|-
| [[Nequi]]*|| Colombia || 1 day || 0.0625 || Nequi limit: ~7,000,000 COP/month.
|-
| [[NEFT]]* || India || 1 day || 0.10 || NEFT limit: ~50,000 INR/transaction.
|-
| [[Paxum]]* || Global || 1 day || 0.0625 ||
|-
| [[Paysera]]* || Global || 1 day || 0.0625 ||
|-
| [[PayTM]]* || India || 1 day || 0.0250 || PayTM limit: ~100,000 INR/transaction.
|-
| Perfect Money* || Global || 1 day || 0.25 ||
|-
| [[Pix]]*|| Brazil || 1 day || 0.0625 ||
|-
| Popmoney || USA || 1 day || 0.0625 ||
|-
| PromptPay* || Thailand || 1 day || 0.25 ||
|-
| [[Revolut]] || Global || 1 day || 0.0625 || See [[Revolut|article]] for usage notes.
|-
| [[RTGS]]* || India || 1 day || 0.10 || RTGS limits: Min 200,000 INR, Max 1,000,000 INR/transaction.
|-
| [[Satispay]]* || Italy || 1 day || 0.0625 ||
|-
| [[SEPA]] || Europe || 6 days || 0.0625 ||
|-
| [[SEPA Instant]] || Europe || 1 day || 0.0625 ||
|-
| [[Strike]]* || USA || 1 day || 0.0625 || Non-KYC Strike users have lower limits.
|-
| [[SWIFT]]* || Global || 7 days || 0.125 ||
|-
| Swish* || Sweden || 1 day || 0.25 ||
|-
| [[Tikkie]]* || The Netherlands || 1 day || 0.0250 || Tikkie limit: ~2500 EUR/24 hours.
|-
| Transfer with Same Bank || Global || 2 days || 0.0625 ||
|-
| Transfer from Specific Banks || Global || 4 days || 0.0625 ||
|-
| [[US Postal Money Order]]* || USA || 8 days || 0.0625 || USPS limits: Max 1000 USD/order, check daily limits.
|-
| Uphold || Global || 1 day || 0.0625 ||
|-
| [[UPI]]* || India || 1 day || 0.0250 || UPI limit: ~100,000 INR/transaction.
|-
| WeChat Pay* || China || 1 day || 0.25 ||
|-
| Western Union || Global || 4 days || 0.125 ||
|-
| [[Wise]]* || Global ('''non-USD''' trades) || 4 days || 0.0625 ||
|-
| [[Wise-USD]]* || Global ('''USD''' trades) || 4 days || 0.0625 ||
|-
| [[Zelle]] || USA || 4 days || 0.0625 || Check your bank's Zelle support & limits.
|}
=== Payment method guides ===

<gallery mode="packed" heights="150px">
File:Payment-methods-advice-eur.png|EUR payment methods overview.
File:Payment-methods-advice-usd.png|USD payment methods overview.
</gallery>

== Altcoin payment methods ==

Bisq also supports trading Bitcoin against various cryptocurrencies, like XMR, ETH, ZEC, L-BTC or LTC. A full list is available on the [https://bisq.network/markets/ Bisq Network Markets page].

Because cryptocurrency transfers are generally irreversible and fast, altcoin trades usually have higher limits (up to 0.5 BTC) available immediately, without the need for account aging or signing required for many fiat methods.

{| class="wikitable"
|+ Supported Altcoin Payment Methods (Bisq v1)
|-
! Payment Method !! Trading Period !! Per-Trade Limit (BTC)
|-
| [[Altcoins]] || 1 day || 0.5
|-
| [[Altcoins Instant]] || 1 hour || 0.5
|}

'''Warning for Instant Trades:''' Altcoins Instant trades require quick confirmation (within 1 hour). Remember to disable any open Instant offers (via `Portfolio` > `My Open Offers`) if you might be unavailable to complete the trade promptly.

See the general Account setup process within Bisq for adding altcoin accounts.

[[Category:Features]]
</translate>

Account limits

2026-02-12T12:24:13Z

SuddenWhipVapor: /* With your own signed account */

Elevated '''account limits''' apply to fiat payment accounts in order to limit damage a malicious user can do while allowing honest users to start trading immediately with no KYC and utmost privacy.

Altcoin accounts can trade 0.5 BTC right away, but all fiat payment account types have limits lower than 0.5 BTC to match their particular risk profiles (see [[Payment_methods#Fiat_payment_methods|this table]] for details). Some payment methods with chargeback risk implement a mechanism called ''account signing'' that restricts trading activity until a trader proves their integrity to further secure against foul play.

To reduce the size of trades entering arbitration Bisq also sets new users trade limits to be 0.1 BTC. This is an additional limit to account limits but users can opt out of this limit at any time.

__TOC__

== Which payment accounts are affected ==

Only fiat payment methods are affected by elevated account limits. Altcoin accounts are only affected by the new user limits which can be opted out if necessary for allow every altcoin account to trade up to 0.5 BTC right away upon creating a payment account in Bisq.

All fiat payment methods in all markets limit total trade size depending on the payment method's risk profile (see [[Payment_methods#Fiat_payment_methods|this table]] for details).

Despite these limitations, chargebacks can still be possible for certain payment methods. Bisq reduces this risk with a mechanism called '''account signing'''.

Account signing only applies to payment accounts that meet ''both'' of the following conditions:
* used in the following markets: USD, EUR, CAD, GBP, AUD, or BRL
* is subject to chargeback risk: SEPA, SEPA Instant, Interac e-Transfer, Zelle, Revolut, Chase QuickPay, Popmoney, MoneyBeam, Uphold, and any kind of bank transfer

This means that all payment accounts that deal in currencies not listed above do ''not'' require account signing, even if they are subject to chargeback risk.

== Account aging ==

[[File:See-account-age.png|400px|thumb|See account age in the offer book.]]

Account age is no longer used to determine trade size limits for most payment methods. It is still measured, however, and you can see a payment account's age in the offer book before taking an offer, but we caution against using it as a measure of integrity. Older accounts are not ''necessarily'' safer.

'''Practically, this means that all payment methods on Bisq have full selling capability from the moment they are created.''' Selling limits no longer phase in over time.

Some payment methods implement a variation of account aging called account signing whereby limits are increased in stages over a period of 60 days after signing. More about this below.

If you're interested, details on the <code>AccountAgeWitness</code> object that enables this aging mechanism are [https://docs.bisq.network/payment-account-age-witness.html here].

== Account signing ==

[[File:Account-signing-overview.png|thumb|right|A graphical overview of account signing.]]

Account signing limits ''buying'' limits of risky fiat payment methods to {{MaxTradeSizeUnsigned}} until the trader has bought bitcoin from a seller with a signed payment account, and then gradually phases in full buying limits. Selling limits are unaffected.

In a nutshell, this is how it works:
* Payment account is created in Bisq for risky payment method
** Buying is limited to {{MaxTradeSizeUnsigned}} BTC per trade until account is signed (see how [[#How_to_get_an_account_signed|below]])
* 30 days after signing, buying limits are increased to 50% of maximum
* 60 days after signing, maximum trade size is allowed

Let's see how this works in practice by looking at an example. SEPA has a maximum trade size of 0.0624 BTC, and it requires account signing in order for to enable full trade limits.

First let's observe what happens if a new SEPA account is never signed. Notice how buying limits never increase beyond {{MaxTradeSizeUnsigned}}, but selling 0.0624 BTC is allowed from day 0.

{| class="wikitable"
! Time Since Creating SEPA Payment Account (Never Signed)
! Maximum Trade Size (Buy)
! Maximum Trade Size (Sell)
|-
| Day 0
| {{MaxTradeSizeUnsigned}}
| 0.0624 BTC
|-
| Day 30
| {{MaxTradeSizeUnsigned}}
| 0.0624 BTC
|-
| Day 60
| {{MaxTradeSizeUnsigned}}
| 0.0624 BTC
|-
| Day 90
| {{MaxTradeSizeUnsigned}}
| 0.0624 BTC
|}

If that SEPA account manages to get signed on the same day it's created, it will see its {{MaxTradeSizeUnsigned}} limit increased on Day 30. Selling limits are unaffected.

{| class="wikitable"
! Time Since Creating SEPA Payment Account
! Maximum Trade Size (Buy)
! Maximum Trade Size (Sell)
|-
| Day 0 - Account Signed
| {{MaxTradeSizeUnsigned}}
| 0.0624 BTC
|-
| Day 30
| 0.03125 BTC
| 0.0624 BTC
|-
| Day 60
| 0.0624 BTC
| 0.0624 BTC
|-
| Day 90
| 0.0624 BTC
| 0.0624 BTC
|}

But if that SEPA account isn't signed until Day 30, it won't see its limits lifted until Day 60. Again, selling limits are unaffected.

{| class="wikitable"
! Time Since Creating SEPA Payment Account
! Maximum Trade Size (Buy)
! Maximum Trade Size (Sell)
|-
| Day 0
| {{MaxTradeSizeUnsigned}}
| 0.0624 BTC
|-
| Day 30 - Account Signed
| {{MaxTradeSizeUnsigned}}
| 0.0624 BTC
|-
| Day 60
| 0.0325 BTC
| 0.0624 BTC
|-
| Day 90
| 0.0624 BTC
| 0.0624 BTC
|}

=== How to get an account signed ===

Payment accounts that require signing cannot buy more than {{MaxTradeSizeUnsigned}} until 30 days ''after'' they are signed. Accounts can be signed with the following two methods.

==== Buying BTC ====
To sign your account you have to buy BTC following these requirements:
* trade amount is greater than or equal to {{MinTradeSizeToBeSigned}} BTC and lesser than or equal to {{MaxTradeSizeUnsigned}}
* offer must be in a market that requires signing (USD, EUR, CAD, GBP, AUD, BRL)
* seller's account must have been signed for over 30 days at the time of the signing trade

Through taking an offer you can make sure that the offer fulfills the requirements to sign your account. Making an offer could not sign your account, because taker could be unable to sign your account (signed since less than 30 days, or unsigned).

The Bisq interface makes it easy to determine if an offer can help you get signed: simply '''look for buy offers with a check mark badge''':

[[File:Good-bad-signing-asks.png|600px|thumb|left|Top offer won't get you signed. Bottom offer will get you signed.]]

<div style="clear: both;"></div>

In the image above, the offer on top does not have a check mark, but the offer on the bottom does. And it's a valid size (i.e., between {{MinTradeSizeToBeSigned}} BTC and {{MaxTradeSizeUnsigned}}), so taking that offer and successfully completing the trade will result in a signed account.

You can see your payment account's limits and signing status at <code>Accounts</code> > <code>National Currency Accounts</code>. Pick an account and look toward the bottom:

[[File:Payment-account-signing-status.png|600px|thumb|left|Where to see your payment account's limits and signing status.]]

<div style="clear: both;"></div>

==== With your own signed account ====

Once you have a signed and fully matured payment account, any new payment account you create after it, that requires signing, will be self-signed as long as it uses the '''exact same name''' as your previously signed account. The payment account can be of a different type (e.g. a signed SEPA account can self-sign a SEPA Instant account), but a payment account created with a name that is even slightly different will not be self-signed.

Payment account types that don't require your full name cannot be self-signed (e.g. Revolut, which only requires an email address) and they cannot self-sign other payment accounts.

Self-signed accounts are immediately signed, but limits are not immediately lifted. This is because they have an age of 0 days, so 30 days must pass for the {{MaxTradeSizeUnsigned}} limit to be lifted, and another 30 days must pass for full trading ability to take effect (see tables above).

== Backing up and restoring payment accounts ==

Once your payment accounts have accrued age and been signed, you won't want to give them up. With [[Backing_up_application_data|proper backups]], you won't have to—payment accounts can be restored if you ever have to remove/reinstall Bisq, move to another machine, etc.

== User opt-out limits ==

To reduce trades into arbitration for new users unfamiliar with Bisq, new users have a 0.1 BTC limit by default that can be opt-out of at any time.

To access this limit go to Settings > Preferences

[[File:Trade limits.png|frameless|left|Trade limit setting in Bisq that can opted out of or changed at any time]]

Shown above is the trade limit setting in Bisq that can opted out of or edited higher or lower at any time.

If you opt of of this limit you will be given a pop up message informing you...

{{Admonition_Warn|Trading limits are set to reduce risk of costly disputes and losing funds for new users. Raise trading limits at your own risk. Every trader has their own pace, but it's recommended to complete at least 5 trades before raising trade limits.

By raising trading limits you acknowledge to be familiar with the basic use of Bisq, like [[Backing_up_application_data|backing up your data]], [[rading_rules|trading rules]], [[Dispute_resolution|dispute resolution]], [[Table_of_penalties|penalties]] and [[User_support|where to find support]].}}

Account signing limits are still applied to buy BTC with most National Account payment methods to reduce chargeback risk.

Backup

2025-12-14T18:22:15Z

SuddenWhipVapor:

= Backup strategies=

== Manual backup ==

Bisq1 has a manually triggered backup feature that saves a copy of the whole contents of the data directory to a selected location: [[backing up application data]]

Bisq2 has a very similar feature that can be reached under Support > Resources > Backup, and works in a similar manner.

== Built-in automatic backup ==

Bisq2 extends the existing manual backup, and also provides a feature to create versioned backups: [[automatic backup]]

== Custom automatic backup scripts ==

A standalone script is also available to create versioned backups on Windows, MacOS and Linux, of the essential database files of both Bisq1 and Bisq2: [[automatic backup script]]

Backup

2025-12-14T18:21:44Z

SuddenWhipVapor:

= Backup strategies=

== Manual backup ==

Bisq1 has a manually triggered backup feature that saves a copy of the whole contents of the data directory to a selected location: [[backing up application data]]

Bisq2 has a very similar feature that can be reached under Support > Resources > Backup, and works in a similar manner.

== Built-in automatic backup ==

Bisq2 extends the existing manual backup, and also provides a feature to create versioned backups: [[automatic backups]]

== Custom automatic backup scripts ==

A standalone script is also available to create versioned backups on Windows, MacOS and Linux, of the essential database files of both Bisq1 and Bisq2: [[automatic backup script]]

Backup

2025-12-14T18:21:06Z

SuddenWhipVapor:

= Backup strategies=

== Manual backup ==

Bisq1 has a manually triggered backup feature that saves a copy of the whole contents of the data directory to a selected location: [[backing up application data]]

Bisq2 has a very similar feature that can be reached under Support > Resources > Backup, and works in a similar manner.

== Builtin automatic backup ==

Bisq2 builds on top of the existing manual backup, and also provides a feature to create versioned backups: [[automatic backups]]

== Custom automatic backup scripts ==

A standalone script is also available to create versioned backups on Windows, MacOS and Linux, of the essential database files of both Bisq1 and Bisq2: [[automatic backup script]]

Backup

2025-12-14T18:20:32Z

SuddenWhipVapor:

= Backup strategies=

== Manual backup ==

Bisq1 has a manually triggered backup feature that saves a copy of the whole contents of the data directory to a selected location: [[backing up application data]]

Bisq2 has a very similar feature that can be reached under Support > Resources > Backup, and works in a similar manner

== Builtin automatic backup ==

Bisq2 builds on top of the existing manual backup, and also provides a feature to create versioned backups: [[automatic backups]]

== Custom automatic backup scripts ==

A standalone script is also available to create versioned backups on Windows, MacOS and Linux, of the essential database files of both Bisq1 and Bisq2: [[automatic backup script]]

Backup

2025-12-14T18:20:01Z

SuddenWhipVapor: stump

= Backup strategies=

== Manual backup ==

Bisq1 has a manually triggered backup feature that saves a copy of the whole contents of the data directory to a selected location: [[backing up application data]]
Bisq2 has a very similar feature that can be reached under Support > Resources > Backup, and works in a similar manner

== Builtin automatic backup ==

Bisq2 builds on top of the existing manual backup, and also provides a feature to create versioned backups: [[automatic backups]]

== Custom automatic backup scripts ==

A standalone script is also available to create versioned backups on Windows, MacOS and Linux, of the essential database files of both Bisq1 and Bisq2: [[automatic backup script]]

Automatic backup

2025-12-14T18:07:41Z

SuddenWhipVapor: add screenshot

The Bisq application automatically creates a backup whenever a data storage file is updated. Recent backups are retained more densely, while older ones are gradually thinned out. This approach maintains a good balance between storage usage and ensuring that sufficiently recent backups are available when needed.

Backup snapshots are created on every write (the backup filename is the store filename plus the timestamp format <code>yyyy-MM-dd_HHmm</code>) and are grouped by the store’s parent filename.
[[File:Resources automatic backup.png|thumb]]

The system keeps backup snapshots based on the following rules and the <code>MaxBackupSize</code> (default 100MB):

*Last hour: a snapshot every minute
*Past hour → 24 hours: the most recent snapshot from each hour is kept
*Past day → 7 days: the most recent snapshot from each day is kept
*Past week → 28 days: the most recent snapshot from each week is kept
*Past month → 1 year: the most recent snapshot from each month is kept
*Older than a year: the most recent snapshot from each year is kept

File:Resources automatic backup.png

2025-12-14T18:06:46Z

SuddenWhipVapor:

automatic backup & retention system page

Automatic backup

2025-12-14T18:04:02Z

SuddenWhipVapor: fix title format

=== Bisq2 automatic backup & retention system ===

The Bisq application automatically creates a backup whenever a data storage file is updated. Recent backups are retained more densely, while older ones are gradually thinned out. This approach maintains a good balance between storage usage and ensuring that sufficiently recent backups are available when needed.

Backup snapshots are created on every write (the backup filename is the store filename plus the timestamp format <code>yyyy-MM-dd_HHmm</code>) and are grouped by the store’s parent filename.

The system keeps backup snapshots based on the following rules and the <code>MaxBackupSize</code> (default 100MB):

*Last hour: a snapshot every minute\n\
*Past hour → 24 hours: the most recent snapshot from each hour is kept
*Past day → 7 days: the most recent snapshot from each day is kept
*Past week → 28 days: the most recent snapshot from each week is kept
*Past month → 1 year: the most recent snapshot from each month is kept
*Older than a year: the most recent snapshot from each year is kept

Automatic backup

2025-12-14T18:03:15Z

SuddenWhipVapor: Stump created

= Bisq2 automatic backup & retention system =

The Bisq application automatically creates a backup whenever a data storage file is updated. Recent backups are retained more densely, while older ones are gradually thinned out. This approach maintains a good balance between storage usage and ensuring that sufficiently recent backups are available when needed.

Backup snapshots are created on every write (the backup filename is the store filename plus the timestamp format <code>yyyy-MM-dd_HHmm</code>) and are grouped by the store’s parent filename.

The system keeps backup snapshots based on the following rules and the <code>MaxBackupSize</code> (default 100MB):

*Last hour: a snapshot every minute\n\
*Past hour → 24 hours: the most recent snapshot from each hour is kept
*Past day → 7 days: the most recent snapshot from each day is kept
*Past week → 28 days: the most recent snapshot from each week is kept
*Past month → 1 year: the most recent snapshot from each month is kept
*Older than a year: the most recent snapshot from each year is kept

Finding your arbitrator

2025-11-11T09:15:59Z

SuddenWhipVapor: /* Matrix and onion addresses */ updated RA2 matrix handle

Here is a list of current Bisq arbitrators and their onion addresses, as well as how you can find the arbitrator for a specific Bisq trade.

If you need to find your mediator see [[Finding your mediator|here]].

__TOC__

= Get in touch with your arbitrator =

For open trades, you should be able to get in touch with your arbitrator through Bisq arbitration chat itself.

If you cannot get in touch with your arbitrator on Bisq for 72 hours (sometimes Bisq message system fails), or the issue needs urgent attention, you can get in touch with them on the [[Matrix bisq.chat]] group. Their Matrix handles and onion addresses are displayed in the headline for the #support channel as well.

= How to find the arbitrator for a trade =

== In Bisq 1 ==

=== System message ===

Go to 'Support > Arbitration' tab since arbitration begins.

=== View contract in JSON ===

Alternatively, you can look for your arbitrator since the trade starts:

# Go to <code>Portfolio > Open Trades</code>, <code>Portfolio > History</code>, or <code>Portfolio > Failed Trades</code> (depending on the status of your trade)
# Click the <code>i</code> icon next to the trade ID of the trade in question (it's on the very left in the first column)
# In the pop-up that appears, toward the bottom, click <code>View Contract in JSON Format</code>.
# Scroll down and you'll find <code>"refundAgentNodeAddress"</code> it is just below <code>"lockTime"</code> after the refundAgentNodeAddress you will see your arbitrators's onion address.

This is the onion address of the arbitrator for your trade.

= Matrix and onion addresses =

{| class="wikitable"
! Arbitrator
! TorV3 Address
! GitHub Handle
! Matrix Handle
|-
| refundagent2
| 3z5jnirlccgxzoxc6zwkcgwj66bugvqplzf6z2iyd5oxifiaorhnanqd.onion:9999
| [https://github.com/refund-agent2 refund-agent2]
| [[Matrix bisq.chat | @refund-agent2:envs.net]]
|-
| refundagent3
| yjlcxr6rho6zkpecwdp3vlpduzcl7i6cbgaquvxqmvsbw3dnheus6qad.onion:9999
| [https://github.com/refundagent3 refundagent3]
| [[Matrix bisq.chat | @refundagent3:imagisphe.re]]
|}

[[Category:Use Cases]]

Account limits

2025-11-07T12:57:30Z

SuddenWhipVapor: /* How to get an account signed */ better wording

Elevated '''account limits''' apply to fiat payment accounts in order to limit damage a malicious user can do while allowing honest users to start trading immediately with no KYC and utmost privacy.

Altcoin accounts can trade 0.5 BTC right away, but all fiat payment account types have limits lower than 0.5 BTC to match their particular risk profiles (see [[Payment_methods#Fiat_payment_methods|this table]] for details). Some payment methods with chargeback risk implement a mechanism called ''account signing'' that restricts trading activity until a trader proves their integrity to further secure against foul play.

To reduce the size of trades entering arbitration Bisq also sets new users trade limits to be 0.1 BTC. This is an additional limit to account limits but users can opt out of this limit at any time.

__TOC__

== Which payment accounts are affected ==

Only fiat payment methods are affected by elevated account limits. Altcoin accounts are only affected by the new user limits which can be opted out if necessary for allow every altcoin account to trade up to 0.5 BTC right away upon creating a payment account in Bisq.

All fiat payment methods in all markets limit total trade size depending on the payment method's risk profile (see [[Payment_methods#Fiat_payment_methods|this table]] for details).

Despite these limitations, chargebacks can still be possible for certain payment methods. Bisq reduces this risk with a mechanism called '''account signing'''.

Account signing only applies to payment accounts that meet ''both'' of the following conditions:
* used in the following markets: USD, EUR, CAD, GBP, AUD, or BRL
* is subject to chargeback risk: SEPA, SEPA Instant, Interac e-Transfer, Zelle, Revolut, Chase QuickPay, Popmoney, MoneyBeam, Uphold, and any kind of bank transfer

This means that all payment accounts that deal in currencies not listed above do ''not'' require account signing, even if they are subject to chargeback risk.

== Account aging ==

[[File:See-account-age.png|400px|thumb|See account age in the offer book.]]

Account age is no longer used to determine trade size limits for most payment methods. It is still measured, however, and you can see a payment account's age in the offer book before taking an offer, but we caution against using it as a measure of integrity. Older accounts are not ''necessarily'' safer.

'''Practically, this means that all payment methods on Bisq have full selling capability from the moment they are created.''' Selling limits no longer phase in over time.

Some payment methods implement a variation of account aging called account signing whereby limits are increased in stages over a period of 60 days after signing. More about this below.

If you're interested, details on the <code>AccountAgeWitness</code> object that enables this aging mechanism are [https://docs.bisq.network/payment-account-age-witness.html here].

== Account signing ==

[[File:Account-signing-overview.png|thumb|right|A graphical overview of account signing.]]

Account signing limits ''buying'' limits of risky fiat payment methods to {{MaxTradeSizeUnsigned}} until the trader has bought bitcoin from a seller with a signed payment account, and then gradually phases in full buying limits. Selling limits are unaffected.

In a nutshell, this is how it works:
* Payment account is created in Bisq for risky payment method
** Buying is limited to {{MaxTradeSizeUnsigned}} BTC per trade until account is signed (see how [[#How_to_get_an_account_signed|below]])
* 30 days after signing, buying limits are increased to 50% of maximum
* 60 days after signing, maximum trade size is allowed

Let's see how this works in practice by looking at an example. SEPA has a maximum trade size of 0.0624 BTC, and it requires account signing in order for to enable full trade limits.

First let's observe what happens if a new SEPA account is never signed. Notice how buying limits never increase beyond {{MaxTradeSizeUnsigned}}, but selling 0.0624 BTC is allowed from day 0.

{| class="wikitable"
! Time Since Creating SEPA Payment Account (Never Signed)
! Maximum Trade Size (Buy)
! Maximum Trade Size (Sell)
|-
| Day 0
| {{MaxTradeSizeUnsigned}}
| 0.0624 BTC
|-
| Day 30
| {{MaxTradeSizeUnsigned}}
| 0.0624 BTC
|-
| Day 60
| {{MaxTradeSizeUnsigned}}
| 0.0624 BTC
|-
| Day 90
| {{MaxTradeSizeUnsigned}}
| 0.0624 BTC
|}

If that SEPA account manages to get signed on the same day it's created, it will see its {{MaxTradeSizeUnsigned}} limit increased on Day 30. Selling limits are unaffected.

{| class="wikitable"
! Time Since Creating SEPA Payment Account
! Maximum Trade Size (Buy)
! Maximum Trade Size (Sell)
|-
| Day 0 - Account Signed
| {{MaxTradeSizeUnsigned}}
| 0.0624 BTC
|-
| Day 30
| 0.03125 BTC
| 0.0624 BTC
|-
| Day 60
| 0.0624 BTC
| 0.0624 BTC
|-
| Day 90
| 0.0624 BTC
| 0.0624 BTC
|}

But if that SEPA account isn't signed until Day 30, it won't see its limits lifted until Day 60. Again, selling limits are unaffected.

{| class="wikitable"
! Time Since Creating SEPA Payment Account
! Maximum Trade Size (Buy)
! Maximum Trade Size (Sell)
|-
| Day 0
| {{MaxTradeSizeUnsigned}}
| 0.0624 BTC
|-
| Day 30 - Account Signed
| {{MaxTradeSizeUnsigned}}
| 0.0624 BTC
|-
| Day 60
| 0.0325 BTC
| 0.0624 BTC
|-
| Day 90
| 0.0624 BTC
| 0.0624 BTC
|}

=== How to get an account signed ===

Payment accounts that require signing cannot buy more than {{MaxTradeSizeUnsigned}} until 30 days ''after'' they are signed. Accounts can be signed with the following two methods.

==== Buying BTC ====
To sign your account you have to buy BTC following these requirements:
* trade amount is greater than or equal to {{MinTradeSizeToBeSigned}} BTC and lesser than or equal to {{MaxTradeSizeUnsigned}}
* offer must be in a market that requires signing (USD, EUR, CAD, GBP, AUD, BRL)
* seller's account must have been signed for over 30 days at the time of the signing trade

Through taking an offer you can make sure that the offer fulfills the requirements to sign your account. Making an offer could not sign your account, because taker could be unable to sign your account (signed since less than 30 days, or unsigned).

The Bisq interface makes it easy to determine if an offer can help you get signed: simply '''look for buy offers with a check mark badge''':

[[File:Good-bad-signing-asks.png|600px|thumb|left|Top offer won't get you signed. Bottom offer will get you signed.]]

<div style="clear: both;"></div>

In the image above, the offer on top does not have a check mark, but the offer on the bottom does. And it's a valid size (i.e., between {{MinTradeSizeToBeSigned}} BTC and {{MaxTradeSizeUnsigned}}), so taking that offer and successfully completing the trade will result in a signed account.

You can see your payment account's limits and signing status at <code>Accounts</code> > <code>National Currency Accounts</code>. Pick an account and look toward the bottom:

[[File:Payment-account-signing-status.png|600px|thumb|left|Where to see your payment account's limits and signing status.]]

<div style="clear: both;"></div>

==== With your own signed account ====

Once you have 1 signed payment account, any new payment account you create that requires signing will be self-signed as long as it uses the '''exact same name''' as your previously signed account. The payment account can be of a different type (e.g. a signed SEPA account can self-sign a SEPA Instant account), but a payment account created with a name that is even slightly different will not be self-signed.

Payment account types that don't require your full name cannot be self-signed (e.g. Revolut, which only requires an email address) and they cannot self-sign other payment accounts.

Self-signed accounts are immediately signed, but limits are not immediately lifted. This is because they have an age of 0 days, so 30 days must pass for the {{MaxTradeSizeUnsigned}} limit to be lifted, and another 30 days must pass for full trading ability to take effect (see tables above).

== Backing up and restoring payment accounts ==

Once your payment accounts have accrued age and been signed, you won't want to give them up. With [[Backing_up_application_data|proper backups]], you won't have to—payment accounts can be restored if you ever have to remove/reinstall Bisq, move to another machine, etc.

== User opt-out limits ==

To reduce trades into arbitration for new users unfamiliar with Bisq, new users have a 0.1 BTC limit by default that can be opt-out of at any time.

To access this limit go to Settings > Preferences

[[File:Trade limits.png|frameless|left|Trade limit setting in Bisq that can opted out of or changed at any time]]

Shown above is the trade limit setting in Bisq that can opted out of or edited higher or lower at any time.

If you opt of of this limit you will be given a pop up message informing you...

{{Admonition_Warn|Trading limits are set to reduce risk of costly disputes and losing funds for new users. Raise trading limits at your own risk. Every trader has their own pace, but it's recommended to complete at least 5 trades before raising trade limits.

By raising trading limits you acknowledge to be familiar with the basic use of Bisq, like [[Backing_up_application_data|backing up your data]], [[rading_rules|trading rules]], [[Dispute_resolution|dispute resolution]], [[Table_of_penalties|penalties]] and [[User_support|where to find support]].}}

Account signing limits are still applied to buy BTC with most National Account payment methods to reduce chargeback risk.

Payment methods

2025-10-31T16:15:45Z

SuddenWhipVapor: remove interac e-transfer link

<languages/>
<translate>Bisq offers several '''payment methods''' to buy and sell bitcoin for fiat currencies or other cryptocurrencies.

{{Admonition_Note|'''Version Context:''' The details on this page, particularly regarding trade limits and account signing, primarily apply to trading on '''[[Bisq 1|Bisq v1]]'''.}}

Every offer on Bisq designates a payment method for traders to settle payments. The Bisq software does not actually integrate with any payment methods—'''all non-bitcoin fund transfers are made outside of Bisq software'''.

Unlike cryptocurrency transfers, many fiat payment transfers have limitations that require Bisq [[Bisq 1|v1]] to employ special measures like lower per-trade limits and [[Account_limits#Account_signing|account signing]] to encourage fair trades.

__TOC__

== Fiat payment methods ==

Fiat payment methods vary significantly in characteristics like chargeback risk, regional availability, transaction limits, fees, privacy, and verification speed. The primary consideration for supporting a method on Bisq is '''chargeback risk'''. Methods with easy chargebacks (like PayPal, Venmo, Cash App) are generally not supported.

Suggestions for new payment methods, especially those enabling new markets, are welcome. See the criteria and process for adding methods [https://github.com/bisq-network/growth/issues/new?assignees=&labels=re%3Apayment-method&template=add_payment_method.md&title= here on GitHub], or discuss them on [https://bisq.chat Matrix] in the #payment-methods channel.

Below is a list of fiat payment methods currently supported in Bisq v1.

'''Note on Signing Requirement:''' Methods marked with an asterisk (*) '''do not''' require [[Account_limits#Account_signing|account signing]] to lift the initial low buying limit. All other listed fiat methods generally require signing.

'''Note on Trade Limits:''' The maximum trade sizes listed below may not be available immediately for new payment accounts. Please refer to [[Account_limits]] for details on account aging and signing required to enable larger trade sizes.

{| class="wikitable sortable"
|+ Supported Fiat Payment Methods (Bisq v1)
|-
! Payment Method [* = Signing Not Required] !! Region !! Trading Period !! Per-Trade Limit (BTC) !! Notes
|-
| [[ACH]]* || USA || 5 days || 0.0625 ||
|-
| Advanced Cash* || Global (BRL, EUR, GBP, KZT, RUB, UAH, USD) || 1 day || 0.5 || Not available in the USA.
|-
| Alipay* || China || 1 day || 0.25 ||
|-
| [[Amazon_eGift_card|Amazon eGift Card]]* || Global (AUD, CAD, EUR, GBP, INR, JPY, SAR, SEK, SGD, TRY, USD) || 1 day || 0.0625 || Check supported markets in [[Amazon_eGift_card|article]].
|-
| Australian PayID* || Australia || 1 day || 0.25 ||
|-
| [[Bizum]]* || Spain|| 1 day || 0.02 || Bizum limits: ~1000 EUR/trade, ~2000 EUR/day.
|-
| [[Capitual]]* || Global (BRL, EUR, GBP, USD) || 1 day || 0.0625 ||
|-
| [[Cash by Mail]]* || Global || 8 days || 0.0625 || Follow [[Cash_by_Mail|instructions carefully]].
|-
| Cash Deposit* || Global || 4 days || 0.0625 || Check if payee bank allows 3rd party deposits.
|-
| [[CelPay]]* || Global (AUD, CAD, GBP, HKD, USD) || 1 day || 0.0625 || CelPay limit: ~$2,500/day.
|-
| Domestic Wire Transfer* || USA || 3 days || 0.0625 ||
|-
| [[Face-to-face_(payment_method)|Face-to-Face (F2F)]]* || Global || 4 days || 0.25 || See [[Face-to-face_(payment_method)|F2F article]] for guidance.
|-
| [[Faster Payments]]* || UK || 1 day || 0.0625 || See [[Faster_Payments|article]] for usage notes.
|-
| [[Faster_Payments_System_SBP|Faster Payments System (SBP)]]* || Russia || 1 day || 0.05 ||
|-
| HalCash* || Spain || 1 day || 0.25 ||
|-
| [[IMPS]]* || India || 1 day || 0.0625 || IMPS limit: ~1,000,000 INR/day.
|-
| Interac-e-Transfer || Canada || 1 day || 0.0625 || Interac Autodeposit is '''not''' supported.
|-
| Japan Zengin Furikomi* || Japan || 1 day || 0.25 ||
|-
| MercadoPago || Argentina || 1 day || 0.0625 ||
|-
| [[Monese]]* || Europe (GBP, EUR, RON) || 1 day || 0.0625 ||
|-
| MoneyBeam (N26) || Europe || 1 day || 0.0625 ||
|-
| MoneyGram* || Global || 4 days || 0.125 ||
|-
| National Bank Transfer || Global || 4 days || 0.0625 ||
|-
| [[Nequi]]*|| Colombia || 1 day || 0.0625 || Nequi limit: ~7,000,000 COP/month.
|-
| [[NEFT]]* || India || 1 day || 0.10 || NEFT limit: ~50,000 INR/transaction.
|-
| [[Paxum]]* || Global || 1 day || 0.0625 ||
|-
| [[Paysera]]* || Global || 1 day || 0.0625 ||
|-
| [[PayTM]]* || India || 1 day || 0.0250 || PayTM limit: ~100,000 INR/transaction.
|-
| Perfect Money* || Global || 1 day || 0.25 ||
|-
| [[Pix]]*|| Brazil || 1 day || 0.0625 ||
|-
| Popmoney || USA || 1 day || 0.0625 ||
|-
| PromptPay* || Thailand || 1 day || 0.25 ||
|-
| [[Revolut]] || Global || 1 day || 0.0625 || See [[Revolut|article]] for usage notes.
|-
| [[RTGS]]* || India || 1 day || 0.10 || RTGS limits: Min 200,000 INR, Max 1,000,000 INR/transaction.
|-
| [[Satispay]]* || Italy || 1 day || 0.0625 ||
|-
| [[SEPA]] || Europe || 6 days || 0.0625 ||
|-
| [[SEPA Instant]] || Europe || 1 day || 0.0625 ||
|-
| [[Strike]]* || USA || 1 day || 0.0625 || Non-KYC Strike users have lower limits.
|-
| [[SWIFT]]* || Global || 7 days || 0.125 ||
|-
| Swish* || Sweden || 1 day || 0.25 ||
|-
| [[Tikkie]]* || The Netherlands || 1 day || 0.0250 || Tikkie limit: ~2500 EUR/24 hours.
|-
| Transfer with Same Bank || Global || 2 days || 0.0625 ||
|-
| Transfer from Specific Banks || Global || 4 days || 0.0625 ||
|-
| [[US Postal Money Order]]* || USA || 8 days || 0.0625 || USPS limits: Max 1000 USD/order, check daily limits.
|-
| Uphold || Global || 1 day || 0.0625 ||
|-
| [[UPI]]* || India || 1 day || 0.0250 || UPI limit: ~100,000 INR/transaction.
|-
| [[Verse]]* || Europe (EUR, SEK, HUF, DKK, PLN) || 1 day || 0.0625 || Verse limit: ~10,000 EUR/year.
|-
| WeChat Pay* || China || 1 day || 0.25 ||
|-
| Western Union || Global || 4 days || 0.125 ||
|-
| [[Wise]]* || Global ('''non-USD''' trades) || 4 days || 0.0625 ||
|-
| [[Wise-USD]]* || Global ('''USD''' trades) || 4 days || 0.0625 ||
|-
| [[Zelle]] || USA || 4 days || 0.0625 || Check your bank's Zelle support & limits.
|}
=== Payment method guides ===

<gallery mode="packed" heights="150px">
File:Payment-methods-advice-eur.png|EUR payment methods overview.
File:Payment-methods-advice-usd.png|USD payment methods overview.
</gallery>

== Altcoin payment methods ==

Bisq also supports trading Bitcoin against various cryptocurrencies, like XMR, ETH, ZEC, L-BTC or LTC. A full list is available on the [https://bisq.network/markets/ Bisq Network Markets page].

Because cryptocurrency transfers are generally irreversible and fast, altcoin trades usually have higher limits (up to 0.5 BTC) available immediately, without the need for account aging or signing required for many fiat methods.

{| class="wikitable"
|+ Supported Altcoin Payment Methods (Bisq v1)
|-
! Payment Method !! Trading Period !! Per-Trade Limit (BTC)
|-
| [[Altcoins]] || 1 day || 0.5
|-
| [[Altcoins Instant]] || 1 hour || 0.5
|}

'''Warning for Instant Trades:''' Altcoins Instant trades require quick confirmation (within 1 hour). Remember to disable any open Instant offers (via `Portfolio` > `My Open Offers`) if you might be unavailable to complete the trade promptly.

See the general Account setup process within Bisq for adding altcoin accounts.

[[Category:Features]]
</translate>

Howto

2025-10-31T16:15:13Z

SuddenWhipVapor: remove interac e-transfer reference

List of short how-to guides for new Bisq users:

1. Getting started

*[[How to back up your Bisq wallet seed]]
*[[Set up a Revolut payment account]]
*[[Set up a SEPA payment account]] (EUR)
*[[Set up a Zelle payment account]] (USD)
*[[Set up a UK Faster Payments account]] (GBP)
*[[Set up a National bank transfer account]] (BRL)
*How to back up your payment accounts on Bisq

2. Trade

*[[How to buy BSQ on Bisq]]
*[[How to buy BTC on Bisq with EUR]]
*[[How to buy BTC on Bisq with CAD]]
*How to buy BTC on Bisq with USD
*[[How to buy ETH on Bisq]]
*[[How to buy USDT on Bisq]]
*[[How to buy XMR on Bisq]]
*[[How to buy BTC on Bisq with CNY]]
*[[How to buy BTC on Bisq with NGN]]
*[[How to buy BTC on Bisq with INR]]
*[[How to buy BTC on Bisq with ARS]]
*[[How to sell BSQ on Bisq]]
*[[How to sell BTC on Bisq with EUR]]
*How to sell BTC on Bisq with USD
*[[How to sell USDT on Bisq]]
*[[How to sell XMR on Bisq]]
*[[How to create an offer to buy BTC with EUR]]
*[[How to create an offer to sell BTC with EUR]]

3. Contribute
*[[How to be a market maker on Bisq]]
*[[How to do arbitrage on Bisq]]
*[[How to do remittance on Bisq]]
*Educational resources
*Marketing
*How to be a developer on Bisq
*How to make a compensation request on Bisq

4. DAO
*How to vote on the Bisq DAO
*How to make a proposal on the Bisq DAO

==Bitcoin Wisdom==
*DON'T TRUST. VERIFY.
*Trusted Third Parties are security holes.
*Not your keys, not your coins.
*Vires in numeris.

How to buy BTC on Bisq with CAD

2025-10-31T16:13:36Z

SuddenWhipVapor: remove interac e-transfer reference

First download, install Bisq and create a backup (copy seed words - see [[How to back up your Bisq wallet seed]]).

Make sure you have a fiat payment account set up.

1. On '''Market''' tab select CAD - Canadian Dollar

2. Click on '''BUY BTC'''.

3. Select an offer and click on '''TAKE OFFER'''.

4. Review offer details including amount, price. Then click on '''NEXT STEP'''.

5. Fund your trade (from Bisq wallet or external wallet).

6. Click on '''CONFIRM TAKE OFFER'''.

7. After 1 blockchain confirmation (~10 minutes) you will be prompted to initiate payment. Make a transfer to the seller using your fiat payment method, then click on '''PAYMENT STARTED'''.

8. When the seller confirms payment received the trade is complete and you can '''withdraw your BTC'''.

*For more short guides see [[Howto]]. You can also find support on '''[https://bisq.chat Matrix]'''.

Automatic backup script

2025-10-13T09:11:03Z

SuddenWhipVapor:

The biggest issues for users happen when data files are lost or corrupted, leading to missing or borked trades, or unrecoverable Delayed Payout Transactions.

Having an automated backup solution helps covering that risk, by removing the need to manually run a backup after every application state change (mainly "offer created", "trade started", "trade completed").

Issues could still happen when a critical event occurs right after a state change was saved to disk, and before an automated backup was taken, but there are strategies to mitigate that possibility, which will be discussed.

__TOC__

= Common requirements and backup strategy =

All scripts require 7z compression (7-zip on Windows, p7zip-full on Linux, p7zip on MacOS).

The provided code will backup all functional files in the data directory, leaving out non-unique files that the Bisq application will fetch/re-create autonomously, and compress them into a 7zip archive, keeping the number of last backups that you define, while deleting the oldest one(s) if the existing number of backups is higher.

It is advised that you direct the backups to either an external drive, or a NAS, or an encrypted cloud storage.

Depending on how bulletproof of a backup schedule you want, you can increase the number of backups to keep on disk to 10 or more (the size of each depends on the history of your instance, but it usually resides in a few tens of MB, often less) and the frequency the script runs with, for example every 1 or 2 hours.

= Bisq1 =

== Linux ==

Create a <code>scripts</code> folder in your <code>home</code> directory, prepare an executable file and open it with an editor:

<pre>
cd ~
mkdir -p scripts
cd scripts
touch bisq1backup
chmod +x bisq1backup
nano bisq1backup
</pre>

paste the following code in the file, and edit where needed:

<pre>
#!/bin/bash

# ==== EDIT THE FOLLOWING ====
SOURCE_DIR="/home/YOURUSERNAME/.local/share/Bisq/btc_mainnet"
TARGET_FOLDER="/mnt/BACKUPS/BISQ1"
BACKUP_COUNT=4
# ============================

ARCHIVE_ROOT="bisq1_backup_"
BACKUP_FILE="${ARCHIVE_ROOT}$(date +%Y%m%d_%H%M%S).7z"
ARCHIVE_PATH="${TARGET_FOLDER}/${BACKUP_FILE}"
SELECTED_FILES=(
"BsqSwapTrades"
"BallotList"
"DisputeList"
"RefundDisputeList"
"SequenceNumberMap"
"MyVoteList"
"OpenOffers"
"MyBlindVoteList"
"ClosedTrades"
"MediationDisputeList"
"MyProposalList"
"MailboxMessageList"
"AccountAgeWitnessStore"
"PendingTrades"
"MyProofOfBurnList"
"PreferencesPayload"
"UserPayload"
"AddressEntryList"
"FailedTrades"
"MyReputationList"
"TempProposalStore"
"NavigationPath"
"UnconfirmedBsqChangeOutputList"
"IgnoredMailboxMap"
"PeerList"
"RemovedPayloadsMap"
"TradeStatistics3Store"
"SignedWitnessStore"
)

FOLDER_KEYS="keys"
FOLDER_WALLET="wallet"
FOLDER_TOR="tor/hiddenservice"

FILE_LIST=$(mktemp)

SUBFOLDER_DB_PATH="$SOURCE_DIR/db"
for file in "${SELECTED_FILES[@]}"; do
if [ -f "$SUBFOLDER_DB_PATH/$file" ]; then
echo "$SUBFOLDER_DB_PATH/$file" >> "$FILE_LIST"
fi
done

for subfolder in "$FOLDER_KEYS" "$FOLDER_WALLET"; do
find "$SOURCE_DIR/$subfolder" -maxdepth 1 -type f >> "$FILE_LIST"
done

FOLDER_TOR_PATH="$SOURCE_DIR/$FOLDER_TOR"
if [ -d "$FOLDER_TOR_PATH" ]; then
find "$FOLDER_TOR_PATH" -type f >> "$FILE_LIST"
fi

7z a -t7z -mx=9 -m0=lzma2 -mmt=on -spf "$ARCHIVE_PATH" @"$FILE_LIST"

rm "$FILE_LIST"

echo "Backup completed: $BACKUP_FILE"

ARCHIVE_COUNT=$(find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | wc -l)

if [ "${ARCHIVE_COUNT}" -gt "${BACKUP_COUNT}" ]; then
echo "found ${ARCHIVE_COUNT} backups, removing oldest one(s)"
find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | sort -r | tail -n +"${BACKUP_COUNT}" | xargs -I {} rm -f {}
fi
</pre>

Lastly, edit the system <code>crontab</code> with
<code>crontab -e</code>
and add the following line to have a backup taken every 8 hours:

<code>0 */8 * * * /home/YOURUSERNAME/scripts/bisq1backup > /tmp/bisq1backup.log</code>

== Windows ==

Create a scripts solder and a PowerShell script:

* Open File Explorer and navigate to your user directory (e.g. C:\Users\YOURUSERNAME).
* Create a folder named <code>scripts</code>.
* Inside this folder, create a new file named <code>bisq1backup.ps1</code>.

Right-click the script file and open it in Notepad, then paste and edit the following code.

<pre>
# ==== EDIT THE FOLLOWING ====
$SOURCE_DIR = "C:\Users\YOURUSERNAME\AppData\Roaming\Bisq\btc_mainnet"
$TARGET_FOLDER = "D:\BACKUPS\BISQ1"
$BACKUP_COUNT = 4
# ============================

$ARCHIVE_ROOT = "bisq1_backup_"
$timestamp = Get-Date -Format "yyyyMMdd_HHmmss"
$BACKUP_FILE = "$ARCHIVE_ROOT$timestamp.7z"
$ARCHIVE_PATH = Join-Path $TARGET_FOLDER $BACKUP_FILE

$SELECTED_FILES = @(
"BsqSwapTrades",
"BallotList",
"DisputeList",
"RefundDisputeList",
"SequenceNumberMap",
"MyVoteList",
"OpenOffers",
"MyBlindVoteList",
"ClosedTrades",
"MediationDisputeList",
"MyProposalList",
"MailboxMessageList",
"AccountAgeWitnessStore",
"PendingTrades",
"MyProofOfBurnList",
"PreferencesPayload",
"UserPayload",
"AddressEntryList",
"FailedTrades",
"MyReputationList",
"TempProposalStore",
"NavigationPath",
"UnconfirmedBsqChangeOutputList",
"IgnoredMailboxMap",
"PeerList",
"RemovedPayloadsMap",
"TradeStatistics3Store",
"SignedWitnessStore"
)

$FOLDER_KEYS = "keys"
$FOLDER_WALLET = "wallet"
$FOLDER_TOR = "tor\hiddenservice"

$FILE_LIST = [System.IO.Path]::GetTempFileName()

$SUBFOLDER_DB_PATH = Join-Path $SOURCE_DIR "db"
foreach ($file in $SELECTED_FILES) {
$path = Join-Path $SUBFOLDER_DB_PATH $file
if (Test-Path $path -PathType Leaf) {
Add-Content -Path $FILE_LIST -Value $path
}
}

foreach ($subfolder in @($FOLDER_KEYS, $FOLDER_WALLET)) {
$dir = Join-Path $SOURCE_DIR $subfolder
if (Test-Path $dir) {
Get-ChildItem -Path $dir -File | ForEach-Object {
Add-Content -Path $FILE_LIST -Value $_.FullName
}
}
}

$FOLDER_TOR_PATH = Join-Path $SOURCE_DIR $FOLDER_TOR
if (Test-Path $FOLDER_TOR_PATH -PathType Container) {
Get-ChildItem -Path $FOLDER_TOR_PATH -File -Recurse | ForEach-Object {
Add-Content -Path $FILE_LIST -Value $_.FullName
}
}

& "C:\Program Files\7-Zip\7z.exe" a -t7z -mx=9 -m0=lzma2 -mmt=on -spf $ARCHIVE_PATH @"$FILE_LIST"

Remove-Item $FILE_LIST

Write-Output "Backup completed: $BACKUP_FILE"

$backupFiles = Get-ChildItem -Path $TARGET_FOLDER -Filter "$ARCHIVE_ROOT*.7z" | Sort-Object LastWriteTime -Descending
if ($backupFiles.Count -gt $BACKUP_COUNT) {
Write-Output "Found $($backupFiles.Count) backups, removing oldest one(s)"
$backupFiles | Select-Object -Skip $BACKUP_COUNT | ForEach-Object {
Remove-Item $_.FullName -Force
}
}
</pre>

To run the script every 8 hours:
* Open Task Scheduler.
* Create a new task and give it a name (for example, "bisq1backup").
* In the Triggers tab, set a new trigger to begin the task on a schedule, repeating every 8 hours.
* In the Actions tab, add a new action:
** Program/script: powershell.exe
** Add arguments: -ExecutionPolicy Bypass -File "C:\Users\YOURUSERNAME\scripts\bisq1backup.ps1"
* Adjust settings as needed and save the task.

== MacOS ==

Open the Terminal and run:

<pre>
cd ~
mkdir -p scripts
cd scripts
touch bisq1backup
chmod +x bisq1backup
nano bisq1backup
</pre>

Paste the following code and edit where needed:

<pre>
#!/bin/bash

# ==== EDIT THE FOLLOWING ====
SOURCE_DIR="/Users/YOURUSERNAME/Library/Application\ Support/Bisq/btc_mainnet"
TARGET_FOLDER="/Volumes/BACKUPS/BISQ1"
BACKUP_COUNT=4
# ============================

ARCHIVE_ROOT="bisq1_backup_"
BACKUP_FILE="${ARCHIVE_ROOT}$(date +%Y%m%d_%H%M%S).7z"
ARCHIVE_PATH="${TARGET_FOLDER}/${BACKUP_FILE}"
SELECTED_FILES=(
"BsqSwapTrades"
"BallotList"
"DisputeList"
"RefundDisputeList"
"SequenceNumberMap"
"MyVoteList"
"OpenOffers"
"MyBlindVoteList"
"ClosedTrades"
"MediationDisputeList"
"MyProposalList"
"MailboxMessageList"
"AccountAgeWitnessStore"
"PendingTrades"
"MyProofOfBurnList"
"PreferencesPayload"
"UserPayload"
"AddressEntryList"
"FailedTrades"
"MyReputationList"
"TempProposalStore"
"NavigationPath"
"UnconfirmedBsqChangeOutputList"
"IgnoredMailboxMap"
"PeerList"
"RemovedPayloadsMap"
"TradeStatistics3Store"
"SignedWitnessStore"
)

FOLDER_KEYS="keys"
FOLDER_WALLET="wallet"
FOLDER_TOR="tor/hiddenservice"

FILE_LIST=$(mktemp)

SUBFOLDER_DB_PATH="${SOURCE_DIR}/db"
for file in "${SELECTED_FILES[@]}"; do
if [ -f "${SUBFOLDER_DB_PATH}/$file" ]; then
echo "${SUBFOLDER_DB_PATH}/$file" >> "${FILE_LIST}"
fi
done

for subfolder in "${FOLDER_KEYS}" "${FOLDER_WALLET}"; do
find "${SOURCE_DIR}/${subfolder}" -maxdepth 1 -type f >> "${FILE_LIST}"
done

FOLDER_TOR_PATH="${SOURCE_DIR}/${FOLDER_TOR}"
if [ -d "${FOLDER_TOR_PATH}" ]; then
find "${FOLDER_TOR_PATH}" -type f >> "${FILE_LIST}"
fi

7z a -t7z -mx=9 -m0=lzma2 -mmt=on -spf "${ARCHIVE_PATH}" @"${FILE_LIST}"

rm "${FILE_LIST}"

echo "Backup completed: ${BACKUP_FILE}"

ARCHIVE_COUNT=$(find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | wc -l)

if [ "${ARCHIVE_COUNT}" -gt "${BACKUP_COUNT}" ]; then
echo "Found ${ARCHIVE_COUNT} backups, removing oldest one(s)"
find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | sort -r | tail -n +"${BACKUP_COUNT}" | xargs -I {} rm -f {}
fi
</pre>

To run the backup every 8 hours, edit your crontab using

<code>crontab -e</code>

Then add the following line:

<code>0 */8 * * * /Users/YOURUSERNAME/scripts/bisq1backup > /tmp/bisq1backup.log 2>&1</code>

= Bisq2 =

== Linux ==

Create a <code>scripts</code> folder in your <code>home</code> directory, prepare an executable file and open it with an editor:

<pre>
cd ~
mkdir -p scripts
cd scripts
touch bisq2backup
chmod +x bisq2backup
nano bisq2backup
</pre>

paste the following code in the file, and edit where needed:

<pre>
#!/bin/bash

# ==== EDIT THE FOLLOWING ====
FOLDER_TO_BACKUP="/home/YOURUSERNAME/.local/share/Bisq2/db"
TARGET_FOLDER="/mnt/BACKUPS/BISQ2"
BACKUP_COUNT=4
# ============================

ARCHIVE_ROOT="bisq2_backup_"
ARCHIVE_NAME="${ARCHIVE_ROOT}$(date +%Y%m%d_%H%M%S).7z"
ARCHIVE_PATH="${TARGET_FOLDER}/${ARCHIVE_NAME}"

7z a -t7z -mx=9 -mfb=64 -md=32m -ms=on -mmt=on "/tmp/${ARCHIVE_NAME}" "${FOLDER_TO_BACKUP}/private" "${FOLDER_TO_BACKUP}/settings"
mv "/tmp/${ARCHIVE_NAME}" "${TARGET_FOLDER}"

ARCHIVE_COUNT=$(find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | wc -l)

if [ "${ARCHIVE_COUNT}" -gt "${BACKUP_COUNT}" ]; then
echo "found ${ARCHIVE_COUNT} backups, removing oldest one(s)"
find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | sort -r | tail -n +"${BACKUP_COUNT}" | xargs -I {} rm -f {}
fi
</pre>

Lastly, edit the system <code>crontab</code> with
<code>crontab -e</code>
and add the following line to have a backup taken every 8 hours:

<code>0 */8 * * * /home/YOURUSERNAME/scripts/bisq2backup > /tmp/bisq1backup.log</code>

== Windows ==

Create a scripts solder and a PowerShell script:

* Open File Explorer and navigate to your user directory (e.g. C:\Users\YOURUSERNAME).
* Create a folder named scripts.
* Inside this folder, create a new file named bisq2backup.ps1.

Right-click the script file and open it in Notepad, then paste and edit the following code.

<pre>
# ==== EDIT THE FOLLOWING ====
$FolderToBackup = "C:\Users\YOURUSERNAME\AppData\Roaming\Bisq2\db"
$TargetFolder = "D:\BACKUPS\BISQ2"
$BackupCount = 4
# ============================

$ArchiveRoot = "bisq2_backup_"
$Timestamp = Get-Date -Format "yyyyMMdd_HHmmss"
$ArchiveName = "$ArchiveRoot$Timestamp.7z"
$TempArchive = Join-Path $env:TEMP $ArchiveName
$FinalArchive = Join-Path $TargetFolder $ArchiveName

& "C:\Program Files\7-Zip\7z.exe" a -t7z -mx=9 -mfb=64 -md=32m -ms=on -mmt=on "`"$TempArchive`"" "`"$FolderToBackup\private`"" "`"$FolderToBackup\settings`""

Move-Item -Path $TempArchive -Destination $FinalArchive -Force

$Archives = Get-ChildItem -Path $TargetFolder -Filter "$ArchiveRoot*.7z" | Sort-Object LastWriteTime -Descending

if ($Archives.Count -gt $BackupCount) {
Write-Output "Found $($Archives.Count) backups, removing oldest one(s)"
$Archives | Select-Object -Skip $BackupCount | ForEach-Object {
Remove-Item $_.FullName -Force
}
}
</pre>

To run the script every 8 hours:
* Open Task Scheduler.
* Create a new task and give it a name (for example, "bisq2backup").
* In the Triggers tab, set a new trigger to begin the task on a schedule, repeating every 8 hours.
* In the Actions tab, add a new action:
** Program/script: powershell.exe
** Add arguments: -ExecutionPolicy Bypass -File "C:\Users\YOURUSERNAME\scripts\bisq2backup.ps1"
* Adjust settings as needed and save the task.

== MacOS ==

Open the Terminal and run:

<pre>
cd ~
mkdir -p scripts
cd scripts
touch bisq2backup
chmod +x bisq2backup
nano bisq2backup
</pre>

Paste the following code and edit where needed:

<pre>
#!/bin/bash

# ==== EDIT THE FOLLOWING ====
FOLDER_TO_BACKUP="/Users/YOURUSERNAME/Library/Application Support/Bisq2/db"
TARGET_FOLDER="/Volumes/BACKUPS/BISQ2"
BACKUP_COUNT=4
# ============================

ARCHIVE_ROOT="bisq2_backup_"
ARCHIVE_NAME="${ARCHIVE_ROOT}$(date +%Y%m%d_%H%M%S).7z"
ARCHIVE_PATH="${TARGET_FOLDER}/${ARCHIVE_NAME}"

7z a -t7z -mx=9 -mfb=64 -md=32m -ms=on -mmt=on "/tmp/${ARCHIVE_NAME}" "${FOLDER_TO_BACKUP}/private" "${FOLDER_TO_BACKUP}/settings"
mv "/tmp/${ARCHIVE_NAME}" "${ARCHIVE_PATH}"

ARCHIVE_COUNT=$(find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | wc -l)

if [ "${ARCHIVE_COUNT}" -gt "${BACKUP_COUNT}" ]; then
echo "Found ${ARCHIVE_COUNT} backups, removing oldest one(s)"
find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | sort -r | tail -n +"${BACKUP_COUNT}" | xargs -I {} rm -f {}
fi
</pre>

To run the backup every 8 hours, edit your crontab using:

<code>crontab -e</code>

Then add the following line:

<code>0 */8 * * * /Users/YOURUSERNAME/scripts/bisq2backup > /tmp/bisq2backup.log 2>&1</code>