Bet Status Update: The primary goal of the /payments/close method is to update the current status of a bet. The Partner can signal that a bet has been finalized (closed) or reactivated (open) by sending the appropriate flag in the request.
Synchronization of Bet Lifecycle: By using this endpoint, both the Partner and BETCORE can maintain consistent, up-to-date information about the bet's state. This synchronization is essential to prevent further transactions from being processed on a bet that has already reached its final state.
Control over Transaction Flow: Closing a bet ensures that no additional transaction requests (such as bet adjustments or extra payments) will be sent for that particular bet. If there's a need to process further transactions on a previously closed bet, BETCORE can transition its status to open, process the necessary operations, and then close the bet again afterward.
