> 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/subscriptions-and-transactions.md).

# Subscriptions and transactions

In the [account portal](https://docs.tiun.io/reference/customer-account/overview.md), customers see what they pay for and what they've paid. This page covers what they can do there, and what each action means for your integration.

***

## Subscriptions

The **Subscriptions** section lists every subscription the customer has taken out through tiun, split into **Active** and **Inactive**. Opening one shows:

* Your business name and logo, and the price per interval.
* The plan, and its status.
* The payment method it's charged to, and the billing date.
* For a subscription in a trial, what it will cost once the trial ends, with the price breakdown.
* **Billing history** — every payment for this subscription.
* **Contact business** — your website and support email. See [What you control](https://docs.tiun.io/reference/customer-account/overview.md#what-you-control).
* **Cancel subscription**, while the subscription is active.

A subscription stays on the payment method it started with. To move it to another method, the customer cancels it and subscribes again.

***

## Cancellation

Customers cancel subscriptions themselves in the portal. You don't need to build a cancel flow in your app.

A cancellation takes effect at the **end of the paid period**. Until then, nothing changes for the customer:

1. Right after the customer cancels, the product ID **stays** in `productAccess`. `checkProductAccess()` and `listProductAccess()` now return an `expiresAt` set to the end of the paid period, so you can show something like "Ends on 12 March".
2. At the end of the paid period, the subscription doesn't renew and isn't charged again. tiun **removes** the product ID from `productAccess`.

If your app already gates on `productAccess`, there's no extra code. If your backend keeps its own copy of who has access, the `product_access.remove` webhook tells it when access ends. See [Product access](https://docs.tiun.io/reference/checkout/product-access.md) and [Webhook events](https://docs.tiun.io/reference/webhooks/events.md).

{% hint style="info" %}
Cancelling doesn't refund the current period. The customer keeps access until it ends.
{% endhint %}

One-time purchases appear under **Transactions** but never under Subscriptions. They can't be cancelled. See [One-time purchases](https://docs.tiun.io/reference/checkout/one-time-purchases.md).

***

## Transactions

The **Transactions** section lists every payment the customer has made through tiun, at any business, grouped by date. Opening one shows:

* The amount, your business name and logo, and the date and time.
* The **status**: Successful, Failed, or Refunded. Failed and refunded amounts are shown struck through.
* The **price breakdown**, including tax. tiun is the Merchant of Record, so tax is shown the way tiun collected it.
* The payment method used.
* **View subscription**, for a subscription payment.
* **Contact business**.

***

## Refunds

Customers can ask you or tiun support for a refund. You decide whether a refund is due, since you know what was delivered, and tiun sends the money back to the customer's original payment method. Once it's processed, the transaction shows as **Refunded**.

If you and the customer can't agree, tiun support looks at it, because tiun is the seller on record. See [Who handles refunds, chargebacks, and fraud?](https://docs.tiun.io/faq.md#who-handles-refunds-chargebacks-and-fraud) in the FAQ.

***

## Where to go next

* [Payment methods](https://docs.tiun.io/reference/customer-account/payment-methods.md) — saved methods, the default, and why one can't always be removed.
* [Subscriptions](https://docs.tiun.io/reference/checkout/subscriptions.md) — the full subscription lifecycle.
* To try a cancellation in sandbox, see [simulating payments](https://docs.tiun.io/guides/testing/simulate-payments.md#cancellation-and-expiration).


---

# 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/subscriptions-and-transactions.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.
