> For the complete documentation index, see [llms.txt](https://islamu.gitbook.io/islamu-event/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://islamu.gitbook.io/islamu-event/documentation/readme/events-and-ticketing/paid-events-and-payouts.md).

# Paid Events & Payouts

Operate organizer-direct Stripe Connect payments, reconciliation, refunds, and payout boundaries.

ISLAMU Event utilizes **Stripe Connect** as its primary payment adapter. The commercial model is **organizer-direct**: attendees pay the event organizer’s connected Stripe account directly, rather than funds pooling into platform escrow.

***

## 1. Organizer-Direct Commerce Flow

1. **Provider Onboarding**: The organizer completes Stripe-hosted Express/Standard onboarding via organization settings (see [Administration Guide](/islamu-event/documentation/readme/administration-and-branding/admin-guide.md#4-organization--group-governance)).
2. **Checkout Session**: When an attendee registers for a paid ticket (see [Ticketing & Check-In](/islamu-event/documentation/readme/events-and-ticketing/ticketing-and-check-in.md)), a Stripe Checkout session is created in the connected account's context.
3. **Webhook Reconciliation**: Payment truth is established strictly by signed Stripe webhook events (see [Webhooks & Callbacks](/islamu-event/documentation/readme/integrations-and-ai/webhooks.md)). A browser redirect back to the app is never treated as financial settlement.
4. **Admission Issuance**: Cryptographic admission tickets are generated only after signed webhook reconciliation succeeds.

> \[!IMPORTANT] **Operator Legal Identity Prerequisite:**\
> Paid checkout and ticket publication fail closed until the operator's legal identity parameters are configured in `.env` (see [Operator Legal Identity Reference](/islamu-event/documentation/readme/configuration-and-operations/environment-variables.md#9-operator-legal-identity-production-gate)).

***

## 2. Refund Workflows

The platform implements durable, provider-backed refund state machines:

* **Attendee Requests**: Attendees can request refunds through their self-service order portal.
* **Organizer Approval**: Organizers evaluate refund requests and approve or reject them directly in the management console.
* **Partial Refunds**: Support for partial line-item refunds or full order cancellations.
* **Finality Guarantee**: An order is marked "Refunded" only after Stripe delivers signed webhook confirmation of fund return.

***

## 3. Payout Boundaries & Operator Responsibility

Provider-managed schedules determine payout timing directly to the organizer's bank account. ISLAMU Event does not act as an escrow agent, banking institution, or tax accounting authority. Operators must ensure their public terms and refund policies comply with local e-commerce laws.

***

## Related Guides & Next Steps

* [**Ticketing & Check-In**](/islamu-event/documentation/readme/events-and-ticketing/ticketing-and-check-in.md) — Manage ticket capacity, admissions, and gate check-in.
* [**Webhooks & Callbacks**](/islamu-event/documentation/readme/integrations-and-ai/webhooks.md) — Verify signed Stripe webhook intake and replay windows.
* [**Platform Monetization Policy**](/islamu-event/documentation/readme/administration-and-branding/admin-guide.md#platform-monetization) — Configure platform application fees on ticket sales.
* [**Operator Legal Identity Reference**](/islamu-event/documentation/readme/configuration-and-operations/environment-variables.md#9-operator-legal-identity-production-gate) — Mandatory production legal disclosures.


---

# 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://islamu.gitbook.io/islamu-event/documentation/readme/events-and-ticketing/paid-events-and-payouts.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.