The transaction ID is set asynchronously from the callback sent by QuickPay. This callback has not necessarily reached the shop by the time a customer returns to the shop/receives the order confirmation. It is therefore, at the time being, not possible to consistently provide this information.
The transaction ID is set asynchronously from the callback sent by QuickPay. This callback has not necessarily reached the shop by the time a customer returns to the shop/receives the order confirmation. It is therefore, at the time being, not possible to consistently provide this information.
Thats unfortunate as it is required by NETS / Teller in order to get an acquirerer agreement.
I resent an order confirmation mail, after checking that the transaction ID is present in the order. Shouldn’t it be present then?
Cheers, K
I don’t know if it should. It might lead to a confusing experience if there is an inconsistent behavior of where and when the transaction ID is presented in a dialog with the customer. It might be a good idea to implement it as a feature of choice though. I will add it to the roadmap!
