Implementing state pattern in practise

I have use case which has physical mailbox and got some package there. My app should have state unlock, lock, payment. Unlock can perform every person if mailbox is empty. If it not empty just owner or person who got shared item. Locking can be performed by both persons. Also other person should pay for item, otherwise cannot use item. Using item is free until 1h after that is payable. Also we have 100 differnet mailbox.

The first implementation was done without state, but some change requestes propagates trought all apis. I was thinking if would be smart to use state/strategy pattern?

............................