Topics
Topics
Earnings / After the event
Movago organizers manage event listings, ticket sales, attendee access, and post-event earnings.
Movago organizers manage event listings, ticket sales, attendee access, and post-event earnings. This article explains how organizers receive ticket earnings and payouts, including the main workflow, relevant conditions, and what to expect in the app.
Connect the payout account the earnings screen uses. Ticket money is released when you confirm an event that has ended. Earnings can be viewed for 7 days, 30 days, 90 days, or 1 year. You can open one earning, request a payout from the withdrawable balance, turn automatic payout on or off, and cancel a payout that is still cancellable.
Outstanding penalties, if the cancellation policy charged you, show on the earnings side and are taken from later earnings.
The app should show the earning after the event is confirmed, and the payout after you request it or automatic payout runs.
Confirming before the event has ended does not release the money. A payout needs a connected account and a withdrawable balance that meets the minimum shown on the payout screen. Settling money is not the same as money you can withdraw. A cancelled event does not get confirmed, so that is not how you release ticket earnings.
Event publication, ticket availability, scanner access, and earnings release occur at different stages of the event lifecycle. Changes become visible when the corresponding action succeeds; an unavailable button, incomplete setup, or pending payment means the next stage has not yet been reached. Always rely on the status displayed for the particular item rather than assuming it has progressed.
Review the eligibility requirements and status described above. Missing required information, an earlier incomplete step, or an account-level limitation may prevent the action. Where the application displays a specific reason or a required next step, that message is the best guide to resolving the issue. For payments or decisions requiring review, use the relevant in-app support channel rather than assuming an automatic reversal or approval.
Did this answer your question?