Module assumes a certain call order of transaction-callback and transaction-accept?

About a week ago the commerce_dibs-module suddenly stop working for a webshop I am part of building. After completing payment you are sent back to checkout_review, money authorized at dibs, but an order is NOT created. I tracked down the problem to what seems to be an assumption that "transaction_callback" is always run before "transaction_accept" in dibs-api.

When the transaction is first created in function commerce_dibs_redirect_form it's status is set to COMMERCE_PAYMENT_STATUS_PENDING.

In transaction_accept we have:

if ($commerce_transaction->status !== COMMERCE_CREDIT_AUTH_ONLY) {
  drupal_set_message(t('Unable to verify your payment, please try again.'), 'error'); 
  drupal_goto('checkout/' . $order->order_id . '/payment/back/' . $transaction['params']['payment_redirect_key']); 
}

Which causes the redirect to the review step.

The only place where I could find $commerce_transaction->status is set to COMMERCE_CREDIT_AUTH_ONLY is in transaction_callback:

foreach ($commerce_transactions as $commerce_transaction) {
  $delta = $commerce_transaction->payload['delta']; 
  $commerce_transaction->message = 'Payment completed at DIBS'; 
  $commerce_transaction->status = COMMERCE_CREDIT_AUTH_ONLY; 
  $commerce_transaction->payload['dibs_id'] = $transaction['dibs_split_payments'][$delta]; 
  commerce_payment_transaction_save($commerce_transaction); 
}

so it obviously needs to be run BEFORE transaction_accept, but I logged the order using watchdog and it does not!

What puzzles me is that every drupal-site using the dibs-module should have this problem, and if so why is there not more issues reported?