We add a payment to an open order through the Clover REST API when a merchants selects Cash a payment in our app. We capture the active employee in the app and send this to our server where we call the Create a Payment Record on an Order endpoint using the active employee ID passed from the app.
This works fine in the sandbox environment, but in production the resulting employee on the payment is the default employee of the Clover account.
We tried to update the employee on the payment using the update payment endpoint, but we get a 200 response, but the employee is not updated.
We're using the oauth token obtained from within the app for the Clover account to perform these API calls.
Can someone investigate this seemingly incorrect behavior in prod?