SeatGeek Checkout Technical Overview

Note: This documention is under active development. We would love your feedback as we continue to refine and improve it.
Please email with any questions, comments or concerns. Thanks!

SeatGeek Checkout is a ticket-buying experience hosted on or in a SeatGeek mobile app that allows a user to make purchases across multiple marketplaces using stored payment and delivery information.

SeatGeek Checkout consists of three main parts:

The SeatGeek API coordinates purchase requests betweens users and markets, handles storage of payment information and manages the delivery of electronic tickets to users' mobile devices.

A web service you deploy on your server is responsible for reserving inventory, capturing payments, creating shipping labels for physical tickets, and anything else that's part of your normal purchase flow (see the SeatGeek Checkout Web Service Reference for a detailed definition of the web service protocol).

Here's an overview of the interactions between client, SeatGeek API and market API in a typical e-ticket purchase:

The flow for physical tickets is similar, except that rather than providing eticket.url, your web service would provide shipment.tracking_num.

Payment Data Security

SeatGeek uses a payments platform called Spreedly to store and deliver payment data. In order for you to accept payment data via your web service API, Spreedly will need to verify that your integration meets their PCI compliance standard. See their article on Becoming a Receiver for more information.

Not equipped to handle payment data directly? That's all right, we can integrate directly with your existing payment processor. Email for more detail and to discuss integrations with specific vendors.

Protecting Against Fraud

SeatGeek can integrate with your existing anti-fraud solution both on the web and in our mobile apps. Email for more detail and to discuss integrations with specific anti-fraud vendors.