> For the complete documentation index, see [llms.txt](https://docs.thewalletcrew.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thewalletcrew.io/connectors/crm-and-fidelity/comarch/real-time-updates.md).

# Real-time updates

Real-time updates keep the pass aligned with Comarch between two pass opens. This is useful when loyalty changes must appear quickly after a purchase, a tier update, or a coupon assignment.

## How Kafka refresh works

The connector can subscribe to a Comarch CLM Kafka topic.

When a supported event arrives, The Wallet Crew identifies the affected pass and starts a refresh.

This reduces the delay between a change in Comarch and the visible update on the wallet pass.

## Supported event types

The connector refreshes passes for the event families below:

* **Customer**
* **Account point type balance**
* **Counter balance**
* **Coupon**

These events cover common loyalty changes such as profile updates, point balance changes, counter changes, and coupon activity.

## Kafka settings

Use the Kafka section in **Connectors → Comarch** to configure:

* **Bootstrap servers**
* **Username**
* **Password**
* **Topic**

Kafka authentication uses **SCRAM-SHA-512**.

## When Kafka is not configured

The connector still works without Kafka.

In that mode, passes refresh when the pass is opened or when a scheduled refresh runs. The difference is timing, not connector capability.

## Validation steps

A Kafka setup is usually validated in three steps:

1. Publish or wait for a known Comarch loyalty change.
2. Confirm the event reaches the configured topic.
3. Confirm the related pass refreshes shortly after.

## FAQ

<details>

<summary><strong>What should be checked if a Comarch event does not refresh a pass?</strong></summary>

Check the topic name and Kafka credentials first.

Then confirm Comarch publishes one of the supported event types listed on this page.

</details>

<details>

<summary><strong>What if pass refresh is delayed?</strong></summary>

Check Kafka connectivity before checking the pass template.

If Kafka is unavailable, refresh falls back to the next pass open or scheduled refresh.

</details>

<details>

<summary><strong>What if Kafka triggers too many refreshes?</strong></summary>

Review the event stream design and the expected event volume.

Some projects publish many events for the same customer in a short time. In that case, rollout should start in staging and be monitored closely before production activation.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.thewalletcrew.io/connectors/crm-and-fidelity/comarch/real-time-updates.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.