STRYK Payments.

Booking, payment intent, method, amount, provider state, fees, refund, invoice and remaining balance.

Cash, bank transfer, credit card, PayPal, OTA payment, company account and other, each with date, reference and note. In Austria and Germany, cash and card payments on site need the ‘Cash register & fiscalisation’ add-on.

Yes. Paid amount, remaining balance and state are updated from recorded payments and shown on the stay.

Yes. With permission a payment can be removed; invoice and booking payment state are then recalculated from the remaining amounts.

Online payments run exclusively via the integrated payment service. Which methods your guests see, for example credit card, PayPal, Apple Pay or EPS, depends on the methods enabled in your hotel’s payment account. Bank transfer is not available in the online checkout.

Your hotel needs its own payment account connected to STRYK. Online payments run exclusively via the integrated payment service; bank transfer is not offered in the online checkout. Bank transfers received can still be recorded manually on the invoice.

No. Onboarding, test mode, credentials, approved methods and connection test must be complete. Test credentials may not appear as live payment.

Yes. The rate plan defines whether the guest pays at the property, in full in advance, or with a deposit and remaining balance. STRYK automatically calculates the amount due.

Yes, for direct bookings paid online: STRYK automatically collects the balance via the integrated payment service at the cancellation deadline, or immediately if there is no free cancellation period. If a collection fails, STRYK tries again on the following days and then flags the case for manual follow-up. For an issued, open invoice, STRYK also creates a payment link that you copy or send by email; the guest pays the open amount via the integrated payment service.

Scheduled payments have states such as scheduled, blocked, failed or manual required. The payment area shows open actions centrally.

Yes, where provider and method enable the capability. STRYK keeps authorisation and capture as separate traceable states.

Yes. STRYK supports partial and full refunds and checks that no more than the captured amount is returned.

The operation receives a visible failure state and safe message. STRYK does not record success unless the provider confirmed it.

Payment actions, webhooks and manual payout matches use idempotency keys or unique events so retries are not silently booked twice.

Provider events are validated, assigned to the property and protected against replay. Invalid or unassignable notifications are rejected.

Yes. Estimated provider fee, net amount and actually reported fees are kept separately in payment and ledger context.

Yes. Payouts, commissions, fees, refunds and unmatched lines are shown separately and can be deliberately matched to a booking or ledger line.

Clear payments, commissions, fees and refunds are matched automatically. Conflicting or incomplete lines remain visibly under manual review until finance resolves them.

Transactions, captured amounts, refunds, fees, scheduled balances, payout state and unmatched items in one dashboard.

Yes. CSV and spreadsheet-compatible exports include transactions, operations, schedules, ledger, payouts and matches. Generated exports remain available in history.

Payment and finance actions are role-based. Sensitive provider settings and corrections remain limited to responsible employees.

Yes. Payment activity, payment providers, bookings and payouts remain clearly assigned to the relevant property.

The payment features are included in the STRYK price, with no set-up fee. For direct bookings paid online, a STRYK platform fee of 1.9% applies; the payment service also charges its own transaction fees. Without online payment, there is no platform fee.