Datatrans
Datatrans
Datatrans & Oniva – Secure payment processing for your events
Accept payments directly on your event website – secure, fast and PCI DSS compliant.
The direct integration of Datatrans into Oniva enables seamless and secure payment processing directly on your event registration page. Participants can pay using common payment methods such as credit cards, TWINT, PostFinance or Apple Pay – without being redirected to external pages. As a leading Swiss payment gateway, Datatrans meets all PCI DSS and GDPR requirements. The integration runs entirely in the background and requires no further effort once activated.
Instructions
- Activate integration in Oniva: Enable online payments in your event settings.
- Define pricing: Set ticket prices and applicable VAT within your event’s booking options.
- Go live: Publish your event to start accepting registrations.
Requirements
- Valid Oniva licence agreement
Licence & pricing
- All licences
Available across all licence tiers - Enterprise licences
Option to connect your own payment ID (see pricing)
Use cases
- Ticketing for paid conferences: Participants purchase tickets directly on the event website using credit card or TWINT, without external ticketing platforms.
- Multi-tier pricing: Early bird, regular and VIP pricing can be configured in Oniva and automatically processed via Datatrans.
- Refunds: In case of cancellations, refunds can be triggered via the Oniva support portal API.
Further links
- Events with payment - Oniva support article
- Refund request form - Oniva contact form
- Datatrans - Datatrans website
Validate your use case
Want to check your specific use case with Oniva? Get in touch with us.
Frequently asked questions
Visa, Mastercard, TWINT, PostFinance and Apple Pay. Additional methods are available on request.
Yes, Datatrans is PCI DSS Level 1 certified. Card data are never transmitted via Oniva servers.
A 5% payment commission (including credit card fees) is charged on net ticket revenue.
Yes, Oniva supports CHF and EUR. The desired currency can be defined per event.
Participants receive an error message and can retry using another payment method. Registration is only confirmed after successful payment.