Know what happens next.

Direct payment links

Funds go from the payer’s wallet directly to the recipient. Vino charges no service fee and cannot cancel, reverse or arbitrate that transfer. Network fees are additional. Supported direct-payment assets are USDC on Base, Polygon, Arbitrum, Ethereum and Solana; USDT on Ethereum; and EURC on Ethereum, Base and Solana. Always use the token and network named in the request. Solana payments may also require the payer to fund the recipient token account’s rent.

1. Pending or interrupted: save the transaction hash, reopen the original request, sign in with the paying wallet, and select Verify receipt. Wait for network finality. Do not send another payment while the first is unresolved.
2. Failed transaction: a verified failed transaction did not complete the requested transfer, but may have used gas. Verify the failure before reviewing a fresh payment.
3. Wrong amount or duplicate: automatic verification accepts one exact transfer for a request, not a combined total or excess. Contact the recipient using your previously agreed channel. Agree whether they will return the excess, return a duplicate, or record a separate payment manually. Do not send a top-up without that agreement.
4. Expired or late: the app does not offer new payments after expiry. A transfer mined after expiry can still reach the recipient, but will not automatically mark the request paid. Share the original request, chain and transaction hash with the recipient; agree fulfilment or a refund before paying a replacement request.
5. Wrong network or token: preserve the transaction hash and contact the recipient. Recovery depends on their control of the receiving address and the asset/network; recovery is not guaranteed. Vino does not bridge, swap or recover funds automatically.

Any direct-payment refund is a separate transfer signed by the recipient. Both parties must agree the amount, return network, original payer address and gas responsibility. Verify the original sender on-chain; never accept a substituted refund address from an unsolicited message. A recipient’s manual acknowledgement does not create a Vino finalized receipt.

Vino can help diagnose a receipt problem at emathews924@gmail.com. Include the public transaction hash, network and request ID, with no wallet secrets. Support cannot compel a recipient refund; no guaranteed response time is offered during this pilot.

Cross-chain USDC

Circle CCTP Standard transfers have a separate preview and recovery page. New transfers are disabled until live acceptance is complete. A quote does not reserve a fee or deliver funds. The payer covers source approval and burn gas, destination mint gas, and the maximum Circle fee shown before signing; Vino charges zero.

A successful burn cannot be cancelled or refunded by Vino. Keep the transfer ID and both transaction hashes. Recovery completes the original destination mint after Circle attestation. Never burn again because an attestation or RPC is delayed. Only a finalized destination mint is labelled delivered. This is separate from escrow settlement and does not swap assets.

Escrow: terms before funds

The pilot supports native USDC on four registered networks. Each case is capped at 1 USDC and each deployed contract at 3 USDC outstanding. The contracts have not been independently audited. Both parties should keep a copy of the agreement and verify the receiver, amount, deadlines and review period before funding.

New agreements use zero-fee contracts: Vino deducts nothing from awards or refunds. For a full 1 USDC award, the receiver gets 1 USDC. Wallet gas is separate and donations are optional. Historical contracts are immutable and retain their original 0.5% receiver-award fee; they are available for existing-case review only. Create new agreements on the current contracts.

1. Both parties agree to the terms in the workspace. The sender approves the exact USDC allowance and funds the contract.
2. The receiver accepts the funded case, then delivers before the agreed deadline. Either party may cancel an unaccepted funded case for a full sender refund.
3. The sender can approve payment. After delivery, a dispute must be opened before the review deadline; otherwise a timeout transaction can pay the receiver.
4. A dispute opens 12 hours for evidence, followed by 12 hours for judgement. Save supporting text and record its hash on-chain within the evidence window. The arbitrator considers both sides and signs an allocation.
5. If the arbitrator misses the deadline, a timeout transaction can refund the entire deposit to the sender. An unaccepted or undelivered case can also time out to the sender after its applicable deadline.

Deadlines do not move money automatically. A person must submit the applicable transaction and pay gas. The pilot does not run an operator-funded timeout service. Both parties can agree a matching mutual resolution while the contract permits it. A completed settlement cannot be reopened through this contract.

Evidence and availability

Evidence is plain UTF-8 text, up to 64 KiB per item, visible to the parties and arbitrator in the workspace. It is retained for 30 days. Keep your own copy; hashes and transactions remain public on-chain. See the privacy policy.

Automated dispute alerts and deadline reminders assist the operator. They do not guarantee a human response. The pilot has no committed round-the-clock staffing or response SLA. Use the agreed contract deadlines and timeout rights; do not rely on an email reply to extend a deadline. Email is never an instruction to sign a transaction.