| Who controls the funds? | The receiving destination belongs to the merchant. Confirm that the server configuration cannot sign transfers and that the merchant can recover and spend independently. | The provider controls the balance or payout process under its agreement. Check withdrawal, review, reserve, and suspension provisions. | The merchant controls the wallet and must also protect the process used to issue destinations and identify receipts. |
|---|
| What does it cost? | Price setup, hosting, monitoring, maintenance and support, plus network costs. A proposal without a percentage charge still has operating costs. | Read transaction, conversion, withdrawal, and payout charges together. Obtain the actual schedule for the product, country, and settlement method. | Price staff time, reconciliation, support, and error handling alongside wallet and network costs. A free wallet is not a cost-free payment operation. |
|---|
| When is an order ready? | The application checks the configured invoice and settlement rule, then records one fulfillment decision. | The provider’s payment status and payout availability can be different milestones. Define which one the business needs before fulfillment. | Someone checks the chain, amount and destination, matches the invoice, and authorizes release. Document who can make that decision. |
|---|
| Which assets are accepted? | Only the methods and exact contracts or mints configured and tested for the deployment. | Only the assets, networks, and customer locations accepted by the current product and account. | Only what the wallet can receive and the team can identify reliably. Supporting an asset in a wallet does not create invoice matching. |
|---|
| How are refunds handled? | A receive-only integration cannot sign refunds. The authorized merchant wallet controller completes the agreed refund process. | Follow the provider’s available refund mechanism, fees, and terms. Confirm whether refunds return the original asset or another amount. | The wallet controller sends the transfer and the team reconciles it to the original order and customer instruction. |
|---|
| What can interrupt receipt? | Endpoint failure, exhausted address capacity, chain conditions, or a software fault. Assign monitoring and reconciliation ownership. | Provider outages, account restrictions, payout holds and supported-network changes, alongside the underlying asset risks. | Missed payments, reused destinations, spreadsheet errors, unavailable staff, and wallet-access problems. |
|---|
| What remains your responsibility? | Wallet recovery, commercial terms, support decisions, refund authorization, and a verified handover from the operator. | Understanding the provider agreement, account compliance, customer support, and a usable export of payment records. | All of those business decisions plus the invoice, monitoring, and reconciliation workflow itself. |
|---|