Statements Time Question
Hi,
I noticed that, when requesting statements, both the "buy"- and "sell"-type entries have the same time-stamp (given the same Contract ID). Shouldn't "sell"-type entries have a later time-stamp representing the contract expiry / auto-sell? I noticed that this is even so when viewing statements on binary.com's web platform and am pretty sure this was never the case before...
{ "echo_req": { "statement": 1, "limit": 2, "description": 1 }, "statement": { "count": 2, "transactions": [ { "balance_after": "12512.3700", "shortcode": "PUT_FRXEURUSD_1_1453447541_1453447661_S0P_0", "contract_id": "7211911768", "longcode": "USD 1.00 payout if EUR/USD is strictly lower than entry spot at 2 minutes after contract start time.", "transaction_time": 1453447541, "action_type": "sell", "amount": "1.0000", "transaction_id": "14273767448" }, { "balance_after": "12511.3700", "shortcode": "PUT_FRXEURUSD_1_1453447541_1453447661_S0P_0", "contract_id": "7211911768", "longcode": "USD 1.00 payout if EUR/USD is strictly lower than entry spot at 2 minutes after contract start time.", "transaction_time": 1453447541, "action_type": "buy", "amount": "-0.5000", "transaction_id": "14273707108" } ] }, "msg_type": "statement" }
Best Answer
-
@DragonFly81 this has been fixed. Please check and verify it. Please note that in case of
sell
transaction there will be new fieldpurchase_time
just in case you need it.
Answers
@DragonFly81 We will check and update you accordingly
@Raunak Looks good - thanks for the effort and update.