How Protected Transfers work

A protected coordination layer for peer-to-peer ticket transfers. The ticket still moves through the original issuer (Ticketmaster, AXS, etc.) — Secure Ticket Transfer is the protected workflow around it, with payments and payouts powered by Stripe.

1. Step 1

   Buyer payment is protected

   When the buyer pays, funds are secured through Secure Ticket Transfer's protected payment flow powered by Stripe. Sellers see payment confirmation immediately, but payouts remain protected until the transfer is verified.

   Powered by StripeProtected payout flowTransaction accountability
2. Step 2

   Seller completes secure payout onboarding

   Sellers complete secure payout onboarding through Stripe before receiving protected payments. This identity and payout verification helps reduce fraud and creates accountability for both sides. Stripe may ask sellers for identity and banking details before payouts can be enabled.

   To avoid delays, sellers should complete onboarding before listing tickets.

   Stripe identity verificationSecure payout onboardingSeller accountability
3. Step 3

   Tickets transfer through the original provider

   The seller transfers tickets through the original ticket provider (Ticketmaster, AXS, SeatGeek, etc.) directly to the buyer's verified email.

   Official issuer transferVerified buyer email
4. Step 4

   Transfer evidence is recorded

   Transfer timestamps, communication history, and private proof uploads are recorded inside the transaction room to support review if needed. STT does not independently authenticate tickets.

   Transfer evidenceServer-owned timestampsPrivate transaction history
5. Step 5

   Buyer confirms or reports a problem

   The buyer confirms only after the correct tickets appear in their issuer account. If the buyer is silent after the response deadline, the seller may request an audited STT review—silence alone never releases funds.

   Buyer confirmationDispute freezeAudited delivery review