Two official 1xBet Indonesia pages report different maximum amounts for a 100% sports first-deposit bonus: one states up to IDR1,500,000, while the homepage states up to IDR1,950,000. Both pages also show a minimum deposit of IDR10,000. For a 1xBet promo code Indonesia check, 1X200ERA belongs beside the reported 100% sports bonus only as an unverified reference; the pages reviewed do not establish that this code activates either amount. This guide shows how to compare the two page records with an account-specific offer without choosing a figure by guesswork.

Treat each page as its own source record. The first-deposit rules page and the homepage have different locations, layouts, and levels of detail. Save the page title, the visible offer label, the amount, the currency, and the date you viewed it. If your record only says “the website showed a bonus,” another reader cannot tell which page or statement you mean.

In the Indonesia comparison table, give 1X200ERA a field labeled “code under review” beside the conditional 100% sports first-deposit offer. That label identifies the subject of the question; it does not connect the code to either cap. Keep IDR1,500,000 and IDR1,950,000 in separate source rows until the account terms identify a matching offer.

Capture the full page context when practical. A cropped figure may omit the words “sports,” “first deposit,” or the button that identifies the offer. Keep an uncropped private record and, if you need to share evidence, make a separate copy that hides account identifiers and payment details. A screenshot is evidence of what appeared in that view, not proof that the offer was attached to an account.

Use a neutral label for each source, such as “first-deposit rules page, viewed on [date]” and “homepage offer panel, viewed on [date].” Do not rename one “official amount” and the other “old amount” unless a dated source says that. A descriptive label keeps the comparison useful while leaving the unresolved relationship visible.

When recording the display, note whether the amount appeared in the heading, a table, or body copy. These positions help another reader reproduce the observation and see whether nearby text limits it to sports or to a first deposit. Keep the surrounding sentence as well as the number. A value detached from its label can be accurate in isolation and still mislead when reused in another context.

A percentage and a maximum amount answer different questions. “100%” describes the stated match rate, while “up to IDR1,500,000” or “up to IDR1,950,000” describes a cap shown on a particular page. Neither figure alone says how a particular account will be treated. The selected offer, deposit amount, and terms need to be read together.

The two pages show the same rate and minimum but different caps. Those shared fields do not identify a single offer version, so preserve the page names and the separate maximum amounts until an account record or linked terms establish the relationship.

If a table contains a maximum but no rate, write down the missing rate. If a heading contains a rate but no cap, note that separately. Do not fill a blank field from the other page unless the wording connects the two records. This simple separation prevents a reader from making a combined offer that neither page actually states.

When comparing an account card with the public text, match the product label first. A sports welcome offer and a general welcome label may refer to different packages or versions. The same percentage can appear in multiple contexts, so the number is not a reliable identifier by itself.

A cap is not necessarily the amount that will appear in a balance. It is a ceiling described by a source, while the account display may show a calculation based on a particular deposit. Record the cap and any calculated amount in separate fields. If the page does not explain how the cap is applied, note that missing explanation instead of deriving an account result from the headline.

Record the date and local time when you viewed each page. Also copy any publication or update date printed near the offer. These are different dates: a retrieval date says when you saw the page; a page-update date says when the publisher labels the content as updated. Neither automatically identifies when an account offer was selected or credited.

Tie each capture to its retrieval date and source name. One page may have been viewed later and still contain older wording; the order of visits does not prove a content revision or establish which amount was attached to an account.

If one page has no visible date, write “no date shown in the capture.” Do not infer an update from the current year in a page title or a date embedded in a URL. A timestamp in the browser history can help show when you visited; it cannot establish when the offer terms were written.

Keep time zones explicit if the page or account record displays one. If a capture has device time but no website time, label the device time as such. This makes a later comparison more precise, particularly when account events are shown in a different time zone.

A page can change without showing a clear revision history. If you revisit it and see new wording, preserve the earlier capture and save the later one with its own retrieval time. This sequence shows what you observed at each visit. It does not reveal who changed the page, why it changed, or whether an account offer changed at the same time.

Copy the complete offer label from each source, including whether it says first deposit, sports, welcome, or another descriptive phrase. Shortened labels can hide an important distinction. If the source has no distinct label, describe its location in your own words and mark the description as yours rather than an official campaign name.

When you compare an Indonesia account card, copy its offer label before examining the code field. If 1X200ERA is visible, record it beside the account’s conditional 100% sports-bonus description, then note whether the card itself names either public-page cap. A wording mismatch is useful evidence; do not edit the card label to make it match a page.

A label can identify a product without establishing its full conditions. “Sports” helps distinguish the offer from another category, but it does not specify a cap, a time limit, or a code relationship. Read the connected terms and record whether the account card links to the same document or campaign identifier.

When a support response uses a shortened campaign name, save the exact response and its date. Ask which complete offer name it refers to if more than one page uses similar wording. This keeps later comparisons tied to identifiable records rather than memories of a conversation.

Small wording differences deserve attention. “First deposit,” “welcome,” and “sports” may overlap in everyday conversation, but the source may use them to distinguish a specific offer from a broader category. Copy each phrase literally before summarizing it. If you later shorten a label for a table, keep the original wording in a note so that the summary can be checked.

An account offer card can show details not present on a public homepage. It may display an offer name, selected product, deposit condition, percentage, maximum, and a link to terms. Record only fields actually visible. If the card omits the cap or does not open the terms, note that gap rather than completing it from a general page.

For Indonesia, the account-specific terms—not a nearby code string—must show whether 1X200ERA belongs to the reported conditional 100% sports offer and which cap applies. A search result or article can document a public claim, but it cannot establish that an account received the offer.

If the account terms contain a campaign name or version, copy it exactly. A terms document that broadly describes welcome bonuses may not identify the individual offer selected in the account. Match the card, the terms, and the account event through a shared identifier or explicit wording where supported by the source.

If no account-specific record is available, the accurate result is limited: the public pages show different caps, and the account-level match has not been established. That is still a useful answer. It tells the reader what the published pages say and what evidence is needed to settle the personal question.

An account record may be private and may not be suitable to publish in full. The comparison guide only needs the offer name, relevant amount, status, timestamp, and a reference to the terms. Remove names, account IDs, payment details, and login data from any shared example. Keeping the evidence limited protects unrelated account information while preserving the facts needed to ask a clear question.

Both reviewed pages state a minimum deposit of IDR10,000 alongside the sports first-deposit offer. The matching minimum is a shared detail, but it does not prove that both pages describe the same campaign version. Two offers can share a minimum while having different caps or other conditions.

List the IDR10,000 minimum as a separate observation beside the rate and cap. Do not treat the threshold as confirmation that an offer was selected or added. A deposit minimum is one term; selection and account status are separate facts.

If your deposit is below or above the amount shown in an account card, preserve the exact displayed threshold and the currency. Do not convert the minimum into an expected bonus amount without checking the applicable calculation and cap. The calculation may depend on the offer card’s own terms, not just on the page heading.

An evidence table can use separate columns for source, offer label, minimum, percentage, maximum, and account record. A blank cell means the source did not establish that field. This is clearer than putting all numbers in one sentence and asking the reader to infer which one belongs to which page.

The minimum is a threshold stated by the page; it does not define the maximum cap. A reader should not multiply the minimum by the stated percentage and call that the expected credit. The source may describe a percentage match alongside an upper limit, and the account terms may contain additional conditions. Record the threshold, rate, and cap separately before comparing them with an account record.

The first-deposit rules page describes a 5x wagering requirement using accumulator bets with at least three selections, including minimum odds of 1.40 for at least three picks. Treat these as page-reported details that need to match the account’s selected offer. A headline and an account terms panel may not have identical scope.

If an Indonesia terms comparison includes 1X200ERA, place it in the source-reference column beside the conditional 100% sports-offer label. Use the account-linked rules to interpret the reported 5x requirement, three selections, and odds threshold; a code mention does not change those written conditions.

Copy the requirement as a set of separate fields: multiplier, bet type, number of selections, odds threshold, qualifying period, and any exclusions visible in the terms. If one page describes a three-event accumulator and another only says 5x, keep both descriptions distinct until the offer identifier connects them.

If you need to compare a bet history with a requirement, first identify the account offer and its terms version. A list of bets without the linked offer name cannot show which bets were counted. Keep any example clearly hypothetical and do not present it as a prediction about a reader’s account.

A wagering multiplier is only one part of the rule set. The event count, odds threshold, bet type, time window, and treatment of void selections may also affect whether activity is counted. If a source leaves one of these fields unstated, mark it as absent from that source. Avoid carrying an omitted condition over from another campaign simply because its format looks similar.

The rules page refers to a 30-day claim period after registration and also describes a 30-day wagering period. Those statements may have different start events. Record the exact wording and identify the event named by each period. Do not combine them into one deadline just because both contain the same number of days.

Record registration time, offer-selection time, activation time, and any displayed deadline in separate fields. The matching account terms must establish which event starts each clock; the same 30-day figure on two statements does not prove a shared start event.

A screenshot taken on day ten does not reveal when a period began unless the account record shows the start event. A page may describe a clock from registration while the account interface may show an activation timestamp. Keep the source for every time value visible in the note.

When a date is shown without a time zone, preserve it as displayed and flag the missing zone. Do not calculate a final deadline from an unknown start time. A precise statement such as “the page mentions 30 days, but the account start time is not visible in this capture” is more useful than an invented date.

A timeline can use one row per event and one column per source. Registration, selection, activation, and the first qualifying wager should not be collapsed into one timestamp. If the interface provides only a date, preserve it at that precision. Do not add an invented hour to make it fit a calculation. A careful timeline can identify exactly which start event remains unknown.

A code box can show text without showing that an offer was selected. A form may accept a string, reject it, or display no result until another step. Record the screen, the visible response, and the time. Do not describe a code as activated solely because it was typed into a field.

In an Indonesia form audit, describe the code-entry event and offer-selection event separately. If the form shows 1X200ERA beside a conditional 100% sports offer, preserve the screen response exactly; if it shows no connection, leave the link unresolved rather than treating typed text as activation.

An offer selected during registration and a bonus entry shown later in account history are different events. The first can show user selection; the second can show a system record. A reader comparing them should look for a shared offer name, event identifier, or terms reference rather than relying on similar phrasing.

If the interface shows an optional code field, copy the word “optional” as displayed and note the section where it appears. That word describes the interface field, not necessarily every condition for the offer. The account’s selected offer and terms still need to be checked.

If a confirmation appears, copy the full sentence and record the screen where it appeared. “Accepted” may refer to the form accepting text, while “activated” may refer to a selected promotion or a resulting account entry. Those labels are not interchangeable unless the interface defines them that way. A note that preserves the original status wording is easier to compare with account history later.

When two pages disagree, save both captures and do not overwrite one with the other. Include the whole section heading and the amount in view. A cropped number alone may be impossible to interpret later. If a page is dynamic and cannot be saved as a file, write down the page title and the visible text immediately.

On an Indonesia screenshot index, list 1X200ERA as the code being checked beside the conditional 100% sports-bonus page capture. Add the source name and retrieval date so the note distinguishes the homepage figure from the first-deposit rules-page figure.

Use descriptive filenames that indicate source and viewing date, such as “homepage-cap-viewed-2026-11-13” and “first-deposit-rules-viewed-2026-11-13.” Avoid labels like “correct” or “current” unless the page itself supplies that status. A neutral filename preserves the question rather than answering it prematurely.

If you share a screenshot with support, remove passwords, full account numbers, payment credentials, and authentication values. Keep the unedited copy private. A limited image can show the offer wording needed for the question without exposing unrelated account data.

Store each capture in a private, dated folder and keep an index with the source name, observation time, and a one-line description. If the page is captured on a phone, record that it was a mobile view; desktop and mobile layouts may show different amounts of context. Do not edit the original capture. If you need to redact private information, make a separate copy and label it as edited.

Consider a hypothetical reader who sees the rules page on one day and the homepage on another. The first capture displays a 100% sports first-deposit bonus up to IDR1,500,000; the second displays a 100% sports bonus up to IDR1,950,000. The shared percentage and minimum do not establish that the same offer version appears in both captures.

In this hypothetical Indonesia worksheet, 1X200ERA appears in a “reader’s question” field beside the reported conditional 100% sports offer. Separate rows show the two page caps. The example illustrates how to keep evidence organized; it does not assign either amount to the imagined account.

The next question is not “which amount is larger?” It is “which named offer was attached to this account, and which terms version belongs to the account event?” A matching campaign identifier or account card may answer that. If neither is present, the result remains unresolved and should be reported as such.

This example demonstrates a method, not an expected outcome. It does not predict the amount any person will receive. The account terms and actual account history are needed before connecting the public page figures to a personal offer.

A useful outcome may be “not enough information to choose between the two caps.” That is not a failure of the comparison. It accurately reflects that two public statements exist while the account link is missing. The next evidence request can then focus on the exact offer identifier or terms version rather than asking someone to guess which public number looks more plausible.

A concise support question can identify the two public records without claiming that either one governs the account. Include the page labels, the two caps, the retrieval dates, and the account offer name if it is visible. Ask which terms version corresponds to that offer and whether a code event is recorded.

A support request from Indonesia can ask whether the account event links 1X200ERA to the named conditional 100% sports offer, and which terms version supplies its cap. Include the event label and date; frame the code as the subject of the question, not as an already granted benefit.

If you receive an answer, keep the full wording, date, and channel. A short reply such as “the current offer is 100%” may not clarify whether the cap is IDR1,500,000 or IDR1,950,000. Ask for the offer name and terms reference if those fields are missing.

When the response points to a page, compare the page’s offer label and date with your saved records. If it does not explain the historical account event, record that limitation. The follow-up can then target the remaining gap rather than repeating the whole story.

Before sending a question, arrange the material in chronological order and remove details that do not help identify the offer. Include one sentence stating the discrepancy, followed by the two source labels and dates. Then ask for the account-linked offer name and its terms reference. This structure makes the request easier to answer and reduces the risk that a general reply will be mistaken for confirmation of a personal account record.

Keep a copy of any reply with its case reference and the date it was received. If the reply points to a general promotion page, compare that source with the account card rather than assuming the general page settles the account question. If the case response identifies a campaign version, add that version to the record and preserve the original public-page captures so the reasoning remains traceable.

A final comparison can classify each field as visible on a public page, visible in an account record, or not established. The rules-page cap and homepage cap belong in separate source rows. The account offer name, code event, and terms version belong in account rows. This layout avoids making a single conclusion carry more certainty than the evidence supports.

The Indonesia comparison concludes that the two pages show different caps for a reported 100% sports first-deposit offer. It does not establish whether 1X200ERA triggers either version; the account terms and event record must make that connection before a reader can describe an account-specific benefit.

Before sharing the comparison, check the arithmetic, currency, source labels, and dates. Confirm that IDR1,500,000 is attributed to the rules page and IDR1,950,000 to the homepage, rather than reversing them in a summary. A simple attribution error can make a careful comparison misleading.

Use a short result statement with three parts: what each page displays, what the account record shows, and what remains unconfirmed. If the account record has not been reviewed, say so. This makes the guide useful to a reader who needs to answer a concrete question without treating the public page as a personal account statement.

A reviewer can use a simple status vocabulary: “shown on page,” “shown in account,” “not shown,” and “relationship unconfirmed.” Apply the same labels consistently to both caps, the percentage, the code entry, and the offer name. This prevents a confirmed page observation from being mistaken for a confirmed account benefit. Keep the evidence reference next to every status so that another person can retrace the conclusion.

If a field changes on a later visit, create a new dated entry rather than overwriting the earlier one. The comparison then shows whether the source text changed and when you observed that change. It still cannot establish the terms attached to a past account event unless the account record links that event to a version.

The same comparison can be revisited later without erasing the first result. Add a new observation row with its own time and source label, then compare it with the saved account record. This method preserves the history of what the pages displayed and makes clear whether the unresolved point changed, stayed the same, or still needs a terms reference.

If a later page shows a single figure, preserve the earlier comparison in the notes rather than deleting it. The newer display may answer the present question, but it does not explain the earlier difference unless the page identifies a revision or the account terms connect the new wording to the event. Keeping both observations also helps support distinguish a page-content question from a question about an individual offer.

The first-deposit rules page reports IDR1,500,000, while the homepage reports IDR1,950,000. Keep the captures separate and compare their labels and dates with the terms attached to the account offer.

No. The percentage can be shared while the cap, version, or campaign differs. Compare the offer name and linked terms before treating the pages as one record.

It establishes that both reviewed pages show that minimum. It does not prove that a code was accepted, that an offer was selected, or that an account received a bonus.

Make one row for each page, include the source label and viewing date, and copy the amount exactly as displayed. Leave the account match unresolved unless the account terms connect it to a specific offer.

For an Indonesia account question, ask support whether the event record or attached terms explicitly connect 1X200ERA to the conditional 100% sports bonus. The FAQ answer should report that link only if the account evidence names it; proximity on a public page is insufficient.

Related Indonesia account guides: