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

# Reference data

> Lookup endpoints that provide valid IDs and values for creating transaction bundles.

Before creating a transaction bundle you need group-specific IDs and configuration values. The endpoints below return this reference data.

## Payment method kinds

**Endpoint:** `GET /v1/transaction_settings`

The `payment_method_kinds` array lists the payment method strings allowed for your group. Pass one of these as `payment_method_kind` on each transaction.

The `default_status_id` field gives you the status to use for new valid transactions.

## Transaction statuses

**Endpoint:** `GET /v1/transaction_statuses`

Each status has a `kind` that controls its meaning:

| Kind         | Usage                                              |
| :----------- | :------------------------------------------------- |
| `valid`      | Normal completed payment                           |
| `unpaid`     | Payment not yet received                           |
| `reimbursed` | Refunded — pair with `reimbursed_amount`           |
| `bank_error` | Payment returned by bank                           |
| `cancel`     | Payment cancelled, the transaction will be ignored |
| `other`      |                                                    |

Use `default_status_id` from `GET /v1/transaction_settings` for new valid transactions.

## Membership prices

**Endpoint:** `GET /v1/membership_prices`

Returns all membership prices configured for your group. Use the `id` as `membership_price_id` when creating memberships.

Each price includes `amount`, `currency`, `name`, `allow_custom_amount`, and optional `rolling_period` / `duration` fields.

## Membership price groups

**Endpoint:** `GET /v1/membership_price_groups`

Returns membership prices grouped by category. Useful when you want to present prices organised by group (e.g. individual, couple, family) in your integration UI.

## Donation prices

**Endpoint:** `GET /v1/donation_prices`

Returns all donation price tiers configured for your group. Use the `id` as `donation_price_id` when creating donations.

## Campaign codes

**Endpoint:** `GET /v1/code_campaigns`

Returns all campaign codes active for your group. Pass a `code` string as `code_campaign` on a transaction to associate it with a campaign.