> ## Documentation Index
> Fetch the complete documentation index at: https://docs-v2.reeple.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Track an event

> Report checkout UI events back to Reeple for analytics and fraud signals

Records a customer-behaviour event against an order. This feeds Reeple's checkout analytics and
fraud signals — it never changes the order's state.

Calling it is optional, but events improve fraud scoring on the orders you send them for.

## Endpoint

```
POST https://api-v4.reeple.ai/charge/order/event/track
```

Authenticate with your **public key**. See [Authentication](/api-reference/authentication).

## Request body

<Warning>
  The envelope key on this endpoint is **capitalised** — `Data`, not `data`. It is the only
  endpoint that differs.
</Warning>

| Field  | Type   | Description                                                             |
| ------ | ------ | ----------------------------------------------------------------------- |
| `Data` | String | **Required.** The RSA-[encrypted](/encryption) payload described below. |

```json theme={null}
{ "Data": "YOUR_ENCRYPTED_PAYLOAD" }
```

## Payload (before encryption)

| Field            | Type   | Description                                              |
| ---------------- | ------ | -------------------------------------------------------- |
| `eventname`      | String | **Required.** The event identifier, e.g. `CARD-ENTERED`. |
| `orderreference` | String | **Required.** The order the event belongs to.            |
| `meta`           | String | Optional. Free-form context. Send `""` if unused.        |

```json theme={null}
{
  "eventname": "CARD-ENTERED",
  "orderreference": "order-2026-0001",
  "meta": ""
}
```

<Note>
  `eventname` is a free-form string. `CARD-ENTERED` is the documented example; agree the
  vocabulary you intend to send with Reeple so the events are useful on their side.
</Note>

## Request example

```bash theme={null}
curl -X POST https://api-v4.reeple.ai/charge/order/event/track \
  -H "Content-Type: application/json" \
  -H "api-key: YOUR_PUBLIC_KEY" \
  -d '{ "Data": "YOUR_ENCRYPTED_PAYLOAD" }'
```

## Response

```json theme={null}
{
  "data": null,
  "status": "success",
  "statusCode": "00",
  "message": "Event logged successfully"
}
```

<Tip>
  Fire event tracking in the background and ignore its result. A failed event should never block
  or fail a payment — it is a telemetry call, not part of the payment path.
</Tip>