Booking transactions
Booking transactions is a view in Control Center that lists higher-level financial entries for a provider.
These entries belong to items such as bookings, tips, service credits, personal discounts, and tickets.
This page focuses on the business transaction that belongs to a purchasable item. If you want to see the actual payment and refund attempts that settle those transactions, use Payment transactions.
View booking transactions
Permissions:
read_purchases
From the provider view in Control Center, select ⚙️ > Booking transactions in the dropdown menu or in the left sidebar.
The page shows one row per transaction.
| Field | Description | Example |
|---|---|---|
| ID | The unique identifier of the transaction. | pur_... |
| Purchasable | The type of item the transaction belongs to. This can be a booking, tip, service credit, personal discount, or ticket. | Booking |
| Type | Whether the transaction is a debit or a credit. Debits charge money. Credits reduce or return money. | Debit |
| State | The current transaction state. See Transaction states. | Succeeded |
| Amount gross | The full amount including VAT. | 12.00 EUR |
| Amount net | The amount before VAT. | 10.08 EUR |
| VAT rate | The VAT rate applied to the transaction. | 19% |
| Payment method type | The payment method linked to the transaction. | LogPay, Stripe, Service credits, External payment |
| Name | The linked user. | Jane Example |
| Created at | The date and time when the transaction was created. | 2026-04-01 14:35 |
A ride fare is usually shown as a debit transaction. If the fare is refunded later, the refund appears as a separate credit transaction linked to the original debit.
Transaction states
The State field shows where the transaction is in its lifecycle.
| State | Meaning |
|---|---|
| Not initiated | The transaction exists, but settlement has not started yet. |
| Pending | The transaction is currently being settled. |
| Reserved | An amount has been reserved, but settlement is not finished yet. |
| Succeeded | The transaction was settled successfully. |
| Failed | Settlement failed and the transaction is still unsettled. |
| Canceled | The transaction was canceled. |
| Forfeited | The debit was written off and is no longer collected. |
Filter and search booking transactions
You can narrow the list in several ways.
Filter by transaction data
You can filter booking transactions by:
- State
- Amount gross greater than or equal to
- Amount gross less than or equal to
- Created at greater than or equal to
- Created at less than or equal to
Search by identifiers or user
You can search booking transactions by:
- ID
- User ID
- User
Limit the list by type or month
The page also lets you:
- Switch between Debit and Credit
- Move between calendar months
Open the detailed view of a booking transaction
Permissions:
read_purchases
To open the detailed view of a booking transaction, select ⚙️ > Show in the dropdown menu. Alternatively, select its type in the table.
The detailed view shows the following fields.
| Field | Description |
|---|---|
| ID | The transaction identifier. |
| User | The linked user. |
| Created at | When the transaction was created. |
| Type | Whether the transaction is a debit or a credit. |
| Purchasable | The linked item, such as a booking, service credit, or ticket. |
| Purchasable ID | The identifier of the linked item. |
| State | The current transaction state. |
| Amount gross | The total amount including VAT. |
| Amount net | The amount before VAT. |
| VAT rate | The VAT rate applied to the transaction. |
| Payment method | The payment method linked to the transaction. |
| Settled | Whether the transaction amount has already been fully balanced by successful charges or refunds. |
| Overpaid | Whether more money was processed than expected for this transaction. |
| Manually charged | Whether the transaction was settled manually instead of through a PSP flow. |
Depending on the transaction type, additional fields can appear.
Additional fields for debit transactions
| Field | Description |
|---|---|
| Refundable | Whether the transaction can currently be refunded. |
| Refunded | Whether the transaction has already been refunded fully or partially. |
Additional fields for credit transactions
| Field | Description |
|---|---|
| Debit purchase | The original debit transaction that this credit belongs to. |
| Creator | The user or administrator who created the credit transaction. |
| Reason | The stored reason for the credit transaction. |
Refund a booking transaction
Permissions:
manage_purchases
You can refund a debit booking transaction from its detailed view. Any refundable item can be refunded this way—a booking (ride fare), tip, service credit, personal discount, or ticket.
A transaction is refunded through the same payment method that was used for the original payment. Control Center can do this only for payments settled through a payment service provider—Stripe or LogPay. Payments taken in the vehicle, such as cash, aren’t handled by a payment service provider, so there’s no original payment to reverse and Control Center can’t refund them.
A transaction can be refunded only while its Refundable field is true. This is the case when it was settled through a payment service provider and hasn’t been fully refunded yet. When the transaction isn’t refundable, the Refund payment button is disabled.
There’s no way to delete a transaction in Control Center. A transaction that was recorded in error is corrected only through a refund.
To refund a transaction:
- Open the detailed view of the transaction and select Refund payment.
- Enter a reason for the refund.
- Enter the amount to refund. It defaults to the full refundable amount and can be lowered for a partial refund, but it can’t exceed that amount.
- When the item can be deactivated, decide whether to keep Deactivate purchasable after refund selected—see Deactivate the item after a refund.
- Submit the refund.
Once processed, the refund appears as a separate credit transaction linked to the original debit, and the debit’s Refunded field is updated.
Deactivate the item after a refund
When the item is a service credit, personal discount, or ticket, the refund form shows a Deactivate purchasable after refund option, selected by default. When it stays selected, the item is marked as unusable after the refund and the user can no longer use it. Because this invalidates the whole item, refund the full outstanding balance in this case—a partial refund combined with continued use of the remainder isn’t possible.
For a ticket, deactivation only marks it unusable in ioki Platform. The ticket must still be refunded manually with the ticket provider.
Related sections in the detailed view
The detailed view can also show related records below the transaction details.
Payment transactions
If payment or refund charges exist for the transaction, the page shows them in a separate table. Use this section when you want to see which payment transactions were used to settle the transaction.
Credit transactions
If the debit transaction has related credits, the page shows them in a separate table. This is useful for refunds and forfeited debits.
Invoices
If invoices exist for the transaction, they are listed in the detailed view.
Line items
If line items exist, the page shows a breakdown with the following fields:
- ID
- Title
- Description
- Quantity
- Amount gross
- Amount net
- Total amount gross
- VAT rate
- Created at