Overview

Update payment information carefully and verify the next billing date after saving changes.

This article is written as a practical reference for update payment information. Follow the steps in order the first time, then use the headings and screenshots as landmarks when you return later. The screenshots reflect the current Open Accessible Cloud layout shown in September 2026, so labels may move slightly as the dashboard evolves.

Before you begin

Confirm that you are signed in to the correct account and, when applicable, that the organization selector in the upper-right corner shows the organization you intend to manage. If you work with multiple websites, verify the domain before changing settings.

For changes that can affect a live site, take note of the current configuration first. A screenshot, copied setting value, or short change note makes rollback much easier. Avoid changing unrelated options at the same time; smaller changes are easier to verify and troubleshoot.

Before making billing changes

Billing changes can affect the whole organization, so confirm which organization and plan you are working with before changing payment or subscription information. If several people manage the account, coordinate ownership so two people do not make overlapping changes at the same time.

Keep receipts, invoice numbers, renewal dates, and the organization name together when contacting support. Those details make it easier to match a billing question to the correct account without sharing passwords, API keys, or other credentials.

Step-by-step workflow

  1. Confirm the organization. Billing is normally associated with an organization rather than a single website.
  2. Gather the billing record. Keep the invoice, receipt, charge date, or current plan name available before making a change.
  3. Make one billing change at a time. Save and wait for the confirmation screen or updated status.
  4. Verify the effective date. Plan changes can take effect immediately or on a later billing date depending on the action.
  5. Keep confirmation records. Save the receipt or confirmation message for future reference.

How to verify the result

Do not stop at the saved confirmation. Reload the relevant page and confirm the visible state matches what you intended. If the change affects authentication, open a fresh browser session. If it affects a website, test the public page as a visitor rather than only the dashboard.

For user-facing changes, check with keyboard input, browser zoom, and a narrow mobile viewport. Watch for overlapping fixed controls, clipped dialogs, focus that disappears off-screen, or settings that reset unexpectedly after navigation.

Troubleshooting

If the dashboard does not match these screenshots, first confirm you are in the correct organization and account. UI labels can also change over time, so look for the same concepts—Websites, API Keys, Secrets, organization settings, or Profile & 2FA—even if the exact placement has moved.

For website problems, check the browser developer console and network panel. Look for blocked scripts, 404 responses, Content Security Policy errors, or requests being stopped by a consent manager or extension. For account problems, try a private window and verify that the email address and organization membership are correct before resetting credentials.

Use descriptive names for websites, keys, tokens, secrets, and team roles. Clear names reduce the chance of editing the wrong resource and make audits easier months later. Avoid putting sensitive values into screenshots, tickets, documentation, or public source repositories.

Review access periodically. Remove old sessions, unused credentials, and team members who no longer need access. For production integrations, document where each credential is used and who is responsible for rotating it.

Next steps

After completing update payment information, return to the documentation home page and use search to find the next related workflow. Search accepts normal phrases, so queries such as “website branding,” “2FA,” “API token,” or “installation” will surface related guides.

If you are troubleshooting, keep the page URL, browser name, approximate time, and a concise set of reproduction steps. Those details make it much easier to distinguish an account configuration issue from a website integration issue.