> For the complete documentation index, see [llms.txt](https://bify.gitbook.io/rwa-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bify.gitbook.io/rwa-docs/bify-commerce/webhooks.md).

# Commerce Webhooks

BIFY sends signed lifecycle events to the partner backend.

## Events

```
purchase.settled
purchase.fulfilled
certificate.minted
reward.eligible
reward.claimed
access.pass.created
access.pass.status_changed
access.grant_changed
voting.poll.created
voting.poll.status_changed
```

Each event includes an event ID, event type, creation time, BIFY order or purchase ID, external order ID, and the relevant state transition. Customer email, phone, shipping data, API keys, and decrypted session data are not event fields.

The partner verifies the raw request body and signature before parsing or mutating its order state. Duplicate event IDs are idempotent.


---

# 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://bify.gitbook.io/rwa-docs/bify-commerce/webhooks.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.
