Track an event - Reeple Checkout

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.

Request body

The envelope key on this endpoint is capitalised — Data, not data. It is the only endpoint that differs.

Field	Type	Description
`Data`	String	Required. The RSA-encrypted payload described below.

{ "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.

{
  "eventname": "CARD-ENTERED",
  "orderreference": "order-2026-0001",
  "meta": ""
}

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.

Request example

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

{
  "data": null,
  "status": "success",
  "statusCode": "00",
  "message": "Event logged successfully"
}

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.