Agree on the commercial obligation
Before discussing a wallet, establish the invoice amount, denomination and allocation reference. If the invoice is in USD but the proposed settlement is in USDC, confirm how the parties will determine the token amount and handle any difference. Do not silently substitute a token transfer for the agreed payment terms.
Give the supplier a clear point of contact for payment questions. Record the business role rather than exposing personal details in a reusable template. The commercial agreement belongs in the organization’s approved records, with an accessible reference in the payment packet.
Collect receiving instructions as a complete set
Request the exact asset, network, receiving address and any platform-specific instructions. A valid-looking address alone is insufficient. Confirm that the recipient controls or is authorized to use the destination and that its receiving service accepts the intended token on that network. If instructions change, verify the change through an established channel.
Bancoli’s USDC sending guide describes a beneficiary record, network selection, an optional memo and transaction confirmation. These features are useful to investigate for a repeat supplier workflow. They do not replace supplier verification, and a memo is not automatically the same thing as a destination tag required by another service.
Decide how completion will be recognized
Agree what evidence each side will use: transaction reference, provider status and invoice allocation. A confirmed on-chain transaction and a settled commercial invoice are related but distinct. The recipient may still need to identify the payment in its own records.
For a new route, follow the provider’s current instructions and the organization’s approval policy. Any limited test should be separately agreed, including its amount and how it will be accounted for. A successful earlier transfer does not validate a later changed destination or a different network.
| Invoice reference | DEMO-SUP-208 |
|---|---|
| Payment basis | Commercial terms recorded separately |
| Receiving instructions | Asset + network + approved destination reference |
| Verification | Role, date and established channel |
| Completion | Transaction evidence + invoice acknowledgement |
The packet contains references, not a real recipient address. Keep private supplier information in the approved business system, not in a public guide or shared demo.
Questions that come up
Can the supplier just send a QR code?
A QR code can carry data, but the team still needs to verify the asset, network, destination and commercial context.
What if the supplier requests another network?
Treat it as a changed route. Reconfirm support and costs before authorizing a transfer.
Sources and context
Product facts are distinguished from original process guidance and hypothetical examples. Check the current terms for your route.