Skip to content
TixFin

Payments

Take payment on the rails your market uses

Adyen, PayPal and Mollie sit behind one provider interface, next to a manual bank transfer flow. Enable them per project, and purchases, refunds and status checks route themselves.

Get started freeAll features

In short

How do payments work in TixFin?

TixFin uses a multi-provider payment architecture: Adyen, PayPal and Mollie implement the same provider interface, bank transfer runs through a built-in manual confirmation flow, and the platform routes purchases, refunds and status queries to the right one automatically. Each provider stores its credentials per project in the database, with a fallback to global configuration, so every payment method is fully multi-tenant. Idempotency keys protect refunds on every provider, and payment creation on Mollie, against duplicate transactions.

  • Adyen, PayPal, Mollie and bank transfer

  • Per-project credentials with global fallback

  • Idempotency keys on every refund

Capabilities

One interface, four rails

  • 01

    Unified provider interface

    A single PaymentProvider contract means purchases, refunds and status lookups behave the same across Adyen, PayPal and Mollie.

  • 02

    PayPal Orders API v2

    Payment link creation, order capture, refund and status lookup, with sandbox and live mode, OAuth2 token caching and webhooks for approval and capture.

  • 03

    Mollie payments

    Payment link creation, refunds and status lookup with SEPA Direct Debit, iDEAL, Bancontact, Klarna and other European methods, plus a webhook for automatic confirmation.

  • 04

    Manual bank transfer

    Buyers can place an order as a bank transfer; the system issues a reference, snapshots the payment data and holds the purchase pending until an admin confirms receipt.

  • 05

    Per-project configuration

    A payment methods tab in billing toggles each provider and stores its credentials for that project, so tenants never share a merchant account by accident.

  • 06

    Buyer-side clarity

    Confirmation mail, ticket detail view and pending states show transfer details including the payment reference, in German and English.

Specifications

Key facts

Supported methods
ADYEN, PAYPAL, MOLLIE, BANK_TRANSFER
Credential scope
Per project, with fallback to global configuration
PayPal integration
Orders API v2 with sandbox and live mode
Mollie methods
SEPA Direct Debit, iDEAL, Bancontact, Klarna and more
Duplicate protection
Idempotency keys on refunds across all providers, and on payment creation for Mollie

Payments

Methods the buyer actually recognises

The checkout shows the payment methods that are active for that tenant, as radio buttons whenever more than one is enabled. Bank account holder, bank name, IBAN and BIC are maintained once in the project billing profile and reused in the dashboard and the box-office checkout.

How it works

Getting paid

  1. 01

    Enable providers

    Turn on the rails you need in the billing payment methods tab — one, two or all four.

  2. 02

    Store credentials

    Enter provider credentials for this project; global configuration remains the fallback where a project has none.

  3. 03

    Sell

    Checkout offers the active methods, and the platform routes the purchase to the matching provider.

  4. 04

    Reconcile

    Webhooks confirm captured payments automatically; bank transfers are confirmed by an admin and then activate the tickets.

Use cases

Built for

FAQ

Payment questions

Ask the team

  • Yes. Adyen, PayPal, Mollie and bank transfer can each be enabled per project and run in parallel. The checkout shows the active methods and the platform routes each purchase to the matching provider.

  • No. Every provider stores its credentials per project in the database and falls back to global configuration only when a project has none, so payments are fully multi-tenant.

  • The buyer places the order as a bank transfer, the system generates a reference and snapshots the payment data, and the purchase stays pending until an admin confirms the incoming payment and the tickets activate.

  • Refund calls on every provider, and payment creation on Mollie, use idempotency keys, so a retried request cannot create a second transaction.

Set up your payment rails

Enable the providers your audience expects and start taking money the same day.