Before you subscribe to MaxData: a practical verification worksheet

Start a subscription decision with a written description of the work you want to do. Then assemble the purchase terms you are willing to accept. This article sets out our proposed verification workflow: a worksheet for asking questions, recording official answers and deciding whether to proceed. Its checklists and examples are editorial recommendations, not statements of MaxData subscription policy.

We publish no prices, refund entitlements, renewal rules or assertions about supported integrations here. Our proposed workflow asks you to confirm those details in the applicable official offer and documents before making a payment.

Write a small acceptance brief

Our recommendation is to describe one intended task before comparing offers. A beginner might write: “I want to build and save a chart for a metric I am learning.” Someone evaluating notifications might write: “I want to combine conditions and inspect when the notification triggers.” Treat these as sample requirements rather than promises about any subscription.

The Max Terminal article describes Pro Charts as a tool for analysing on-chain, macroeconomic and exchange data, and describes creating and saving charts. We cite that documentation as a description of the tool rather than confirmation of access for a particular account. Max Terminal documentation.

In our proposed brief, add a required task, an optional task and a question that needs an answer. Keep the required task narrow enough to demonstrate. Instead of “advanced analytics,” write down the chart, configuration or notification you intend to inspect. Leave plan names blank until you have checked the offer you are considering.

Separate product descriptions from purchase evidence

Our proposed worksheet uses two separate entries: “documented function” and “access confirmed for this offer.” Put a help article in the first entry. Reserve the second for an official answer or offer that addresses the particular subscription you intend to buy. This distinction is a recordkeeping convention for this article.

For every required task, ask about access, limits, prerequisites and any additional charges. Record the exact offer name and the location of the answer. If the answer remains incomplete, mark the entry “unconfirmed.” Do not fill the gap with an assumption drawn from a screenshot, example or remembered description.

We also recommend keeping questions at the same level of detail across competing options. If you ask one offer about notification limits, ask the other about the same limit. If a task is optional, label it optional throughout the worksheet rather than letting it become an unstated purchase requirement.

Build a billing record before checkout

Our proposed billing record contains the amount due, currency, billing period, payment method and purchase confirmation document. Add a field for any additional charges and a field identifying where the complete amount is shown before approval. Enter actual values only after checking the relevant official offer.

If cryptocurrency payment is important to you, ask whether it is supported for that purchase. If the answer is yes, request the applicable asset, network, payment instructions and method of matching the transfer to your account. These are proposed questions; this article does not assert that cryptocurrency payment is offered.

Before approving payment, compare the offer name, amount and period in your worksheet with the order summary. Under our proposed decision rule, pause when those entries differ and request clarification. Keep a copy of the information you relied on, including its location and the date you checked it. Do not substitute an educational example for a quoted subscription price.

Ask about renewal, cancellation and refunds separately

For this worksheet, we propose three independent question groups. The access group asks how long the purchase lasts and what happens at the end of that period. The cancellation group asks what action you must take to stop the subscription. The refund group asks which stated policy applies to the payment you are considering.

Suggested wording includes: “Does renewal require an action from me?”, “Where do I submit a cancellation?”, “What is the resulting access end date?” and “Please link the refund policy applicable to this offer.” Record each answer separately. Our convention is to leave an unanswered refund question open even when cancellation instructions have been supplied.

For an ambiguous answer, write a hypothetical scenario using a named offer and example dates. Ask the provider to explain that scenario and identify the relevant official text. Label the dates as examples. Do not turn your own interpretation into a stated refund entitlement or a promised processing deadline.

Check the alert configuration you actually need

The Pro Alerts documentation distinguishes an Alert based on one condition from a Pro Alert based on several conditions. Pro Alerts documentation.

It also describes a time window for meeting conditions and a sleep period after a Pro Alert triggers. Pro Alert settings.

Our proposed acceptance test is to write the configuration you want in plain language, then ask whether that configuration is available under the offer being considered. Include the condition, chosen data field, intended observation interval and notification destination as questions to confirm. Do not treat the documentation description as a completed account test.

For an analytical experiment, we recommend adding the data definition, source, expected update delay, observation horizon and a rule for abandoning the interpretation. Leave unknown items explicitly unresolved. Treat the experiment as product evaluation; do not use an expected trading return as the acceptance criterion for a subscription purchase.

Specify an integration as a task

Our integration worksheet begins with a sentence describing the intended connection. For example: “I want a notification delivered to a chosen destination.” A separate example is: “I want to evaluate a defined automation.” These are requirement examples, without asserting that either connection is available.

Then ask for the official setup instructions for the exact service and action. Request the account prerequisites, configuration scope, limitations and disconnection procedure. For automation, add questions about stopping the process and reviewing performed actions. Record the answer against the specific integration rather than against the product as a whole.

Our proposed test record has four entries: expected result, observed result, test time and unresolved difference. Choose a bounded test scenario before starting. At the review stage, compare the observation with that written scenario. If they differ, keep the test open and request an explanation instead of declaring the integration ready on the strength of a visible setup option.

Prepare a support request someone can answer

The Help Hub presents MaxData Info Bot as an assistant for questions about MaxData. MaxData Help Hub.

Our recommended support request starts with the exact offer under consideration, the task you want to perform and the official page you have reviewed. Follow with numbered questions whose answers are still missing. For a purchase query, include an order reference if you have received one. For a configuration query, describe the screen and the action you attempted.

A suggested message is: “I am considering offer X for saved charts and notification testing. Please point me to its feature limits, renewal terms, cancellation instructions and applicable refund policy. I also need the official instructions for my proposed integration.” Replace X with the verified offer name and describe the integration precisely. Keep the response alongside your worksheet.

Make a decision with explicit open items

We propose three closing decisions: proceed, request more information or decline the purchase. Add a short reason linked to your requirements and budget. For example: “Request more information because the access limit for my required task remains unconfirmed.” This is a suggested decision format, not an assessment of any particular offer.

Keep the completed worksheet attached to the offer you reviewed. If you later consider a different period or feature bundle, create a new entry and revisit the relevant questions. Under our convention, a change in price, period or scope calls for a fresh written decision rather than an automatic carryover from the previous record.

Commercial section — our recommendation: treat account registration, product evaluation and approval of a paid purchase as separate decisions in the proposed workflow.