What each payout record proves
Link the records with one payout reference, while keeping the royalty calculation, wallet operation and network transfer distinct.
| Record | What it establishes | Keep it separate from |
|---|---|---|
| Royalty statement | The amount calculated under the publishing agreement | A transfer instruction or wallet balance |
| Approved payout instruction | Payee, asset, network, amount and authorisation | Provider acceptance or network confirmation |
| Provider history | An account operation or status shown by the wallet service | A public transaction unless a hash is supplied |
| Network transaction | An on-chain transfer to a specified address | The recipient’s internal crediting decision |
| Recipient confirmation | The payee can see the expected asset and amount | The original royalty calculation |
Start with the royalty agreement and approved payment method
A royalty calculation and a wallet transfer are different records. The royalty statement establishes how the publisher calculated an amount under the author’s agreement; the payout record establishes how that amount was sent and what reached the recipient. A digital-asset option adds a settlement path to the workflow, but it does not change the edition, territory, sales channel, royalty base or rate used in the calculation.
Begin with the governing documents. Confirm that the agreement or a later written election permits payment in a digital asset, identifies who bears conversion and network costs, and states which currency fixes the obligation. Verify the payee’s legal identity and the approved destination through the publisher’s normal change-control process. An email requesting new wallet details should be checked through a previously verified channel before the payee record is changed.
Choose the wallet route by custody and settlement record
Next choose the wallet route by who controls the signing keys, how the recipient can access the funds, and which records each party can export. A custodial wallet places technical key storage with a provider and typically records balances and operations in an account history. A self-custody wallet leaves signing authority with the holder, who must protect the recovery method. An exchange account may add trading functions but can involve separate account balances and withdrawal rules. These options answer different operational needs; they are not interchangeable merely because each can display a token balance.
Coinhold’s wallet overview, dated 2 September 2026, describes its wallet as custodial and separates Main, Trading and Card account functions (Coinhold Wallet overview). Its guide explains that supported operations depend on the account, country and coin. A publisher considering any named wallet should verify the recipient’s actual deposit screen and current terms rather than infer support from a brand name or a general coin list. The wallet provider’s own interface determines which asset and network are available to that account at the time of payment.
Match the asset and network at both ends
A stablecoin ticker is not a complete transfer instruction. The publisher and recipient must identify the same asset on the same network, then confirm the destination address and any required reference field. Coinhold’s send-and-receive guide, dated 2 September 2026, instructs users to choose the coin and network and verify them before sending (Coinhold send-and-receive guide). The sender should compare the coin, network, address and amount on the final review screen before authorising the transfer. If the recipient’s wallet does not show the exact asset-network combination, pause the payment and agree on another route instead of substituting a visually similar address.
Custodial and self-custody routes also produce different evidence. A custodial provider may show an internal balance movement or a blockchain withdrawal; those are distinct events. A self-custody receipt can be checked against the transaction on the relevant network. Record which event satisfies the publisher’s payment policy: a submitted instruction, a provider-confirmed transfer, a network transaction, or the recipient’s confirmed credit. Do not label an instruction as received merely because it left the publisher’s queue.
Reconcile conversion, fees and the author’s receipt
Conversion should remain a separate ledger step. If the royalty is calculated in pounds or dollars but paid in a stablecoin, preserve the original payable, the quote or rate used, the time it was accepted, any spread or service fee, and the resulting token amount. Coinhold’s converter guide, dated 9 September 2026, says its quote is time-limited and that a completed conversion appears in transaction history (Coinhold Converter guide); the publisher should retain the quote and confirmation applicable to its own operation. A later conversion by the author is a separate transaction and should not be folded into the publisher’s payout amount.
A useful payout ledger makes the path visible without exposing credentials. Link the royalty statement ID to the approved payee, selected asset and network, destination-change approval, instruction timestamp, transaction reference, gross amount, fees, net amount and recipient confirmation. Keep the provider record and public transaction record as separate evidence where both exist. Never ask an author to send a seed phrase or private key as proof of receipt; a transaction reference or account statement is sufficient for reconciliation.
Keep a payout trail that can be reviewed later
If the transfer is delayed, first identify its current state. Check whether the provider has accepted the instruction, whether a network transaction hash exists, and whether the recipient’s wallet displays a pending or credited deposit. If an address or network mismatch is suspected, preserve the original instruction and contact the relevant provider through its published support channel. Do not issue a second payment until the first attempt has been traced, because a delayed credit and a failed transfer require different remedies.
At period close, reconcile the sales report to the royalty calculation, the payable ledger and the settlement record. Differences should be assigned to a specific cause such as a rate adjustment, conversion, fee, failed transfer or timing difference. The statement should retain enough information for another reviewer to reproduce the payable and follow the payment without access to the author’s wallet credentials. That separation protects both the accuracy of royalty accounting and the privacy of the recipient.


Publishing decisions: reader questions
Does a wallet receipt change the royalty calculation?
No. The publishing agreement and sales records determine the royalty; the wallet record documents the separate payout step.
Can a publisher assume a wallet supports a specific stablecoin network?
No. The sender and recipient should confirm the exact asset and network in the accounts used for that payment.
What should the publisher retain after an on-chain payout?
Keep the approved instruction, asset and network, destination-change review, transaction reference, amount, fees, valuation basis and recipient-side status.
Should an author share a recovery phrase to confirm payment?
No. Use a transaction reference or wallet history; never request private keys or recovery phrases.
