> For the complete documentation index, see [llms.txt](https://docs.cloudeka.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cloudeka.ai/guidance-for-enterprise/service-limit/crds/cloudeka-topup.md).

# Cloudeka Topup

A record of **prepaid credit applied to your balance**. Each object is one credit event — an immutable ledger entry showing your balance before and after. Multiple top-ups over time show up as multiple objects, oldest to newest.

```bash
kubectl get topup -n <your-namespace>
kubectl get topup -n <your-namespace> -o yaml
```

| Field                    | Meaning                                                   |
| ------------------------ | --------------------------------------------------------- |
| `spec.topup`             | Amount credited in this event                             |
| `status.previousBalance` | Your balance right before this top-up                     |
| `status.balance`         | Your balance right after (`previousBalance + spec.topup`) |
| `status.createdAt`       | When it was applied                                       |

## How to add credit

Top-ups are applied by the platform team/billing system through your normal Service Portal Cloudeka payment channel — you don't create these objects yourself. Once processed, the credit appears here and your [Cloudeka Tenant](/guidance-for-enterprise/service-limit/crds/cloudeka-tenant.md) balance updates immediately.
