Step 1
Choose the receiving method before you send instructions
Direct transfer
Useful when you and an already agreed client can verify the wallet address, asset, network, amount and confirmation rule together. You remain responsible for matching the payment to the invoice and checking the transaction.
Provider gateway
Useful when a provider offers a payment link, checkout or reconciliation workflow that fits your business. Its availability, verification, assets, networks, fees, custody, refunds and payout terms are provider- and jurisdiction-specific.
Do not treat a wallet address as a complete business payment flow. If you need card acceptance, subscriptions, automated status updates, formal refunds or accounting integration, pause and evaluate a provider's official merchant documentation before promising that option to a client.
Step 2
Prepare a payment request with unambiguous fields
Before funds move, give the client one written request. The address and the network must match: an address alone is not sufficient payment instruction.
- Invoice or reference ID and a short description of the agreed work.
- Invoice currency and the exact crypto amount to send.
- Exact asset and network, written together, for example USDC on [network].
- Receiving wallet address, copied from the wallet you control and independently rechecked.
- Payment deadline, who pays the network fee, and the confirmation rule you both accept.
- A contact path for a mismatch, delayed confirmation or suspected wrong-network transfer.
Example
A neutral payment-request template
This is an example of fields to include in your own invoice or message. It is not a MyCoinWay invoice, payment link or checkout service.
Reference: INV-EXAMPLE-001
Service: [agreed description]
Invoice currency / amount: [currency] / [amount]
Send: [asset] on [network]
Receiving address: [independently verified address]
Network fee: paid by [sender / recipient as agreed]
Confirmation rule: [for example, agreed network confirmations]
Deadline and support contact: [agreed details]
Step 3
Confirm and document the payment
A payment request and a received transaction are separate records. Check the transaction against the agreed asset, network, destination address, amount and confirmation rule before marking the invoice paid.
- Keep the invoice or payment request, the transaction identifier, receipt timestamp and the agreed exchange-rate or invoice-currency record.
- Record any provider charge separately from the network fee; they are not the same cost and may be charged to different parties.
- Keep any provider status record or wallet evidence with the client reference so that a later reconciliation is possible.
Accounting, tax, licensing and consumer-payment obligations depend on your business and jurisdiction. Obtain local professional advice where those rules apply; this guide is operational education, not legal, tax or accounting advice.
After receipt
Keep later actions separate from the invoice
Converting received crypto to local currency through P2P is a separate process with its own venue, counterparty, payment-method and local-availability risks. It is not a completion step for every crypto invoice and should not be promised to the client as part of accepting payment.
Read the P2P guide for that separate process after you have completed and recorded the original payment.
Provider-specific checks
If you choose a gateway, verify merchant onboarding, verification, supported capabilities and terms directly with that provider. For example, Binance Pay's merchant material describes account creation, verification, agreement and API integration; it does not establish eligibility or terms for every business or country.