Integrator Guide

This comprehensive guide covers everything an integrator (marketplace, venue, or platform) needs to know to build on TIX Protocol.

What is an Integrator?

An integrator is a third-party platform that uses TIX Protocol for ticketing operations:

  • Ticketing marketplaces — Primary and secondary ticket sales

  • Event organizers — Direct-to-consumer ticket issuance

  • Venue box offices — On-site ticket operations

  • Fan clubs — Exclusive access and ticket distribution

Getting Registered

Registration Process

  1. Contact Protocol Operator — Request integrator registration

  2. Provide Authority Key — Your signing authority public key

  3. Co-sign Registration — Both parties sign the registration transaction

  4. Receive Integrator Account — PDA created with your identity

Registration Transaction

Fund Your Treasury

Your treasury must have USDC to pay protocol fees:

Managing Events

Create an Event

Event Planning Checklist

Step
Action

1

Define total ticket supply

2

Set royalty percentage and floor

3

Create USDC ATAs for royalty recipients

4

Calculate BPS splits (must sum to royaltyBps)

5

Choose unique event ID

6

Register event on-chain

Query Event State

Issuing Tickets

Batch Issuance

Ticket ID Management

Facilitating Transfers

Integrator-Initiated Transfer

As an integrator, you can transfer tickets on behalf of holders:

When to Use Integrator Transfer

Scenario
Use Integrator Transfer?

User requests transfer in your app

✅ Yes

Bulk transfers during migration

✅ Yes

Correcting issuance errors

✅ Yes

Transferring without user consent

❌ No (policy decision)

Ticket Lifecycle Management

Mark Ticket as Used (Redemption)

When a fan enters the venue:

Mark Ticket as Void (Cancellation)

For refunds or chargebacks:

Listing Management

Cancel Listings

Integrators can cancel any listing for their events:

When to Cancel Listings

Reason
Action

Event cancelled

Cancel all listings

Suspicious activity

Cancel fraudulent listings

Policy violation

Cancel violating listings

Price cap exceeded

Cancel overpriced listings

User request

Help user cancel

Controlling Transfers & Resale

TIX Protocol provides integrators with fine-grained control over ticket transfers and secondary market activity. These settings are configured at the event level.

Resale Price Caps

Prevent ticket scalping by setting a maximum resale price for your events. When a price cap is set, any listing exceeding the cap will be rejected by the protocol.

Price Cap Enforcement

Scenario
Listing Attempt
Result

Price within cap

$150 (cap is $200)

✅ Listing created

Price exceeds cap

$250 (cap is $200)

ResalePriceExceedsCap error

No cap set

Any price

✅ Listing created

Use Cases for Price Caps

Use Case
Recommended Cap

Community events

100-120% of face value

Charity events

Face value only (100%)

Premium events

No cap (market-driven)

General admission

150-200% of face value

Disabling Transfers

For events where tickets should be non-transferable (e.g., identity-verified events), you can disable peer-to-peer transfers entirely.

What Happens When Transfers Are Disabled

  • transferPermit calls fail — Returns TransfersDisabled error

  • Integrator transfers still work — Integrator authority can still transfer tickets for customer service purposes

  • Listings still possible — Unless resale is also disabled (see below)

Use Cases for Disabling Transfers

Scenario
Reason

Identity-verified events

Ticket must match ID at entry

Corporate events

Employees only

VIP experiences

Prevent unauthorized access

Promotional giveaways

Ensure original recipient attends

Disabling Resale

Completely block secondary market listings for an event. This is more restrictive than price caps and prevents any resale activity.

What Happens When Resale Is Disabled

  • listTicket calls fail — Returns ResaleDisabled error

  • No secondary market activity — Tickets cannot be listed for sale

  • Direct transfers may still work — Unless transfersEnabled is also false

Configuration
Transfers
Resale Listings

Default (both enabled)

✅ Allowed

✅ Allowed

resaleEnabled: false

✅ Allowed

❌ Blocked

transfersEnabled: false

❌ Blocked (owner)

✅ Allowed

Both disabled

❌ Blocked (owner)

❌ Blocked

Combining Restrictions

You can combine multiple restrictions for maximum control:

Updating Event Settings

If you need to modify transfer/resale settings after event creation:

Note: Changing settings does not affect existing listings. Cancel active listings before tightening restrictions.

Authority Management

Update Your Authority Key

If you need to rotate keys:

Key Security Best Practices

Practice
Description

HSM Storage

Store authority keys in hardware security modules

MPC Wallets

Use multi-party computation for signing

Key Rotation

Regularly rotate authority keys

Audit Logging

Log all authority operations

Access Control

Limit who can access authority keys

Monitoring & Analytics

Query Your Integrator State

Monitor Treasury Balance

Track Event Metrics

Integration Patterns

Webhook-Based Integration

Troubleshooting

Common Issues

Issue
Cause
Solution

IntegratorSuspended

Your integrator is suspended

Contact protocol operator

InsufficientFunds

Treasury lacks USDC

Fund your treasury

Unauthorized

Wrong authority key

Use correct signing key

SupplyExceeded

Event sold out

Check remaining supply

Transaction timeout

Network congestion

Retry with priority fee

Debug Checklist

  1. Is integrator status Active?

  2. Is treasury funded sufficiently?

  3. Are you using the correct authority key?

  4. Is the event ID correct?

  5. Is the ticket ID within supply bounds?

  6. Is the permit in the correct status?

Next Steps

Last updated