Crakey Protection
Follow eligible order funding, private delivery, buyer confirmation, disputes and mutually exclusive release or refund outcomes.
Pre-launch release: checkout, payments, payouts and external email are disabled. Use designated test accounts and synthetic documents only. These pages explain this release; they do not announce a public launch.
1. Eligible payment protection
Checkout and payments are disabled in this release. The following explains the supported order workflow when separately approved payment services become available. An eligible order must have verified funding before delivery; pending payments, screenshots and browser redirects are not funding evidence. Protected funds remain associated with the order until an authorized outcome.
2. Seller delivery and buyer access
Sellers must provide the product and restrictions stated in the listing. For supported digital-code orders, the allocated code is delivered privately and can be revealed only by the authorized buyer when the order permits it. Instant-code handling does not promise instant delivery for every category. Keep communication and evidence in the order conversation.
3. Buyer confirmation
Check the delivered product before selecting Confirm & Release Funds. Normal buyer-confirmed release requires eligible delivered status and a seller star rating from 1 to 5; a written review is optional. Confirmation releases the protected amount to the seller’s internal wallet. It does not send a payout to a bank or payment provider.
4. Problems and disputes
If an eligible funded or delivered order has a problem, use Open dispute before releasing funds and describe the issue accurately. An active dispute blocks normal buyer-confirmed release. Authorized staff review the order and can resolve it through the permitted release or refund path. This is not an automatic refund guarantee or a promise of a response deadline.
5. Release and refund limits
Release and refund are mutually exclusive for the protected amount. A refunded order cannot be released, and the normal protection workflow cannot refund an already released amount. Repeated processing must not create duplicate credits. The supported refund credits the buyer’s internal wallet; it is not an automatic reversal to an external payment method.
There is no enabled scheduled automatic release or published protection countdown in this release. Off-platform payments, unsupported transactions and promises made outside the order are not covered. Statutory rights and provider dispute processes, where applicable, are separate from these application controls.