Find next payment in an E.ON Next account

Purpose

Sign in to an E.ON Next customer account and extract the account's next payment information.

When to Use

Use when the caller provides or can authorize use of E.ON Next account credentials and asks for the upcoming payment amount, due date, or equivalent billing status.

Workflow

1. Navigate directly to https://www.eonnext.com/dashboard/sign-in. This starts the authentication flow without visiting the public homepage. If it does not start authentication, use https://www.eonnext.com/dashboard instead. Do not reuse a previously observed /u/login?state=... URL because its state value is transient.
2. If the OneTrust consent banner is present, click button#onetrust-reject-all-handler before continuing.
3. Complete authentication using caller-authorized credentials or an already-authorized session. On the observed sign-in form, enter the username in input#username, the password in input#password, and submit with button[name='action']; if unavailable, use the visible button[type='submit']:not(.ulp-hidden-form-submit-button). If authentication presents another submit or verification step, wait for the page to settle and follow the visible flow. Never record or expose credentials, tokens, or transient login state. Allow interactive challenges or additional verification to be completed by the caller.
4. After authentication, go directly to https://www.eonnext.com/dashboard/accounts when the dashboard does not visibly show payment information. This avoids exploratory navigation.
5. On the authenticated dashboard, accounts page, or billing page, run this evaluator:

(() => {
  const clean = (s) => (s || "").replace(/\\s+/g, " ").trim();
  const visible = (el) => {
    const r = el.getBoundingClientRect();
    const cs = getComputedStyle(el);
    return (
      r.width > 0 &&
      r.height > 0 &&
      cs.visibility !== "hidden" &&
      cs.display !== "none"
    );
  };
  const keyword =
    /next payment|payment due|due date|amount due|upcoming payment|direct debit/i;
  const lines = (document.body.innerText || "")
    .split(/\n+/)
    .map(clean)
    .filter(Boolean);
  const lineMatches = [];
  lines.forEach((line, i) => {
    if (keyword.test(line))
      lineMatches.push(
        ...lines.slice(Math.max(0, i - 1), Math.min(lines.length, i + 3)),
      );
  });
  const regions = Array.from(
    document.querySelectorAll(
      'main, section, article, [role="main"], [data-testid], div',
    ),
  )
    .filter(visible)
    .map((el) => clean(el.innerText))
    .filter((text) => text && keyword.test(text))
    .sort((a, b) => a.length - b.length);
  const candidates = [...new Set([...lineMatches, ...regions.slice(0, 5)])];
  return {
    nextPaymentText: [...new Set(lineMatches)].join(" | "),
    paymentCardText: regions[0] || "",
    candidates,
  };
})();

6. Report the amount and due date from the returned evidence. Preserve surrounding payment text when labels are ambiguous and distinguish a scheduled payment from a current balance.
7. If no payment evidence is found on the dashboard or accounts page, use visible authenticated navigation to open the billing or payments page and rerun the evaluator there.

Site-Specific Gotchas

• The public entry point is on www.eonnext.com, while authentication is hosted on auth.eonnext.com; /dashboard/sign-in is the observed direct sign-in entry route, with /dashboard as a fallback.
• The observed authenticated accounts route is https://www.eonnext.com/dashboard/accounts.
• The OneTrust reject control is button#onetrust-reject-all-handler; dismiss it when present.
• The observed login controls are input#username, input#password, and button[name='action']. A visible non-hidden submit button matching button[type='submit']:not(.ulp-hidden-form-submit-button) is a fallback. Preserve caller credentials and do not expose them.
• Authentication may require an additional submit, interactive challenge, or additional verification; pause for caller intervention rather than attempting to bypass it.
• Payment wording and card markup may vary by account, so preserve matched surrounding text when reporting the result and distinguish a scheduled payment from a current balance.
• The evaluator uses visible text and broad semantic regions because account-card markup may change; prefer the shortest matching region as the likely payment card and retain nearby line matches as supporting evidence.
• Login URLs containing /u/login?state=... contain transient authentication state and must be obtained through the sign-in route rather than constructed or reused.

Expected Output

Return the upcoming payment amount and scheduled due date, with supporting payment text when the page uses ambiguous labels. If unavailable, state that no next-payment value was visible after authentication.