Understand account states
Separate account creation, confirmed email, submitted request and an entitlement actually granted. Each state answers a different question. If a page asks for payment while you believe you already qualify, do not infer that your right disappeared or that you must pay again. Begin by reading your account status.
Use the relevant path
Offers describe subscriptions; the partner route describes its conditions; the account area shows your situation. A broker deposit document is not a COF subscription receipt. Keep amount, currency, date and legal entity separate, and do not post them in public conversations.
Report a useful discrepancy
Record the page, visible message and type of entitlement expected. Send documents only through the intended account channel. Never include a password or access key in a support request. The team must reconcile the request with your identity before confirming rights; marketing copy does not replace that check.
Identify the step that needs evidence
When access appears incomplete, distinguish the created account, submitted evidence and actually validated right. A submission confirmation establishes submission; it does not establish completed validation. Keep the process references without publishing personal information.
A useful support request identifies the page, the right expected under the offer and the visible status. Do not send a password or key. Readers can compare account information with offer terms before concluding that there is a service issue.
Keep access rights distinct
Access to content, a room and a feature may depend on different conditions. This guide neither creates nor validates those rights. It helps prepare a readable file for the existing process.
Your verification grid
| Item | Document or check to request |
|---|---|
| Registration | Check the displayed account state without sharing a password. |
| Account identity | Use the same account journey to locate the relevant request. |
| Evidence | Name the evidence type and sending status without publishing private data. |
| Entitlement | Read the access actually granted, its scope and any duration. |
| Mismatch | Record URL, message and expected entitlement for a precise support request. |
Practical questions
Does sending evidence prove active access?
No. Sent, received, reviewed and validated are separate states. A sending confirmation does not prove an entitlement was granted. Retain the request reference and read the state displayed in the relevant space.
Must I pay again if a page offers payment?
Do not infer an obligation from one screen. Compare account status with offer terms and report the mismatch through the intended journey. Never include a password or key in a support request.
To complete this file: VIP trading membership: compare access and price ; Broker withdrawals: documents to read before depositing.
Sources and limitations
COFIATRADING — offres, espace et preuves actuels. Editorial consultation: 8 October 2026. Supplier statements do not replace independent checks. Re-read terms at the time of your decision.
COFIATRADING has commercial relationships with partners presented on the site. This guide is educational, without personalised investment advice. Trading involves capital loss risk; past performance does not guarantee future results.
Continue checking: current offers and access, public evidence, Desk space and Academy resources.