payment protection terms

maxi@domains:~$ cat legal/multisig-terms.md

payment protection terms

last updated 2026-10-30. effective 2026-10-31 (12:00 AM Eastern). operator: PixelMint LLC, contact [offers@maxi.domains](mailto:offers@maxi.domains).

launch phase: until Jan 3, 2027, maxi.domains sells only its own (house) domains. PixelMint LLC is the seller, you pay our own wallet directly, and no multisig payment is involved. third-party listings, seller accounts and the 2-of-3 multisig settlement open on Jan 3, 2027; the parts of this page about them apply only from that date.

these payment protection terms are part of the terms of service. they apply to every sale of a third-party domain on maxi.domains. if they and the terms of service ever disagree, the terms of service win. plain-language steps and wallet guides are on how it works.

1. which sales use the multisig payment

  • third-party domains (listed by sellers) are sold only through the 2-of-3 multisig settlement described here.
  • house domains (owned by PixelMint LLC) are direct sales: you pay our own wallet, we are the seller, and no multisig payment is involved. sections 2 to 8 do not apply to them; the refund policy does.

2. how the multisig payment works

  • each order gets its own bitcoin address, made from three public keys: one from the buyer, one from the seller and one from PixelMint LLC (a fresh key for each order). any two of the three keys must sign to move the funds held in the order's multisig payment address.
  • PixelMint LLC only co-signs: we add our signature to a transaction that the buyer or the seller has also signed. we never have unilateral control of the funds held in the order's multisig payment address, and we cannot move, take or keep them on our own. our server stores only public keys; our signing key is kept offline.
  • the buyer and the seller each keep their own key. we cannot sign for you or recover a lost key.
  • before paying, the buyer gives a multisig public key, signs a practice transaction that can never be broadcast, and checks in their own wallet that the order's multisig payment address is the 2-of-3 address with their key in it. the seller does the same key test before the listing is approved, and checks the address of each sale.

3. payment

  • send the exact amount shown, to the order's multisig payment address only. the buyer has 120 minutes for the key steps and then 120 minutes to pay; after that the order is cancelled and the domain becomes available again.
  • we wait for the number of confirmations shown on the order page.
  • underpaid: the order page shows what is missing. send the rest to the same address.
  • overpaid: the release pays out everything that arrived at the multisig payment address. if you paid too much, do not sign the release: open a dispute. we cannot return only the excess; we can co-sign a refund of the whole payment (minus the network fee), and you can then buy again at the right amount.
  • paid after the order was cancelled or expired: the payment is refunded as in section 6.

4. delivery

  • after the payment confirms, the buyer gives an account id at the domain's registrar, and the seller pushes the domain to that account. sellers should push within 3 days of being asked. if the seller has not pushed 7 days after being asked, the buyer may ask for a refund.
  • while an order is open, the seller must not sell, transfer or list the domain anywhere else.

5. release

  • once the seller reports the push, we prepare the release transaction: 95% of the amount that arrived at the multisig payment address to the seller's payout address, and our 5% fee. the network fee of the release is paid out of our fee.
  • the buyer confirms receipt by signing the release, and we co-sign. a buyer must not sign before the domain is in their registrar account.
  • 3-day fallback: if the buyer has not signed 3 days after the push was reported, we check whether the domain arrived in the buyer's registrar account (for example by WHOIS/RDAP, registrar records or the buyer's confirmation) and record that evidence. if it did, the seller signs and we co-sign the same release. we never co-sign a fallback release without that check.
  • the sale is final once the release is broadcast.

6. refunds

  • a refund is signed by the buyer and PixelMint LLC. it sends everything that arrived at the multisig payment address to an address the buyer enters (twice) on their order page.
  • the buyer pays the network fee of the refund: it comes out of the refund. if that fee would be more than 10% of the amount, we check with the buyer before we co-sign.
  • the cases in which a refund is owed are in the refund policy.

7. disputes

  • either the buyer or the seller can open a dispute from their order page. while a dispute is open we do not co-sign a release or a refund on that order. a release or refund that is already fully signed can no longer be changed by a dispute.
  • we respond within 2 business days and decide using registrar records, WHOIS/RDAP and what both sides send us.
  • disputes are all-or-nothing. we co-sign either the whole release to the seller or the whole refund to the buyer (minus the network fee). we never split the funds held in the order's multisig payment address. our decision about which transaction we co-sign is final as far as our co-signature goes; it does not limit any claim the buyer and the seller have against each other.

8. bundles

  • a bundle is several domains sold together in one order, for one payment, to one multisig payment address.
  • bundles are all-or-nothing. the seller has 14 days from the funding of the order to deliver every domain in it. we send the seller warnings on days 3, 5, 7, 9 and 13.
  • if any domain has not been delivered by day 14, the buyer gets a full refund (signed by the buyer and us; the buyer pays the network fee), the seller receives no funds, and the seller may lose any domains already pushed. there are no partial releases or partial payouts.
  • if the seller has reported delivery of every domain by day 14, we check the delivery before anything is released, as in section 5.

9. if we stop operating

the buyer and the seller hold two of the three keys and each have the order's wallet file, so together they can move the funds held in the order's multisig payment address without us. our 5% fee is still owed on a sale completed that way (see section 3 of the terms of service).

10. what we are not

we are not a bank. we hold one of the three keys of each multisig payment address and can only co-sign; we never have unilateral control of the funds held in the order's multisig payment address. for third-party domains we are not a party to the sale contract between the buyer and the seller. we are not a registrar. our liability is limited as set out in sections 10 and 11 of the terms of service.

operator: PixelMint LLC. contact: [offers@maxi.domains](mailto:offers@maxi.domains). these terms are governed by the laws of the State of Florida, USA.