You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reading the payZen doc make me think about this var, is you have a very active shop, or very big amount of little payments, or even a long lasting implementation you could run into this issue because the id_transaction will be bigger.
An approach could be to add time values and concatenate the last 2 digits of the id_transaction (and zerofill for the 9 first) to generate a number:
(Year + Day + Month + Hour + Minute + Second) . xx
2019+8+7+11+51+27 = 2123
if the id_transaction is 250, you will end with 212350, one day in a long long long time, you will face the same issue in year 8814 if I'm correct ^^...
The best way is perhaps to simply store a daily counter, but it requires DB schema changes.
Reading the payZen doc make me think about this var, is you have a very active shop, or very big amount of little payments, or even a long lasting implementation you could run into this issue because the id_transaction will be bigger.
An approach could be to add time values and concatenate the last 2 digits of the id_transaction (and zerofill for the 9 first) to generate a number:
(Year + Day + Month + Hour + Minute + Second) . xx
2019+8+7+11+51+27 = 2123
if the id_transaction is 250, you will end with 212350, one day in a long long long time, you will face the same issue in year 8814 if I'm correct ^^...
The best way is perhaps to simply store a daily counter, but it requires DB schema changes.
SystempayBundle/src/Tlconseil/SystempayBundle/Service/SystemPay.php
Line 98 in 83c2492
https://payzen.io/fr-FR/payment-file/oneclick-payment/vads-trans-id.html
The text was updated successfully, but these errors were encountered: