Bitcoin marketplace and current trading restrictions
Sections ↑Peach’s Bitcoin P2P marketplace currently admits only approved sellers, who fully control trade BTC. Peach supplies mediation without a signature; older joint-escrow descriptions do not describe present protection.[1]
Peach claims CHF15 million-plus cumulative P2P turnover without a dated methodology. This company total is neither monthly volume nor an active-trader count.[1]
Service routes
| Route | What the user does | Scope |
|---|---|---|
| Buy Bitcoin | Browse sell offers or publish a buy request with amount, currency, payment method and acceptable premium. | The counterparty supplies the BTC.Source 5 |
| Sell Bitcoin | Publish or accept an offer, fund the trade and confirm actual receipt of the agreed payment. | Current seller approval applies before ordinary workflow instructions.Source 5 |
| Desktop access | Pair a browser with the mobile account to manage offers and trades. | The phone retains signing authority.Source 6 |
| Business integrations | Published API, merchant plugin and professional support routes. | A business enquiry does not guarantee seller approval.Source 21 |
Seller categories announced on 31 August 2026
| Route | Published condition |
|---|---|
| Identity-verified seller | KYC-approved users can create sell offers. |
| Manual exception | Peach can whitelist special users; the announcement said none were then whitelisted. |
| Established seller | Zero lost disputes and more than 60 completed seller trades. |
| Broader established history | Zero lost disputes, more than 30 seller trades and more than 80 total trades. |
Buyer fees, offer premiums and network charges
Sections ↑Components of a quoted purchase
| Component | Treatment |
|---|---|
| Peach trading fee | The trading FAQ charges the buyer 2%, reducing the BTC received.Source 9 |
| Offer premium or discount | The agreed price can sit above or below the reference market price. The former ±21% cap was removed in v0.69.0, announced 17 March 2026.Source 18 |
| Bitcoin network fee | Funding, release and later wallet transfers consume network capacity; batching changes the release fee, not the agreed fiat price.Source 12 |
| Payment provider cost | Buyers and sellers bear their own fiat-transfer costs under the terms.Source 3 |
A hypothetical 100,000-sat trade worth CHF100 at reference costs CHF105 with a 5% premium. The 2% fee removes 2,000 sats, leaving 98,000 before mining. Effective cost per received sat is 7.1429% above reference. Payment/mining costs and price movement are excluded.[18][9]
The August service-change announcement expressly retains the 2% release fee despite removal of Peach’s escrow signature. The continued fee should not be interpreted as purchasing the previous co-signing protection.[2]
Payment, Bitcoin delivery and cancellation
Sections ↑Trade sequence
| Stage | Action and consequence |
|---|---|
| Match | Choose the actual currency, payment method and offer; ordinary requests need acceptance, while instant offers can begin automatically. |
| Fund and inspect | The seller funds the designated trade. The buyer uses the payment details shown for that contract. |
| Pay | Send the agreed amount, then mark payment made. The seller checks receipt in the actual payment account before confirming. |
| Receive | BTC delivery follows the release transaction and any batching choice. A payment confirmation screen alone is not blockchain settlement. |
Payment choices and restrictions
| Method or issue | Published condition |
|---|---|
| Bank, online and cash methods | Availability depends on currency, counterparty and the app. A listed method does not establish residency eligibility. |
| Anonymous methods | The payment FAQ gives CHF1,000 equivalent per month for anonymous methods, including relevant cash, gift-card and USDT payment routes. |
| PayPal buyers | The FAQ requires CHF500 previous traded value, three trades and a five-peach reputation score. |
| Gift cards | Amazon/Steam support concerns online delivery of the exact agreed amount; physical cards are not accepted under the described procedure. |
Before a match, an offer can be withdrawn. Once a trade exists, cancellation is conditional and can affect reputation. The Marketplace FAQ distinguishes a buyer cancelling before marking payment from raising a dispute afterward. A seller should not assume cancellation is permitted after the buyer may already have paid; use the contract’s cancellation request and counterparty response.[10]
External payouts require an address-control signature, which not every wallet supports. The FAQ describes manual addresses rather than live xpub automation. Stuck funding/send transactions may support RBF; released outputs may allow CPFP. Neither reverses a confirmed trade.[9]
The February 2026 GroupHug guide describes batching up to 24 hours and an opt-out under transaction-batching settings for a direct payout with the full network cost. Batching itself adds no claimed privacy. Those are published scheduling mechanics, subject to the current trade arrangement; the guide’s old joint-escrow safety language is superseded.[12]
The Release FAQ directs users to the trade’s participant count and estimated release time. A threshold is a trigger rather than a maximum batch size, and a single queued payout need not broadcast immediately. This distinguishes a transaction still awaiting broadcast from one already submitted to Bitcoin and waiting for confirmation.[11]
Seller control, wallet keys and recovery
Sections ↑The present notice says the seller fully controls the trade BTC and Peach has no escrow control. Consequently, mediation cannot be treated as the old mechanism that let Peach enforce a Bitcoin release. The notice’s offer of support does not specify an insured amount or an unconditional reimbursement formula.[1]
Account recovery is different from trade recovery
| Item | Documented scope |
|---|---|
| Encrypted account file | A complete backup restores the account, including payment data and chat history. |
| Seed backup | Restores wallet/account access but omits chats and payment details. The FAQ identifies a 12-word seed. |
| Forgotten password | While still logged in, create a new backup/password. Peach cannot recover a lost password without the accessible device. |
Wallet and privacy controls
| Control | Boundary |
|---|---|
| Personal wallet | An internet-connected hot wallet; its security depends partly on the phone and operating system. |
| Own node | The FAQ supports connecting an accessible IPv4 node and says Tor is not currently supported. |
| Instant-trade payment details | Unlike the ordinary encrypted exchange, payment information is also shared with Peach to deliver it immediately. |
| Coin control | Lets users select and keep Bitcoin outputs separate; it is not a guarantee of anonymous transactions. |
A restored wallet can need a larger address-discovery gap to find all previously used payout addresses. Keep the full account backup separately from the phone; seed recovery alone does not reconstruct the evidence needed for an old trade dispute.[13]
Jurisdiction, identity and transaction limits
Sections ↑Terms require age 18, one account and own-name payments. Citizenship, permanent/tax residence and location restrictions cover the US/territories, Iran, North Korea, Myanmar, China, Algeria, Bangladesh, Nepal, Afghanistan, Morocco, Egypt, Bolivia, Qatar, Tunisia, Pakistan, Vietnam, Indonesia and Nigeria, plus applicable UN/OFAC/EU-embargoed jurisdictions.[3]
Peach does not actively offer or market in the EU/EEA; it relies on exclusive user initiative and may restrict access. That position establishes neither a MiCA licence nor universal local eligibility.[3]
Published limits are CHF1,000 daily and CHF100,000 annually; specified anonymous payment methods have a CHF1,000 monthly limit. Current application restrictions also apply.[3]
The FAQ offers KYC for higher-volume sellers; buyer limit increases are unavailable. Identity-free marketing is therefore conditional.[9]
Disputes, payment evidence and records
Sections ↑Official assistance routes
| Purpose | Route |
|---|---|
| General assistance | In-app contact form or [email protected]. |
| Trade dispute | Open the dispute within the trade chat; [email protected] is also published. |
| Encrypted correspondence | The support page publishes separate PGP keys for general and dispute correspondence. |
For a disagreement, first communicate inside the trade chat. The published dispute guide describes opening the red dispute control, choosing the reason and supplying payment evidence. Mediators can request proof of receipt or non-receipt and continue through chat or email. Its response estimates are inconsistent, so they are not treated as a binding service level. Current mediation does not restore the removed Peach signature.[16]
The terms require responses within 24 hours; request any extension inside that window. They exclude off-platform conversations from dispute evidence. Users remain responsible for their taxes.[3]
Peach’s safety guidance flags mismatched payment names, fragmented payments, suspicious overpayments and requests to return the difference through another channel. These can be signs of a third-party payment problem. A seller should resolve the actual payment provenance through the agreed process before releasing BTC; a screenshot from the buyer is not equivalent to confirmed bank receipt.[17]
The private API documents contract summaries and full contract records, including price, currency, status and transaction identifiers. Preserve these alongside actual bank/payment records and wallet transactions; they are not a promised tax certificate. A seed-only restoration cannot restore the missing chat evidence.[19]
The privacy policy retains dispute information and payment/device hashes for defined purposes, with some records kept for ten years and banned-user hashes retained indefinitely. Account deletion therefore does not imply immediate erasure of the trade record. Support submissions may include logs or identity evidence; normal counterparty privacy does not mean nothing is disclosed during a dispute.[4]
Swiss AML membership and protection boundaries
Sections ↑PolyReg’s current public membership lookup returns a positive result for the exact name Peach Sàrl. Its published remit is AML supervision of affiliated financial intermediaries under Swiss law. This supports the specific SRO-membership statement, not a claim that Peach holds a bank licence or an EU-wide crypto-service permission.[23][24]
In the 31 August founder’s letter, Peach attributed its escrow suspension to a reassessment of the previously accepted compliance model. That is the company’s account of an ongoing disagreement. No final ruling or restoration date was established; the current site notice still describes the temporary restricted service.[2]
Contracting entity and service continuity
Sections ↑Operator identity
| Field | Published detail |
|---|---|
| Company | Peach Sàrl, company identifier CHE-158.025.408. |
| Registered office | c/o Nohä Fiduciaire SA, Rue Saint-Honoré 2, 2000 Neuchâtel, Switzerland. |
| Legal documents | Privacy policy dated 8 June 2026; service conditions are linked separately. |
The English service terms select Neuchâtel, Switzerland, law.[3]
- Operator
- Peach Sàrl
- Exchange model
- Hybrid
- Service scope
- Bitcoin P2P matching with central coordination and mediation; sellers currently require restricted eligibility.
- Client types
- Retail clients; Professional clients
- Pricing publication
- Public pricing
- Other names
- Peach
- Covered jurisdictions
- Switzerland
- Pricing scope
- Buyer trading fee 2%, plus quoted seller premium or discount and applicable Bitcoin/payment costs.
- Funding scope
- Buyers pay counterparties directly through agreed methods. Sellers fund Bitcoin trades; buyers receive BTC in an eligible wallet.
- Custody and asset handling
- Current temporary arrangement gives sellers full control of trade BTC; Peach cannot co-sign or compel release. The personal wallet remains user-controlled.
- Client eligibility
- Adults in permitted jurisdictions; own-name payments. EU/EEA access is framed as exclusive user initiative, with continuing access restrictions.
- Support
- In-app support and trade dispute chat; [email protected] and [email protected] are published contacts.
- Authorisation and registration scope
- Exact-name PolyReg membership confirmed on 21 October 2026. This is Swiss AML SRO supervision, not a verified MiCA or bank authorisation.
Exchange metadata checked 21 Oct 2026Source 1Source 2Source 3Source 4Source 5Source 9Source 15Source 23Source 24
Covered contracting entities
Peach Sàrl
- Jurisdiction
- Switzerland
- Covered services
- Bitcoin marketplace operator; CHE-158.025.408.
- Client and location scope
- Subject to service terms and current restrictions.
Browser sessions, integration authority and referrals
Sections ↑Phone and browser responsibilities
| Function | Documented behaviour |
|---|---|
| Desktop session | Pair through a QR code. Closing the window or logging out ends that browser session. |
| Multiple browsers | Several browsers can be paired; each session has its own lifetime. |
| Signing | The phone keeps the private keys. Sensitive actions require the mobile device, including when a browser remains available for browsing. |
| Persistent trade | A browser logout ends the session; it is not the published contract-cancellation procedure. |
The API separates public market data from authenticated user operations. A signed challenge obtains a token valid for 60 minutes. Private endpoints include creating/cancelling offers, payment confirmations and disputes, so the interface is not read-only. Its documentation contains older escrow fields; integrations must reconcile those with the temporary arrangement. The public status/info endpoints returned HTTP 451 during this research, so their live operation was not verified.[19]
The business page offers professional support and API wrappers. Its BTCPay Server integration lets a merchant publish sales from its hot wallet and choose an offer premium or discount. This is merchant-controlled offer creation, not a promise of automatic fiat conversion, a guaranteed match or independent discretionary management. Current seller eligibility continues to apply.[22]
The new-user page advertises one fee-free buy trade. That is a trading-fee benefit, not an unconditional cash deposit; it does not establish that Bitcoin network charges or the counterparty premium disappear.[20]
The account FAQ awards one referral point per 10,000 referred sats. Rewards include a custom code at 100 points, two fee-free trades at 200, or conversion from 300 points. Conversion is described as 42 sats per point, linked to 21% of fees from the referred user’s first five trades, with the first fee-free. Payout requires a manual request; Lightning/on-chain routes are listed.[13]
Sources & further reading
- Current trading notice and homepage Peach Bitcoin · Accessed 21 Oct 2026
- Peach at a Crossroads Peach Bitcoin · 31 Aug 2026 · Accessed 21 Oct 2026
- Service terms Peach Bitcoin · 1 Jul 2026 · Accessed 21 Oct 2026
- Privacy policy Peach Bitcoin · 8 Jun 2026 · Accessed 21 Oct 2026
- Mobile trading guide Peach Bitcoin · Accessed 21 Oct 2026
- Desktop web application Peach Bitcoin · Accessed 21 Oct 2026
- Browser session FAQ Peach Bitcoin · Accessed 21 Oct 2026
- Payment-method FAQ Peach Bitcoin · Accessed 21 Oct 2026
- Trading FAQ Peach Bitcoin · Accessed 21 Oct 2026
- Marketplace FAQ Peach Bitcoin · Accessed 21 Oct 2026
- Release FAQ Peach Bitcoin · Accessed 21 Oct 2026
- GroupHug batching Peach Bitcoin · 15 Feb 2026 · Accessed 21 Oct 2026
- Account and recovery FAQ Peach Bitcoin · Accessed 21 Oct 2026
- Wallet privacy FAQ Peach Bitcoin · Accessed 21 Oct 2026
- Customer and dispute contacts Peach Bitcoin · Accessed 21 Oct 2026
- Dispute procedure Peach Bitcoin · 25 Jan 2026 · Accessed 21 Oct 2026
- Payment safety guidance Peach Bitcoin · Accessed 21 Oct 2026
- Premium cap removal Peach Bitcoin · 17 Mar 2026 · Accessed 21 Oct 2026
- Public API reference Peach Bitcoin · Accessed 21 Oct 2026
- New-user offer Peach Bitcoin · Accessed 21 Oct 2026
- Business services Peach Bitcoin · Accessed 21 Oct 2026
- BTCPay Server plugin Peach Bitcoin · 21 Oct 2025 · Accessed 21 Oct 2026
- Peach Sàrl membership result SRO PolyReg · Accessed 21 Oct 2026
- SRO PolyReg remit SRO PolyReg · Accessed 21 Oct 2026
This profile reports dated public information, including exchange-published services and terms. It does not independently test or guarantee trading, custody, pricing or withdrawals. Inclusion is not an endorsement. Permissions and protections apply only to the named legal entity, service and client category; check the current official records and your contract.
Report an error or submit an update