Skip to main content

Website Integration: Partial

Build a custom browsing and cart experience on your website, then hand off to the SECUTIX checkout for payment and finalization.

This architecture offers the flexibility to design your own ticketshop while leveraging the reliability and security of SECUTIX's PCI-compliant payment infrastructure.

Architecture Overview​

Website Partial Integration Architecture

Integration Steps​

The numbered steps below correspond to the flows shown in the architecture diagram.

  1. Retrieve Catalog — Your backend calls the Catalog API to retrieve in real-time all products available on the sales channel. This includes product descriptions, names, pictures, dates, tariffs, prices, and sales periods across all product families (events, competitions, memberships, season tickets, visit passes). Since catalog calls are scoped to a {salesChannelId}, each channel can expose different products and pricing. The API is designed to be called on demand — no client-side caching is required. See Catalog Overview.

  2. Availabilities — For each product on sale, your backend fetches real-time availability using the dedicated availability endpoints. Availability endpoints exist at product, event, performance, and seat level. The APIs deliver up-to-date data directly — no client-side caching or polling strategy is needed.

  3. Sales — Create Order — Your backend uses the Sales API to build the cart on behalf of the user. Start by creating an order with POST /s360/v3/orders/sales, then add products using the appropriate operation endpoints (e.g., POST /s360/v3/orders/performance-operations for event tickets, POST /s360/v3/orders/membership-operations for memberships). You can retrieve and display the cart contents at any time with GET /s360/v3/orders/{orderId}. For seated events, you can optionally embed the Seatmap Widget in your frontend for interactive seat selection. See How to Complete an Event Sale and Understanding Orders and Sales for detailed workflows.

  4. Redirection (Checkout) — Once the order is built, the user is redirected to the SECUTIX Ticketshop to complete the checkout (payment and finalization). Use the Cart Deep Link to send the user directly to their cart on the ticketshop. If the user is not yet authenticated, login or contact creation will be required at this stage. SECUTIX handles promotional code, shipment selection, payment (via the S-Pay / Adyen integration), and order finalization.

  5. Authentication & SSO — When the user needs to be identified (for order creation or checkout), two scenarios are supported: either the user logs in directly at the ticketshop after redirection, or they are already authenticated on your website via your own Identity Provider (IdP) and SECUTIX seamlessly re-authenticates them using SSO (OIDC). See Contact SSO (SECUTIX as Service Provider) for configuration details.

Optional: Seatmap Widget​

For seated events, you can embed the SECUTIX Seatmap Widget directly in your frontend to let users interactively select their seats before the order is created (step 3). The widget handles 2D/3D venue rendering and seat selection, and returns the selected seat identifiers that your backend passes to the Sales API when adding operations to the order.

Usage Plan​

This integration pattern maps to the TS_PARTIAL usage plan. Available tiers: BASIC (18 req/s), STANDARD (90 req/s), PREMIUM (450 req/s). See Rate Limits for full details.

When to Choose This Pattern​

Choose Partial when...Consider instead...
You want full control over browsing & cartDisplay only → Catalog Display
You prefer not to handle payments (PCI)Full control → End-to-End
The standard SECUTIX checkout works for you