What EventMS Pro connects to

Payments: your accounts, your settlement

Stripe and PayPal are both integrated using each vendor’s official SDK, and you supply your own API keys. That matters more than the integration itself: money moves from your attendee directly to your merchant account, with no intermediary holding funds and no platform taking a cut. Webhook endpoints handle the asynchronous side, so an order is only finalized when the provider confirms the payment, not when the browser says so.

• Stripe and PayPal, both via official SDKs, using your own keys
• Webhook-confirmed order finalization rather than client-side trust
• Refunds, cancellations, and per-organizer payouts built in
• Manual and box office bookings for cash or offline sales

A documented REST API, not an afterthought

The platform is an API-first Laravel application: the frontend you receive is a client of the same REST API you get access to. Endpoints are documented with OpenAPI/Swagger, so you can browse the surface, generate clients in your language of choice, and wire the platform into a CRM, an accounting system, or an internal dashboard without waiting on anyone’s roadmap.

• Token authentication via Laravel Sanctum
• OpenAPI/Swagger documentation generated from the codebase
• Role-scoped endpoints for admin, organizer, and scanner clients
• Bulk event import for migrating from another platform

Real-time without a mandatory subscription

Live updates run over WebSockets, and you choose the transport. Pusher works if you want a hosted service, and Laravel Reverb is included if you would rather run your own WebSocket server on the same box. That choice is the difference between owning your stack and owning most of it: nothing about real-time forces a recurring bill on you.

• Pusher or self-hosted Laravel Reverb, your call
• Private admin and per-user channels plus public broadcast
• Live dashboards, notifications, and order status updates

Accounts, media, and calendars

Social login is available through Laravel Socialite alongside standard email registration. Media runs through a driver layer, so Cloudinary is the default rather than a lock-in: images are processed and optimized on upload and served from a CDN, and the storage backend can be pointed elsewhere. Attendees can subscribe to personal iCal feeds of their tickets and RSVPs, which sync into Google Calendar, Apple Calendar, or Outlook automatically.

• Social login plus email registration, via Socialite
• Swappable media storage with image optimization on upload
• Subscribable iCal feeds for tickets and RSVPs
• PDF generation for tickets and invoices, QR codes for door scanning

When something is not integrated yet

You have the source. That is the honest answer, and it is a better one than a roadmap ticket. Because the platform is a standard Laravel application with a documented API, any developer who knows the framework can add an integration, and you are not waiting for a vendor to decide your use case is worth prioritizing. If you would rather not do it yourself, custom integration work is quoted separately.