Verify a document

Is this receipt or statement genuine?

Every execution receipt from 777 Raptor and every statement from the client portal carries a reference and a verification code. Enter both and GIO4X answers from its own records, with the figures the document should state. No sign-in is needed.

What can be checked

Execution receipt: One filled order on 777 Raptor, demo or live. Its reference is the order number.
Monthly statement, year export: One account’s totals for a month or a calendar year. Its reference begins with S-.

A document issued before codes were introduced carries none and cannot be checked here. To check a web address or an e-mail sender instead, use Verify a link.

The check

Enter the reference and the code.

What “genuine” means, exactly.

For an execution receipt: The terminal’s database works the code out again from the order as it holds it now: the order number, instrument, side, size filled, fill price, the time of the fill and whether the account is a demo. A match means the terminal holds that filled order with exactly those values, and they are shown to you. The code does not cover the costs, the events or the close reason printed lower on a receipt.
For a statement: A statement is not a stored document: the portal works it out when its holder asks, and records the totals it printed. A match means the portal issued a statement with that reference for an account of the stated kind and period, and the totals it printed are the ones shown to you. The totals are not worked out again at the moment of the check, because the trading figures are held by the terminal’s database.
“The records have changed since this was issued”: Shown for a statement when the portal has since printed the same account’s statement for the same period with different totals. A month that was still running, a trade that closed afterwards and a corrected record all do that. It is not a finding that the document was forged: it was genuine when issued and is out of date now.
“Not verified”: One answer for a wrong code and for a reference GIO4X does not hold, so that this page cannot be used to find out whether an order or a statement exists.

What this check does and does not do

It shows only what the document states. A receipt’s instrument, side, size, price and time; a statement’s period, account kind and printed totals. Never a name, an e-mail address, an account number or a balance.
It leaves the comparison to you. A genuine code on an altered page is still a genuine code. The check is complete only when every line shown here agrees with the document in your hand.
It is limited. Ten failed checks of one reference in an hour, or too many checks altogether, and the answer is “too many checks” for a while. The limit is kept in the database.
It stores little. For each check the database keeps a one-way hash of the reference typed, the time and whether it matched, for one day, to apply that limit. Not the code, not your address, nothing about you. Answers are never cached.
A demo document says so. A demo receipt is a fill at a simulated price with virtual funds, and a demo statement’s amounts are virtual. A genuine demo document is not evidence of trading with real money.

If a document does not verify and you believe it should, write to GIO4X through the contact page .

Continue

Fetching the page

What “genuine” means, exactly.

For an execution receipt

The terminal’s database works the code out again from the order as it holds it now: the order number, instrument, side, size filled, fill price, the time of the fill and whether the account is a demo. A match means the terminal holds that filled order with exactly those values, and they are shown to you. The code does not cover the costs, the events or the close reason printed lower on a receipt.

For a statement

A statement is not a stored document: the portal works it out when its holder asks, and records the totals it printed. A match means the portal issued a statement with that reference for an account of the stated kind and period, and the totals it printed are the ones shown to you. The totals are not worked out again at the moment of the check, because the trading figures are held by the terminal’s database.

“The records have changed since this was issued”

Shown for a statement when the portal has since printed the same account’s statement for the same period with different totals. A month that was still running, a trade that closed afterwards and a corrected record all do that. It is not a finding that the document was forged: it was genuine when issued and is out of date now.

“Not verified”

One answer for a wrong code and for a reference GIO4X does not hold, so that this page cannot be used to find out whether an order or a statement exists.

What this check does and does not do

It shows only what the document states. A receipt’s instrument, side, size, price and time; a statement’s period, account kind and printed totals. Never a name, an e-mail address, an account number or a balance.

It leaves the comparison to you. A genuine code on an altered page is still a genuine code. The check is complete only when every line shown here agrees with the document in your hand.

It is limited. Ten failed checks of one reference in an hour, or too many checks altogether, and the answer is “too many checks” for a while. The limit is kept in the database.

It stores little. For each check the database keeps a one-way hash of the reference typed, the time and whether it matched, for one day, to apply that limit. Not the code, not your address, nothing about you. Answers are never cached.

A demo document says so. A demo receipt is a fill at a simulated price with virtual funds, and a demo statement’s amounts are virtual. A genuine demo document is not evidence of trading with real money.

If a document does not verify and you believe it should, write to GIO4X through the contact page .