> For the complete documentation index, see [llms.txt](https://docs.tiun.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tiun.io/reference/customer-account/overview.md).

# Overview

Every customer who signs in or buys through tiun gets a **tiun account**. They manage it in the **account portal**, a page run by tiun where they see their payments, manage their subscriptions and saved payment methods, and sign out of apps and devices. You don't build or host any of it.

The account is shared across every business that uses tiun. A customer who buys from you and from another tiun business sees both in the same portal, under the same email.

***

## Where it lives

The portal follows the same split as the rest of tiun: live and sandbox are separate, and each has its own portal.

| Environment | Account portal                                             |
| ----------- | ---------------------------------------------------------- |
| Live        | [account.tiun.io](https://account.tiun.io)                 |
| Sandbox     | [account-sandbox.tiun.io](https://account-sandbox.tiun.io) |

The sandbox portal only shows test customers, test purchases, and test subscriptions, and it shows a **Test mode (Sandbox)** banner at the top. Use it while you test, and send real customers to the live portal. See [Sandbox](https://docs.tiun.io/reference/generic/sandbox.md).

***

## Signing in

Customers sign in the same way they do in your app: with their **email** and a **6-digit code** sent to their phone by SMS, with email as a fallback. It's the same identity they got at checkout, so they don't create anything new. See [Authentication / How it works](https://docs.tiun.io/reference/authentication/how-it-works.md).

***

## What customers can do

The portal home links to five sections:

| Section             | What it holds                                                                                                                                                                                                          |
| ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Transactions**    | Every payment made through tiun, at any business, with its status and price breakdown. See [Subscriptions and transactions](https://docs.tiun.io/reference/customer-account/subscriptions-and-transactions.md).        |
| **Subscriptions**   | Active and inactive subscriptions, with billing details, billing history, and cancellation. See [Subscriptions and transactions](https://docs.tiun.io/reference/customer-account/subscriptions-and-transactions.md).   |
| **Payment methods** | Saved payment methods and which one is the default. See [Payment methods](https://docs.tiun.io/reference/customer-account/payment-methods.md).                                                                         |
| **Connected apps**  | Every app and website the customer signed into with tiun, and the devices they're signed in on there. See [Devices and connected apps](https://docs.tiun.io/reference/customer-account/devices-and-connected-apps.md). |
| **Settings**        | Name, email, phone number, language (English, German, or French), linked devices, and a link to tiun support.                                                                                                          |

***

## What you control

Transactions and subscriptions have a **Contact business** button. It shows your **website** and your **support email**, so customers with questions about what they bought reach you directly.

Set your support email in the [my.tiun.business dashboard](https://my.tiun.business/) under **Settings → General information**. If it's empty, customers only see your website.

***

## Help for your customers

tiun runs an end-customer help center at [support.tiun.io](https://support.tiun.io/faq). It explains each portal task step by step, like cancelling a subscription, removing a payment method, or requesting a refund. Link to it from your own help pages instead of writing those steps yourself.

***

## Where to go next

* [Subscriptions and transactions](https://docs.tiun.io/reference/customer-account/subscriptions-and-transactions.md) — what a cancellation does to your customer's access.
* [Devices and connected apps](https://docs.tiun.io/reference/customer-account/devices-and-connected-apps.md) — what happens in your app when a customer signs out from the portal.
* To point customers to the portal from your app, see [letting customers manage their account](https://docs.tiun.io/guides/customer-account/let-customers-manage-their-account.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.tiun.io/reference/customer-account/overview.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
