Kaynak doğrulamalı araştırma: Kucoin / MEXC

Verified source facts

1. KuCoin says the web export can cover deposits, withdrawals, spot, margin, convert and fiat-related records and may include all sub-accounts when requested from a master account. 2. KuCoin documents a maximum one-year span per export, up to 20 reports per month, and a 30-day download-link lifetime. 3. MEXC separates general account-data exports from more specific Spot Orders, Futures Orders and Funding History exports. 4. MEXC advises splitting large requests into smaller batches when a record cannot be generated.

Comparison at a glance

1. Compare record scope on the same job

A platform comparison becomes useful only when both venues are measured against one job. For record scope, that job concerns which account events are included. Marketing pages frequently describe broad capability while the actual decision lives in a specific pair, contract, network, entity, or account tier. Build two evidence rows from the same timestamp, then list required event classes before exporting. Until that check is complete, neither venue earns the point.

The comparison should distinguish a published ceiling from an executable outcome. A fee table does not reveal slippage; a product menu does not prove regional eligibility; a security feature page does not prove the control is enabled on the reader's account. Record the route from public statement to authenticated evidence. The unresolved variable is undocumented product fields, so the scorecard must preserve that blank instead of awarding a speculative advantage.

For record scope, connect the finding to the reader's actual order plan rather than the other nine rows in the abstract. Document how which account events are included changes the entry, exit, monitoring, or fallback decision, and make the operator list required event classes before exporting. The remaining uncertainty—undocumented product fields—belongs in the dated scorecard. That produces a job-specific preference instead of a permanent winner.

2. Compare time range on the same job

For time range, that job concerns maximum span per request. Build two evidence rows from the same timestamp, then split periods with non-overlapping boundaries.

The unresolved variable is future interface limits, so the scorecard must preserve that blank instead of awarding a speculative advantage.

For time range, connect the finding to the reader's actual order plan rather than the other nine rows in the abstract. Document how maximum span per request changes the entry, exit, monitoring, or fallback decision, and make the operator split periods with non-overlapping boundaries. The remaining uncertainty—future interface limits—belongs in the dated scorecard.

3. Compare sub-accounts on the same job

For sub-accounts, that job concerns master-account inclusion and attribution. Build two evidence rows from the same timestamp, then retain account identifiers in the archive.

The unresolved variable is cross-entity coverage, so the scorecard must preserve that blank instead of awarding a speculative advantage.

For sub-accounts, connect the finding to the reader's actual order plan rather than the other nine rows in the abstract. Document how master-account inclusion and attribution changes the entry, exit, monitoring, or fallback decision, and make the operator retain account identifiers in the archive. The remaining uncertainty—cross-entity coverage—belongs in the dated scorecard.

4. Compare order versus trade on the same job

For order versus trade, that job concerns submitted orders versus actual fills. Build two evidence rows from the same timestamp, then reconcile both execution and balance records.

The unresolved variable is cancelled-order completeness, so the scorecard must preserve that blank instead of awarding a speculative advantage.

For order versus trade, connect the finding to the reader's actual order plan rather than the other nine rows in the abstract. Document how submitted orders versus actual fills changes the entry, exit, monitoring, or fallback decision, and make the operator reconcile both execution and balance records. The remaining uncertainty—cancelled-order completeness—belongs in the dated scorecard.

5. Compare funding records on the same job

For funding records, that job concerns deposits, withdrawals and internal transfers. Build two evidence rows from the same timestamp, then match TxID and destination network.

The unresolved variable is offchain transfer labels, so the scorecard must preserve that blank instead of awarding a speculative advantage.

For funding records, connect the finding to the reader's actual order plan rather than the other nine rows in the abstract. Document how deposits, withdrawals and internal transfers changes the entry, exit, monitoring, or fallback decision, and make the operator match TxID and destination network. The remaining uncertainty—offchain transfer labels—belongs in the dated scorecard.

6. Compare file format on the same job

For file format, that job concerns CSV, XLSX or PDF behavior. Build two evidence rows from the same timestamp, then preserve an original machine-readable file.

The unresolved variable is schema changes, so the scorecard must preserve that blank instead of awarding a speculative advantage.

For file format, connect the finding to the reader's actual order plan rather than the other nine rows in the abstract. Document how CSV, XLSX or PDF behavior changes the entry, exit, monitoring, or fallback decision, and make the operator preserve an original machine-readable file. The remaining uncertainty—schema changes—belongs in the dated scorecard.

7. Compare generation delay on the same job

For generation delay, that job concerns asynchronous report creation. Build two evidence rows from the same timestamp, then allow time before declaring data missing.

The unresolved variable is peak-time latency, so the scorecard must preserve that blank instead of awarding a speculative advantage.

For generation delay, connect the finding to the reader's actual order plan rather than the other nine rows in the abstract. Document how asynchronous report creation changes the entry, exit, monitoring, or fallback decision, and make the operator allow time before declaring data missing. The remaining uncertainty—peak-time latency—belongs in the dated scorecard.

8. Compare download expiry on the same job

For download expiry, that job concerns how long generated files remain available. Build two evidence rows from the same timestamp, then download into controlled encrypted storage.

The unresolved variable is future retention policy, so the scorecard must preserve that blank instead of awarding a speculative advantage.

For download expiry, connect the finding to the reader's actual order plan rather than the other nine rows in the abstract. Document how how long generated files remain available changes the entry, exit, monitoring, or fallback decision, and make the operator download into controlled encrypted storage. The remaining uncertainty—future retention policy—belongs in the dated scorecard.

9. Compare quota on the same job

For quota, that job concerns monthly export limits. Build two evidence rows from the same timestamp, then schedule complete archives before deadlines.

The unresolved variable is account-specific quota, so the scorecard must preserve that blank instead of awarding a speculative advantage.

For quota, connect the finding to the reader's actual order plan rather than the other nine rows in the abstract. Document how monthly export limits changes the entry, exit, monitoring, or fallback decision, and make the operator schedule complete archives before deadlines. The remaining uncertainty—account-specific quota—belongs in the dated scorecard.

10. Compare reconciliation on the same job

For reconciliation, that job concerns file totals versus live balances and chain evidence. Build two evidence rows from the same timestamp, then test a known period before relying on the archive.

The unresolved variable is support resolution outcome, so the scorecard must preserve that blank instead of awarding a speculative advantage.

For reconciliation, connect the finding to the reader's actual order plan rather than the other nine rows in the abstract. Document how file totals versus live balances and chain evidence changes the entry, exit, monitoring, or fallback decision, and make the operator test a known period before relying on the archive. The remaining uncertainty—support resolution outcome—belongs in the dated scorecard.

Decision scenarios

Scenario 1: when record scope becomes decisive

Consider a reader whose main constraint is which account events are included. The correct response is not to infer a universal platform or product winner. It is to list required event classes before exporting, retain the evidence, and define a stop condition before funds or permissions are committed. If the evidence changes, the decision must be reopened. This produces a repeatable operating rule rather than a one-time opinion.

Scenario 2: when time range becomes decisive

Consider a reader whose main constraint is maximum span per request. It is to split periods with non-overlapping boundaries, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 3: when sub-accounts becomes decisive

Consider a reader whose main constraint is master-account inclusion and attribution. It is to retain account identifiers in the archive, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 4: when order versus trade becomes decisive

Consider a reader whose main constraint is submitted orders versus actual fills. It is to reconcile both execution and balance records, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 5: when funding records becomes decisive

Consider a reader whose main constraint is deposits, withdrawals and internal transfers. It is to match TxID and destination network, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 6: when file format becomes decisive

Consider a reader whose main constraint is CSV, XLSX or PDF behavior. It is to preserve an original machine-readable file, retain the evidence, and define a stop condition before funds or permissions are committed.