> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/product/customer-self-service/account-management/customer-account-management.md).

# Customer Account Management

The **My Account** area of the customer portal is where signed-in customers keep their own account details current — without raising a support case or waiting on a CSR. Letting customers self-serve their contact, billing, and payment details reduces failed payments and stale records, and keeps your billing system as the single source of truth.

## What customers can view and do

* **Contact information** — the name, email, phone, and address on the account (billing and sold-to contacts), shown from the customer's live billing record.
* **Billing details** — billing address, account/billing name, and a summary of the current plan, next billing date, and cost breakdown.
* **Invoices** — the account's invoice history, with each invoice **downloadable as a PDF** straight from the list.
* **Payment methods** — view saved methods (card type, last four, expiry, default badge), **add** a new method, **remove** one, and **set a default**. Adding a card is completed on a secure hosted payment page, so raw card data never touches PeakCommerce.

## Managing payment methods

Each saved payment method that is **not** the current default carries an actions menu with two options:

* **Make default** — promotes that method to the account's default; future charges use it.
* **Remove** — deletes the saved method. Removal always asks for confirmation first, since it can't be undone.

The **default** method deliberately has no actions: it can't be removed or demoted directly. To retire it, make another saved method the default first — the old default then gets its own actions menu, including Remove. This guarantees the account always has a usable default on file.

Both actions honor the customer's [portal-action permissions](/product/using-peakcommerce/profiles-and-permissions/portal-action-permissions.md): a profile without the update permission won't see **Make default**, and one without the delete permission won't see **Remove** — so you can offer a fully read-only payment view where that's appropriate.

## How it works

These views are built from Portal-type pages and their blocks (for example the payment-method manager and billing summary). Changes write through to your billing system rather than being stored only in the portal, so what the customer sees and what billing charges stay in sync.

## Who it's for / permissions

Every signed-in customer reaches **My Account**, but what they can see and change is governed by their [profile](/product/using-peakcommerce/profiles-and-permissions/portal-action-permissions.md) — portal-action permissions can show a section read-only or hide an action entirely. Admins can review a customer's account by impersonating them from the **user menu** (your name, bottom-left) → **Settings → Users** (see the [portal overview](/product/customer-self-service/overview/customer-portal-overview.md)).

## Gotchas

* Payment-method changes depend on a configured hosted payment page; without one, adding a card won't complete.
* Invoice PDFs are generated by the billing system **after** an invoice posts, so the document for a just-issued invoice may not exist yet. If a customer downloads too early they see a clear "Invoice PDF not available" message rather than a broken file — trying again a little later succeeds once the billing system has finished generating it.
* Contact and billing edits reflect the billing record, so they may differ from CRM or marketing contacts elsewhere.

## Related

* [Customer Portal Overview](/product/customer-self-service/overview/customer-portal-overview.md)
* [Customer Subscription Management](/product/customer-self-service/subscription-management/customer-subscription-management.md)
* [Portal Action Permissions](/product/using-peakcommerce/profiles-and-permissions/portal-action-permissions.md)
* [Payments & Payment Methods](/product/using-peakcommerce/payments-and-payment-methods.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.peakcommerce.com/product/customer-self-service/account-management/customer-account-management.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.