Ticketing Platforms

Browse Diem Apps, connect an enabled ticket provider, choose who pays its checkout fee, import events, and understand provider-specific limits.

On this page

Use only providers shown as enabled

The current source contains adapters for Posh, Bookt, and Eventbrite. Browse the public Diem Apps directory for what each app does, supported authentication, setup guidance, and its current checkout fee. The directory reads enabled providers and sanitized pricing from Diem's database-backed public catalog; the seller app remains authoritative for whether a provider can be connected.

Connect and import

  1. Open Apps

    Choose the enabled provider you already use, review its details and current fee, then select Connect.

  2. Use the provider's authentication method

    The connector may request a phone verification code or that provider's email and password. Enter credentials only in the intended connector screen.

  3. Complete verification

    Use the newest verification code when one is required. Wait for the provider connection to report success.

  4. Review imported events

    Open Listings and confirm the expected events and ticket types appear. Refresh is available when the adapter declares manual sync and exposes the Refresh action.

  5. Choose who pays

    On the connected account, choose Purchaser pays or Merchant covers. The setting applies to future checkouts on that specific account.

Connect more than one account per provider

Inside the dashboard, each app's icon shows who is connected: the connected account's photo (or a plain avatar when the provider does not expose one) appears as a small badge overlapping the app icon, on both the Apps list card and the app detail page. When more than one account is connected, a count badge shows how many. This connection state is personal to your Diem account, so it never appears on the public Apps directory described above.

You are not limited to one account per provider. Select Connect another account from an already-connected app's detail page to authenticate a second (or third) account of the same provider — useful when you run tickets through more than one organizer login. Each connected account keeps its own imported item count, connected and last-synced dates, and fee-payer choice, and can be refreshed or disconnected independently without affecting the others.

Choose who pays the integration fee

Bookt, Posh, and Eventbrite use provider-specific percentage and fixed fee components stored on the enabled Provider.config.checkout_fee record. Diem does not keep a separate website formula. Review the live schedule and its linked source on the app detail page before enabling checkout. When more than one account of the same provider is connected, each account has its own fee-payer choice.

Integration fee-payer choices
ChoiceCheckout effectProceeds effect
Purchaser paysThe configured integration fee is added to the purchaser charge at checkout.The integration fee does not reduce the ticket-base proceeds; Stripe processing and other deductions still apply.
Merchant coversThe purchaser is charged the ticket base amount.The integration fee reduces merchant proceeds before Stripe processing and any other deductions.

The choice is stored as ProviderAccount.settings.integration_fee_payer. The live app detail page identifies the Provider policy's current default and available choices. At order creation the server calculates the fee from base ticket lines and creates an immutable Purchase.checkout_pricing snapshot containing the provider, currency, payer, base subtotal, integration fee, purchaser charge, merchant net, policy, and calculated components. A later fee or payer change does not reinterpret that purchase. Free ticket orders remain fee-free.

Manage the source event in the provider

Imported events are read-only in Diem. Change event details, ticket types, price, capacity, and availability in the original provider, then refresh or allow the next synchronization to update Diem.

  • Use Listings to search and review the imported result.
  • Attach imported events to a keyword or public Link Page section.
  • Test the buyer-facing event and ticket descriptions after each provider change.
  • Verify fulfilled guests in both Diem and the source provider.
  • Use Refresh for an immediate account sync when the provider exposes it; otherwise wait for its scheduled synchronization.
  • Use Edit Configuration only when the provider declares a working configuration action.
  • Use Disconnect to attempt upstream revocation when the adapter implements it, clear the account credentials, stop future scheduled sync, hide its groups, and mark imported events unavailable. Historical imports remain for purchases and support.

Known provider limitations and errors

Provider integration issues
IssueCurrent guidance
Bookt or Eventbrite can partially synchronize.Compare event and ticket counts against the source before sharing the checkout.
Refresh is not shown.The adapter did not declare both manual sync and the Refresh action. Wait for scheduled sync or contact support instead of inventing a provider-specific refresh path.
Edit Configuration is not shown.The adapter has no declared configuration action and hook. Provider-level application settings remain protected in the database Provider record.
Disconnected events still appear in history.This is intentional. Disconnect removes credentials and availability but retains imported records for purchase history and investigation.
Provider fulfillment can remain Processing or need attention.Confirmation waits for fulfilled delivery or an intentional no-provider path, but verify the guest in the external provider before resolving a dispute.

Next guide

Payments & Delivery
Ticketing Platforms | Diem Documentation