Check the original operation first
For a failed or uncertain command, keep its operation reference, job or checkout ID, error code and UTC attempt time. Follow the recovery guide before repeating a payment or approval. A pending payment, a closed job and a rejected request need different next steps. Reading status does not send a support message or approve a refund.Contact support through the API
The support API supports an account conversation with an API key or a fresh wallet proof, and a paid job conversation with its private job secret. A checkout token is not a support credential. For an uncertain checkout, use its returned recovery instructions. If they direct you to account support, put the checkout references in the message text rather than adding a job selector for an unpaid order. Human support aims to respond within 24 hours. This is a target, not a guarantee of resolution or refund approval. After an uncertain send, read the conversation before deciding whether to repeat the message.Request refund review
For a supported paid custom job, store purchase or direct hire, use the refund-request instructions. A successful request pauses the job for human review; it does not immediately return money. For a creator-selected job with too few qualifying entries, select eligible winners first, then request review for the unfilled prize slots. Explain that the selected winners should be retained. Once review starts, further selection is blocked until the job’s state permits it.Other contact channels
WURK on X
Contact the official WURK account.
Creators and developers
Join the WURK community.