OrderAuthorization and OrderPayment Getting Reset

[OpIvy]

I am working on adding a fake Auth-Capture process to a Stripe payment module.  Its a 'fake' one because Stripe doesn't support the Auth-Capture model, but its necessary for my business.

What I'm seeing is this:  after the payment Capture, the OrderAuthorization.complete is set to True and the OrderPayment is updated to reflect the current payment.  The payment processing is complete and everything moves on.  Then, quite quickly, the OrderAuthorization is reset to False and the OrderPayment is reverted back to its original pre-capture state.

I've added some sleep() calls in at various points and the data reset appears to happen after the payment processor has successfully completed.

Does anyone have a clue as to what would cause this?  I'm 90% certain my payment processor is setting and saving all the correct values.  Is there some master check that will wipe out a payment capture if some variable isn't set properly? 

[OpIvy]

I've done some more testing and the problem appears to be somewhere in the order admin section.  I am triggering the capture of the authorization by updating the order status to 'Shipped'.  This successfully captures the payment and updates the OrderAuthorization and OrderPayment tables.  However, as the processing continues, it appears that an old instance of those 2 models is being saved, and the old data is being saved with it.

What would cause that to happen?