A practical look at accepting Bitcoin for professional work with BTCPay Server: what the software does, what you control, what connecting it to TheOrangeCove involves, and what it asks of you.
If you want to accept Bitcoin for professional work without handing your payments to a third party, BTCPay Server is the usual answer: open-source software you (or a host you choose) run, which creates invoices and receives payments into a wallet you control. On TheOrangeCove, connecting a working BTCPay setup is what allows your eligible Listings to show a Pay with Bitcoin option.
This article is for Professionals deciding whether that is worth doing, and what it commits them to. It is not investment advice and it is not a recommendation to hold Bitcoin.
The honest case is narrower than the enthusiastic one.
Direct settlement. Payments arrive at infrastructure you control, without an intermediary deciding when to release them or whether your line of work is acceptable.
Cross-border usability. Bitcoin does not care which country your Client is in. For international clients, that can remove a category of friction around currencies and correspondent banking.
Less dependence on payment intermediaries. Fewer parties who can freeze, reverse or reclassify a payment after the fact.
Control over your payment stack. You choose the software, the wallet, and the policies around them.
Now the other side, which matters just as much.
Volatility. Bitcoin's value against your local currency can move meaningfully between quoting and settlement, and after settlement. How you price, and whether you convert, is a business decision with real consequences.
Accounting and tax. Receiving Bitcoin does not exempt you from invoicing, bookkeeping or tax obligations, and treatment differs by jurisdiction. Get qualified advice for your situation rather than guessing from forum posts.
Wallet security. Nobody can restore your keys for you. Backups and key handling become part of your professional operations.
Finality. A confirmed Bitcoin transaction is not reversible. That protects you against chargeback abuse and it means mistakes are costly.
A learning curve. Invoices, exchange rates, partial payments, expiry windows, webhooks: all of it needs to work when a real Client is trying to pay you.
Local rules. Whether and how you may accept Bitcoin, and what you must record, depends on where you operate. Bitcoin is not universally cheaper, faster or permitted, and anyone claiming otherwise is selling something.
BTCPay Server is free, open-source, self-hostable Bitcoin payment software. It is a community project — TheOrangeCove neither built it nor owns it. The official project site is btcpayserver.org, and its documentation is the authoritative reference for anything version-specific.
Functionally, it does four things you care about:
The design is non-custodial by intent: BTCPay is a tool for receiving your own payments, not a service that takes possession of them.
Everything in this list sits with you, whether you self-host or use a hosted BTCPay instance:
If a Client pays and something needs to be refunded, you issue that refund. If your instance is offline, checkout does not work. Control and responsibility are the same thing here.
The integration is deliberately thin. TheOrangeCove starts checkouts against your store and reads the resulting status; it never touches your funds.
In the Professional Portal you open the Payments section and supply the connection details for your store — the instance, the Store ID and a credential with the permissions the integration needs. From there:
Labels shift as the Portal evolves, but the shape does not: reachable store, working credential, working webhook, then checkout. Until every step passes, the Listing stays inquiry-only, which is the safe default — it is better for a Client to send you a message than to meet a broken invoice.
The reason the flow looks like this is the payment model itself: the platform integrates a path it never custodies. Non-custodial professional payments explains the same arrangement from the Client's side, which is worth reading if you plan to answer Client questions about it.
Bitcoin checkout is available on Pro and Premium, and the difference is the help you get setting it up.
On Pro, you bring and configure your own BTCPay Server. Standard email support during business days covers questions about TheOrangeCove and the connection itself.
On Premium, you additionally get a guided setup workflow: structured instructions, a checklist, and asynchronous support through the process.
The boundary is firm in both cases, and it is worth reading twice before you buy a plan expecting otherwise. Premium support does not include hosting your instance, holding funds or keys, managing your wallet, administering your server, handling seed phrases, 24/7 availability, or a response-time guarantee. It is help understanding and completing your own setup. Current entitlements are on the pricing page.
Some of these are absolute. Treat them as such.
Anything beyond this — hardening a public-facing server, network topology, node operation — belongs to your own hosting decisions and to the official BTCPay documentation, not to a marketplace article.
Before you enable checkout, you should be able to answer yes to all of these:
If any answer is no, stay inquiry-only until it is yes. An unclear payment experience costs more trust than not offering checkout at all — and how trust and visibility work here is a separate topic, covered in what TheOrangeCove is and how it works.
Questions about eligibility and reviews are answered in the FAQ.
Written by
Marco
Co-founder
Paying a Professional in Bitcoin means the money goes straight to them, not to a platform holding it in the middle. Here is what that changes for you, and what to check before you pay.
TheOrangeCove is a curated marketplace where Clients find Professionals and pay them directly in Bitcoin. Here is how discovery, review, plans and non-custodial checkout actually work.
More in Bitcoin for Professionals.
