Binary.com Statement Shows Loos for Win Trades
Hello,
i dont understand this think, can please somebody explain what is wrong.
Look to the attachet picture, you can see the price is lower then the entry and this is also a sell trade, but it is showing as a loose trade, why is this so?
https://us.v-cdn.net/6026953/uploads/editor/c4/gy0bxxowpk0h.png
From Binary.com i have get a email info with following text:
"Please note that you will need to access the Portfolio page in order for the system to close the contracts and the profit will be credited to your account."
Does somebody understand what this mean?
The trades have been open from the API, is there a special rule for trades which have been send with API, do they show always loos? I really want to understand this think, please help somebody.
Normaly when you send the order and the trade is opened everythink is done, i dont understand this statement, what must i do else after the trade have been open.
Comments
@BinaryComUser if possible can you provide your client loginid so that we can debug?
For this
"Please note that you will need to access the Portfolio page in order for the system to close the contracts and the profit will be credited to your account."
Please note that there is difference between contract expiry and contract sell. Contract expiry is when end time is reached but if contract is not manually sold then sell time will be after contract expiry because it is handled by our system. But if you manually want to tell system to sell expired contracts then you can go to portfolio page or if you are using api then use this call https://developers.binary.com/api/#sell_expired
I can tell you this Guys, i have find a bug in your system and i have find the solution with help of another great binary.com coder, if you want to know the bug offer me somethink i will tell it you, give me a free live account or money then i tell you what a bug you have there which produce that error. I have slove it already.
Why i aks money for it? Because it have cost me also money to get the solution and it have cost me many days waitting for the useless support from binary.com workers, where nobody till today could find the problem.
Thanks for your feedback and offering to help. We are aware there is a bug on our system, we already fix it and it will be out on next release.