Payment
Payment in ioki Platform covers charging for rides, service credits, personal discounts, tips, and public transport tickets. Payment is configured at the provider level; how ride payment behaves once enabled is described in Payment for rides.
Payment service provider
A payment service provider (PSP) is a company that facilitates electronic payment transactions between parties. Its software handles digital payments between passengers and the provider.
ioki Platform supports the following options:
Stripe supports card and SEPA direct debit payments; LogPay supports card, SEPA direct debit, and PayPal.
If a PSP is selected, the provider must set up an account directly with either Stripe or LogPay, because both are external services. Provider-specific PSP configuration is then managed on dedicated provider pages in Control Center: Manage Stripe account and LogPay credentials.
Payment methods
A provider defines which payment methods are available for each purchasable object (rides, service credits, personal discounts), and which are reserved for operator-managed workflows in Control Center. The available method types are:
- Digital payment methods provided by PSP. Available only if Stripe or LogPay is selected as the PSP.
- Cash payment. For rides only.
- Card payment in the vehicle
- Service credits
- 3rd party payment handling. Enables external payment.
- Manual payment handling. See below.
How each method is charged (including cash, service credits, and external payment) is described in Payment for rides.
Which methods apply to what
Not every method is available for every purchasable object:
| Purchasable object | Available methods |
|---|---|
| Ride | Any configured method—a PSP method, cash, card in the vehicle, service credits, external, or manual. |
| Personal discount | A digital method: a PSP method, service credits, external, or manual (not the in-vehicle methods). |
| Service credits | A PSP method. In operator-managed workflows, cash or card in the vehicle can also be recorded. |
| Tip | A PSP method (card, SEPA direct debit, or PayPal). |
| Public transport ticket | A PSP method. |
| Payment retry | A PSP method. |
Purchases and charges
When a user owes money, ioki Platform records it as a purchase—a booking transaction tied to the purchasable object (a ride, tip, service credit, personal discount, or ticket). The actual money movement is a charge—a payment transaction processed through the PSP. A single charge can settle several purchases at once, and a refund is a charge that reverses an earlier payment charge.
A purchase starts as pending or reserved and becomes succeeded once it is settled, or failed, forfeited, or cancelled. When a ride payment fails, it can be retried or handled manually.
Manual payment handling
Manual payment handling lets an administrator record a payment that was settled outside ioki Platform instead of charging it through the configured PSP. This creates a platform-managed manual charge in Control Center.
Users cannot select this payment method in passenger-facing apps. It is only available in operator-managed workflows in Control Center.
Manual payment handling is used in the following cases:
- For rides, when an administrator marks a failed payment as Payment has been made. The ride is then treated as paid, and the payment state changes to payment manually retrieved.
- For service credits, when an administrator sells service credits directly and records the amount as already collected outside ioki Platform.
- For personal discounts, when an administrator sells the discount directly and records the amount as already collected outside ioki Platform.
Where payment is configured
- Which PSP, currency, merchant name, and accepted methods. In a provider’s Payment management settings.
- Enabling payment for a product. In the product’s Payment management settings.
- Viewing charges and recoveries. Payment transactions and Retried payments in Control Center.