Ticket Transfer

Your marketplace sells tickets.
Now it can transfer them.

Ticket fraud exists because transfers are unverified. Deck fixes that. Identity-checked on both sides, executed on the issuing platform, and fully auditable. Your buyers get real transfers, not promises and PDFs.

Order #TRD-4819
Ticketmaster
Lakers vs Celtics Apr 12 · Crypto.com Arena · 7:30 PM
Sec 112 Row A
Seller James Miller @jmiller
Buyer Sarah Chen @sarahc
Ready to transfer
Transfer Progress
Seller verified Identity confirmed on Ticketmaster
Buyer eligibility Transfer recipient approved
Platform authenticated Logged into ticketmaster.com
Transfer initiated Ticket reassigned to buyer
Ownership transferred Confirmation TM-84201

Your buyers get real tickets, not promises.

Deck executes transfers on the issuing platform. Ownership changes at the source. Real reassignment, not a forwarded PDF or screenshot.

Ticketmaster
AXS
SeatGeek
StubHub
Vivid Seats
Eventbrite
Live Nation
Dice
Gametime
Any ticketing platform with a login.

Transfer on any platform, no API needed

No ticketing platform offers transfer APIs for secondary markets. Deck navigates the platform directly. If a seller has an account, you can transfer there.

Seller links account Via your app · Auth Component or API
Credentials stored Encrypted in Deck Vault · AES-256
Buyer eligibility verified Identity check · Transfer eligibility
Session established Authenticated, ready to transfer

Fraud drops when both sides are verified

Seller authenticated, buyer verified, before any transfer begins. Credentials stay encrypted in Deck Vault. Your platform never touches a password.

POST /tasks/v1/ticket-transfer/run
200 OK
{
  "platform": "Ticketmaster",
  "event": "Lakers vs Celtics",
  "section": "112",
  "row": "A",
  "transfer_id": "TM-84201",
  "status": "completed",
  "buyer_verified": true
}

Every transfer is documented and auditable

Transfer ID, verification status, event details. Structured and logged automatically. When disputes arise, the proof is already there.

Authorize. Transfer. Confirm.

Store your seller’s platform credentials, trigger the transfer, and get verified confirmation back.

POST /v2/credentials
{
  "source": "ticketmaster.com",
  "credentials": {
    "username": "...",
    "password": "..."
  }
}

Store credentials

Sellers link once. Deck encrypts in Vault. One connection enables every future transfer.

POST /tasks/v1/ticket-transfer/run
{
  "credential_id": "cred_tm",
  "event": "Lakers vs Celtics",
  "section": "112",
  "row": "A",
  "buyer_email": "buyer@..."
}

Execute transfer

One API call. Deck logs in, locates the ticket, and completes the official reassignment. Your marketplace never touches the portal.

task_run.completed
{
  "transfer_id": "TM-84201",
  "platform": "Ticketmaster",
  "event": "Lakers vs Celtics",
  "status": "completed",
  "buyer_verified": true,
  "runtime_ms": 7240
}

Receive results

Deck completes the transfer and returns a structured confirmation. Transfer ID, platform, verification status. Same schema, every platform, every time.

Who’s this for?

Secondary ticket marketplaces

Turn your marketplace into a transfer platform. Deck eliminates fraud claims by executing real transfers at the source.

Event platforms

Let fans transfer tickets directly through your product. Deck handles the platform-side execution so you don’t have to.

Fan-to-fan resale apps

Sellers list, buyers pay, and Deck moves the ticket. The entire experience stays inside your app.

Enterprise ticket management

Distribute season tickets or corporate seats across employees with Deck handling every transfer automatically.

FAQ

Any platform where transfers can be completed through a browser. Ticketmaster, AXS, SeatGeek, and venue-specific systems. If a human can transfer a ticket there today, Deck can handle it.

Deck verifies seller identity through their authenticated session on the ticketing platform. Buyer verification can integrate with your existing identity layer or be handled as part of the transfer flow.

Failed transfers return with a specific reason: wrong credentials, platform error, ticket already transferred, or transfer restrictions. Your platform handles the downstream notification.

Credentials are encrypted in Deck Vault and used only during the transfer session. They are never exposed to your platform, the buyer, or any third party.

Deck operates within the same constraints a human would face. If a platform restricts transfers for certain events, Deck will return that status so your platform can handle it.

Most transfers complete in under a minute. Deck handles authentication, navigation, and confirmation automatically. Your system receives the result via webhook.