•   over 11 years ago

Hosted MintChip Debit/Credit Logs, value for seconds is always "00" in 'transactionTime'

Why is the value for seconds always being returned as "00" in the debit and credit log services? Can this be fixed to return accurate values for seconds? Because of this bug, I'm getting back data in my results that looks like this:

{
amount = 7;
challenge = 3094E3C2;
currencyCode = 1;
index = 72;
logType = 1;
payeeId = 1310000000005127;
payerId = 1310000000005119;
transactionTime = "21 June 2012, 20:37:00";
},
{
amount = 1;
challenge = D81809B3;
currencyCode = 1;
index = 73;
logType = 1;
payeeId = 1310000000005127;
payerId = 1310000000005119;
transactionTime = "21 June 2012, 20:37:00";
}

These two transactions didn't actually happen at the same time, but the data being returned makes it look as though they did.

  • 2 comments

  •   •   over 11 years ago

    It could probably be fixed in a later version of the ASN.1 packet, but not as it stands now; the DateTime of the transaction is being stored in a three-byte data structure; if that stored number-of-seconds, you'd only have 194 days of transaction time to record - just enough for the length of the competition! By using this value to record minutes, they've got just under 32 years worth, which I suppose is suitable for now.

    Generally, the ASN.1 packet is extraordinarily chintzy; while the three-byte block for Value is enough to carry $CAD 167,772.15, that doesn't help if your CurrencyCode is for Vietnam or, heaven help you, Zimbabwe. I hope that this field gets revisited, if it's the represent a currency's fractional portion; giving a few more bytes would even allow for true microtransactions at the sub-cent level.

  •   •   over 11 years ago

    Ah okay. Thanks for explaining this. Then I will just be happy that I have an accurate value for minutes. ;)

Comments are closed.