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

# Payment Preferences

> Using Omneo to track and personalise based on customer payment behaviour.

Omneo captures payment method data as part of each transaction via the `payments` array. This allows you to understand how customers prefer to pay and personalise experiences accordingly.

## How payment data is captured

Payment methods are passed as a string array in the transaction payload:

```json theme={null}
{
  "payments": ["EFTPOS", "AMEX"]
}
```

The values are free-text strings, define a consistent set of payment method codes for your implementation and use them consistently across all transaction sources.

## Common payment method codes

Standardise on values that make sense for your business:

* `EFTPOS`
* `VISA`
* `MASTERCARD`
* `AMEX`
* `CASH`
* `AFTERPAY`
* `ZIP`
* `GIFT_CARD`
* `OMNEO_REWARD` (if you record reward redemptions as a payment type)

## Using payment data in reactions

Payment method data is available in the transaction event context. You can use it in reaction filters, for example, to trigger a special benefit for customers who pay with a co-branded credit card:

```json theme={null}
{
  "in": ["AMEX", {"var": "payments"}]
}
```

## Reporting and segmentation

Payment method data feeds into aggregations and can be used for segmentation. For example, identifying customers who consistently pay with buy-now-pay-later (BNPL) services may inform your communications and incentive strategy.
