Cinemark

Level 1. Unused Movie Club credits become movie tickets that other people buy.

Status: built, never run for real

Two orders have run from start to finish on the Tempo testnet, with a stand-in doing the Cinemark step. The real Cinemark driver has never bought a ticket on cinemark.com, and no real money has moved.

At a glance

1. Credit holderHas Movie Club credits they will not use
2. BuyerPicks a showtime and pays a set price for the ticket
3. SalvoBuys the ticket on the holder's account, paid with their credits
4. BuyerGets an email with a link to the ticket and its QR code

If there is still no ticket when the showtime is 90 minutes away, the buyer is refunded automatically.

Movie Club credits cannot be transferred, but a member can buy a ticket for anyone from their own account. That is the whole idea: the credit holder's account buys the ticket, and the buyer is the one who watches the film.

The obvious questions

The credits can't be transferred. How is this possible?

Nothing is transferred. The ticket is bought on the credit holder's own account, the same as buying a ticket for a friend. The buyer receives the ticket, not the credits. Checkout applies the holder's Movie Club credits, and also any loyalty rewards it shows.

Is this allowed by Cinemark?

Probably not. Automating checkout with a saved sign-in almost certainly breaks Cinemark's terms. Selling tickets bought with Movie Club credits likely breaks the program's terms too; credits like these usually cannot be transferred and have no cash value, though no one has checked Cinemark's actual terms. The realistic downside is that Cinemark closes the account and the credits are lost, not legal action. The buyer still gets a real ticket. The risk falls on the credit holder, and today that is the operator.

Could it spend real money by mistake?

It is designed not to. The driver refuses to submit a checkout unless the total reads $0: once after applying credits, and again just before it submits. Both checks read the total the same way, and if no total can be read it stops. That guard has only been tested against a hand-built copy of the checkout page. It has never run on cinemark.com.

What if the showtime sells out, or the seat is gone?

If the showtime is sold out, the order fails and is not retried. If a seat is taken while the driver is picking it, the driver tries again, up to three times. The refund is not immediate: the automatic sweep refunds the buyer when the showtime is 90 minutes away, and the operator can refund sooner by hand.

What if the ticket never arrives?

A sweep runs every 15 minutes. Once an order still has no ticket and its showtime is within 90 minutes, the sweep refunds it, so the refund lands between 90 and about 75 minutes before the showtime. By default, orders can only be placed between 4 hours and 14 days ahead, so there is time to try first.

How does the buyer get their money back?

The same way they paid. A card payment is refunded through Stripe. A crypto payment is sent back from the operator's wallet, after checking the wallet holds at least the refund amount. If a refund fails, the operator is paged to do it by hand. After a refund succeeds the buyer is emailed, once email is set up with a verified sending domain.

What if Cinemark asks the account to sign in again?

If the sign-in wall appears before the purchase starts, the order is parked and waits. If it appears partway through, the order is marked failed. Either way it is not retried automatically, because retrying into a sign-in wall can lock the account. The operator signs in again by hand, then taps the order's link to run it. If nobody does, the buyer is refunded when the showtime is 90 minutes away.

Whose credits are these, and how does the holder get paid?

Today, only the operator's own account. The buyer's payment goes to the operator. Other people's credits are not supported: there is no way to sign up as a credit holder.

Is it live?

No. See the status box above, and the Roadmap.

Where it lives in the code

Cinemark is an account_bound form factor: the value sits inside an account and is spent at checkout, so a caught pattern lands on a person's account, not on a card. See Form factors, Order lifecycle and Payment rails.