Service Types¶
Service types group sports field types and link them to the payment and invoicing infrastructure.
Navigation¶
Klub konfiguracio → Szolgaltatas tipus — /Club/ServiceType
Configuration¶
| Column | Description |
|---|---|
| Name | Display name |
| Text_Code | Internal identifier |
| PaymentProvider_ID | FK — primary payment provider |
| PaymentProvider2_ID | FK — secondary payment provider (nullable) |
| InvoiceAccount_ID | FK — invoice account for billing |
| IsPublic | Visible to customers |
The SportsFieldType_Enum.ServiceType_ID column references this table, binding each field type to a service type.
Demo Data¶
| ID | Name | Payment Provider | Invoice Account | IsPublic | Secondary Provider |
|---|---|---|---|---|---|
| 1 | Generic | 1 | 1 | Yes | — |
When to Use Multiple Service Types¶
Single vs. multiple
Most clubs need only one service type. Create additional service types when different sports require:
- Different online payment providers (e.g., SimplePay for tennis, Stripe for padel)
- Separate invoice accounts for accounting purposes
- Different public/private visibility rules
Access Control¶
Club manager only — SystemFunction: ClubConfiguration (ID=4).