Hi,
It might not necessarily be a bug of our module. We had this bug with one client of ours, but it doesn't occur anymore.
PAY. might work fine with it, but we had problems in the beginning. I have a feeling that `order_payment` records are added later, and that in some cases the payment provider only has the old reference.