
When choosing a crypto wallet as a freelancer, first establish whether clients can pay as agreed and whether you can match each payment to a project. An address that receives tokens does not prove that a custodial account permits business payments or that your records are complete. Compare tools from the point of sharing payment instructions through checking assets and networks, confirming receipt, keeping invoices, and converting or withdrawing funds. A suitable arrangement should meet account and business requirements, make payment straightforward for clients, help you explain the source of funds, and show how much you can ultimately use.

The main differences are who controls the assets, who manages payment statuses, and who handles reconciliation. A self-custody wallet generally lets you provide an address directly. A custodial business account requires you to confirm that your activities and payment sources are accepted. A merchant payment service may combine payment requests, exception handling, and settlement in one workflow. Compare these arrangements separately rather than ranking wallets solely by the number of supported assets.
| Payment arrangement | Details provided to clients | Help with business payments | Responsibilities or restrictions |
|---|---|---|---|
| Self-custody wallet, such as MetaMask | Receiving address, QR code, or payment request | Direct receipt of assets on supported networks; independent wallet management | Safeguard keys, match clients and projects, record amounts, and arrange conversion |
| Custodial business account | Supported deposit details or payment tools | May offer account statements, business verification, and conversion features | Check business eligibility, third-party payment requirements, funds reviews, and withdrawal conditions |
| Merchant payment service, such as BitPay | Payment invoice, payment link, or checkout request | Connects payment statuses with orders and settlement records | Complete merchant verification and check service fees, settlement rules, and exception handling |
Individual freelancers, sole proprietors, and incorporated businesses may not qualify for the same account. Permission to hold and convert crypto as an individual does not establish permission to regularly receive client service fees. The rule that personal Coinbase accounts are not intended for business activity illustrates why account use needs its own check. One successful deposit is not enough to make an address your ongoing business payment channel.
When evaluating a custodial service, describe your business structure, services, client payment sources, and expected frequency before confirming the account category. Ask whether clients can pay from their own exchange accounts, whether third-party transfers are accepted, and whether payment records can be exported by order. Inspect a sample statement to see whether project references, fees, and settlement records can be matched. A business account label does not mean every industry or location is supported.
Self-custody wallets require a different assessment: key backups, device security, and your ability to maintain records. Managing a separate business address can reduce the mixing of personal transfers and client payments, but it does not automatically satisfy business, tax, or subsequent conversion-provider requirements. A merchant service's “payment invoice” may also be only a payment request, rather than a substitute for a business invoice required under applicable rules.

Before payment, ask the client to confirm a complete set of instructions they can check, rather than sending only an address. At a minimum, agree on the project reference, invoice currency, payment asset, network, quantity due, and responsibility for fees. For a custodial account, include any memo or tag required by its current deposit instructions. If the client pays through an exchange, check which withdrawal networks and asset versions that exchange actually supports.
Receiving funds with MetaMask can involve a public address, QR code, or payment request, but these tools do not determine your contract amount or business terms. QR codes make details easier to share, yet their contents still need checking before you send them. After copying and pasting an address, the client should verify the complete address and selected network, rather than relying on matching characters at the beginning or end.
Business payment instructions can include:
The same USDC or USDT ticker does not mean transfers work interchangeably across networks. An identical address format also does not establish that a custodial account supports a particular network or asset version. If a client proposes another network, recheck the receiving service and subsequent conversion route before agreeing, even if the fee appears lower.
The pricing method also needs advance agreement. If a contract specifies a fiat amount but payment will be in crypto, establish the quote and timestamp used to calculate the quantity. If you agree on a fixed quantity of an asset instead, clarify how price changes affect each party. Avoid reinterpreting the amount due after payment using the fiat estimate displayed in a wallet.
For a first engagement, both parties may agree to a small test payment before checking the main transfer, but a successful test does not prove that the account permits business use. Verify last-minute address changes through an established contact channel. Receiving an ordinary transfer does not require sharing a private key or recovery phrase with a client, or approving an unfamiliar contract to spend assets to “unlock” payment. When you later send funds, check the wallet's supported methods for paying network fees and prepare the appropriate fee asset if needed.

Check the actual transaction and the receiving service's status before updating project records. A client screenshot is a starting point for investigation, not a replacement for blockchain records or platform statements. You also need to establish whether the agreed asset arrived, whether the full amount was received, and whether the funds are currently usable. “Sent,” “confirmed,” and “available to withdraw” answer different questions.
Look up the transaction hash in a block explorer for the correct network. Verify the transaction status, receiving address, asset identity, and actual quantity. A newly appearing token with a familiar name, or a displayed fiat estimate, should not automatically be treated as project payment. With a self-custody wallet, confirm receipt of the correct asset. A custodial platform may require further confirmations or a review, so blockchain success does not automatically mean the account balance is available.
Payment services also define their own statuses. BitPay merchant payment statuses distinguish Paid, Confirmed, and Complete: Paid is still awaiting blockchain confirmation; Confirmed indicates blockchain confirmation; and Complete means the funds have been credited to the merchant ledger for the next settlement payout. That final status still does not establish that a bank has received the money.
Your business records can therefore note separate times for detecting the payment, confirmation, platform availability, and bank receipt. Handle project delivery or final payment clearance according to the agreed terms. Plan cash flow around actual availability, rather than treating an expected withdrawal amount as cash already received.
Compare the amount received with the valid payment request. For an underpayment, first check whether the client deducted withdrawal fees, used an expired quote, or paid in installments. Record overpayments and duplicate transfers separately to avoid counting the same project income twice. If someone pays on the client's behalf, establish the relationship and check whether the receiving account accepts that arrangement.
When a client pays from an exchange, the sending blockchain address may belong to a wallet managed centrally by the platform and may not identify the client directly. Match the payment using the invoice reference, client confirmation, and withdrawal records. For a wrong network, wrong asset, or missing tag, retain transaction details and follow the receiving service's procedures. Recovery cannot be promised.
Do not automatically send refunds back to the original sending address. Verify the refund instructions authorized by the client, the asset, and the network, and establish whether an exchange requires a new deposit address or tag. Keep the refund transaction and business reason. Matching an address does not resolve every identity question, and pressure from a sender should not prompt you to forward an unusual payment to another unfamiliar address.
A useful record should explain who paid for which service, what was agreed, how much arrived, and what happened afterward. A blockchain transaction proves an asset transfer but generally cannot establish the service provided, the client's identity, or whether a contractual obligation has been settled. Compare record exports and order matching alongside payment capabilities when selecting wallets and payment services.
| Record category | Suggested information to retain | Main reconciliation purpose |
|---|---|---|
| Business agreement | Contract, client details, project and invoice references, service description, invoice amount, and payment terms | Explains why the payment arose and who was expected to pay |
| Payment instructions | Asset, network, address, quantity, quote timestamp, and responsibility for fees | Establishes whether payment followed the agreement |
| Actual receipt | Transaction hash, quantity received, time, status, and platform order reference | Confirms receipt of the correct asset and full amount |
| Valuation | Valuation currency, price source, and relevant timestamp | Explains the payment's value when received |
| Subsequent use of funds | Conversion executions, fees, transfers, bank deposits, and refund documents | Tracks later changes in amount and the funds' destination |
Use a consistent project reference to connect these records; you do not need to put everything into an on-chain memo. For staged payments, label deposits, milestones, and final balances separately. If one transfer covers several invoices, retain an allocation breakdown. If an invoice is settled through several transfers, keep each payment record and the outstanding balance rather than judging completeness solely from the total wallet balance.
Wallet statements, merchant payment invoices, and business invoices serve different purposes. Amounts and statuses on a payment request help with collection, but you still need to check whether its format, required fields, and retention arrangements satisfy applicable requirements. The ability to generate a PDF does not mean all bookkeeping and reporting work is complete.
Where possible, retain exportable transaction details and order files, together with necessary screenshots and correspondence. Include time zones in timestamps and identify valuation sources so records can be checked later. Linking client information to public blockchain addresses also creates privacy considerations. Limit sharing rather than publishing an entire client ledger to prove payment.
Record the receipt and its value even if you retain stablecoins without converting them immediately. Track subsequent holding, conversion, or transfer activity separately. Recording only the final bank deposit can mix service income, fees, and asset price changes together. Apply the relevant rules and professional advice to income recognition, tax classification, and retention periods; do not assume records are needed only when crypto is converted into fiat.
First reconcile the project receivable with the actual payment, then reconcile the assets received with the amount reaching your bank. To compare tools meaningfully, calculate payment service fees, necessary transfer costs, the conversion quote, and withdrawal charges for the same project. Keep the final bank deposit distinct from business revenue and after-tax profit.
Suppose a project is priced at $1,000 and both parties explicitly agree that the client will pay 1,000 USDC on a specified network, with network fees paid separately by the client. After receiving the full amount, assume the executed conversion rate is exactly $1 per USDC, the conversion fee is $5, the withdrawal fee is $3, and no other charges apply. The bank receives:
1,000 × 1 − 5 − 3 = $992.
These are calculation assumptions, not a claim that stablecoins always convert at face value or a quote from any provider. If the client deducts 5 USDC from the amount due and you receive only 995 USDC, first use the contract to determine whether a balance remains outstanding. Do not automatically classify the shortfall as your business expense. Network fees paid separately by the client should not be deducted again from your proceeds.
When the receiving currency differs, use the actual executed exchange rate. Avoid deducting costs twice if a quote already includes spreads or fees. If you transfer assets to another platform before conversion, include the transfer costs you actually bear. When checking a route for transferring crypto to a bank account, focus on account conditions, the deposit currency, and whether settlement records can be connected to your project documents.
With a small number of established clients, clear instructions and manageable project records may be sufficient. As client numbers and milestone payments grow, payment links, order references, exception alerts, and bulk exports become more valuable. A tool with a slightly higher service fee may reduce manual follow-ups and payment mismatches, but its value depends on your actual workload.
If you frequently convert into fiat, first check whether the service accepts your business source of funds, asset network, and bank account type, rather than starting with advertised rates. If you plan to retain some crypto, record the project payment separately from the subsequent holding decision. Different tools can handle collection, custody, and conversion, but each additional step requires checking costs and the connection between supporting records.
If you are considering Biya for subsequent asset management and conversion, first confirm whether the account accepts the relevant business source of funds and check locally available features, asset networks, and transfer conditions. The ability to deposit does not establish permission to collect client service fees directly. Compare the Biya fee center with actual orders to check applicable charges, conversion quotes, and bank proceeds, retaining records linked to project references. If account conditions do not accommodate business funds, choose a payment arrangement suited to business use. Service availability depends on your location, identity verification results, platform rules, and applicable laws and regulations.
An address's ability to receive deposits does not establish that a personal account is suitable for business payments. Check whether the platform permits client service fees, third-party payments, and ongoing business use, and whether a business account or additional documentation is required. One successful deposit does not guarantee acceptance of later payments or withdrawals.
Use the invoice reference, client payment confirmation, withdrawal records, and transaction hash together. An exchange may send from a centrally managed address, so the blockchain address alone cannot establish client identity. Also verify the actual amount received and confirm that the payment source meets the receiving account's requirements.
Not necessarily. Separate addresses depend on wallet capabilities, privacy needs, and bookkeeping arrangements. A dedicated address may help distinguish projects, but it adds management work and cannot replace invoices and client records. If you reuse an address, create clear links through project references and payment details.
That depends on the agreed amount and responsibility for fees. If the agreement requires receipt of a specified quantity in full, a deduction may leave an outstanding balance. If you agreed to bear the charge, record it accordingly. Clarify the amount to send and the net amount to receive before payment to avoid conflicting interpretations afterward.
Do not automatically refund the original address, particularly when payment came from an exchange or payment service. The sending address may not be one through which the client can receive a refund directly. Verify authorization, the refund network, asset, and any required tag, and retain correspondence, the refund amount, and transaction evidence.
Yes. Retain business documents, the quantity received, timestamps, and the relevant valuation when payment arrives, then record later conversions or transfers separately. A stablecoin's name does not replace an actual valuation, and delaying withdrawal does not remove the need for records. Apply the relevant rules to income recognition and tax treatment.
*This article is provided for general information purposes and does not constitute legal, tax or other professional advice from BiyaPay or its subsidiaries and its affiliates, and it is not intended as a substitute for obtaining advice from a financial advisor or any other professional.
We make no representations, warranties or warranties, express or implied, as to the accuracy, completeness or timeliness of the contents of this publication.



