MAJORFailure Reference

Pika Watermark Bleed — Refund Guide

Technical Classification

Tier-Conditional Watermark Routing

Tier-Conditional Watermark Routing on Pika occurs when the post-generation watermark-strip pipeline fails to read the user's subscription tier from the request envelope. The watermark is added during generation and removed in a post-process step keyed on subscription state. When the auth header race-condition fires (rare, but well-documented in Pika user reports), the strip step skips and a paid clip ships with the free-tier watermark visible.

How to identify this failure

✕Pika logo visible in bottom-right corner on paid Standard/Pro output
✕Faint watermark texture across the clip
✕Watermark appears on some clips in a batch but not others (request-level race)
✕Re-running the identical prompt produces watermark-free output

Real generation examples

Prompt used

"A sailing yacht at sunset, slow dolly forward"

Failure observed @ 0:00 → 0:04

Bottom-right Pika watermark visible throughout the 4-second clip

Documentation strength

If you need to escalate

HIGH — Pika support refunds watermark-on-paid as a billing error within 24h with the generation ID.

AVA is a pre-purchase prevention tool, not a post-purchase recovery tool. Platforms generally do not guarantee credit refunds for output-quality failures; goodwill credits are at each platform's discretion. The strength rating reflects how well-formed your support ticket can be, not a promised outcome.

Prevention + documentation steps

01
Score your prompt before you generate
Run your prompt through AVA's pre-flight scoring against the Tier-Conditional Watermark Routing pattern. Green light = generate. Yellow/red = rewrite using the suggested fix before you commit credits.
02
Capture Generation ID + timestamp if it failed anyway
Find the Generation ID in the URL or share link. Note the exact time when the Tier-Conditional Watermark Routing first appears (e.g. "failure first visible at 1.2s"). Timestamped evidence is significantly stronger than a general complaint.
03
Use the correct technical term in your support ticket
Describe this failure as "Tier-Conditional Watermark Routing". This term maps to a recognised internal workflow in the support system and routes the ticket to the right team.
04
Submit via the correct support channel
Runway has no direct email intake. Pro+ plan: open the in-app AI Assistant (help widget bottom-right of app.runwayml.com), describe the failure with the technical term, attach evidence. Free/Standard plan: human support isn't available — your channel is Discord #community-help with @On Call - Moderators.

Frequently asked questions

Will Pika support response credits for watermarked paid output?

Yes — open a ticket citing "watermark on paid tier output" with the generation ID. Pika treats this as a billing-system bug and refunds credits without question.

Why does the Pika watermark sometimes appear on paid clips?

The watermark-strip step is keyed on subscription state read from request metadata. Under specific routing conditions the metadata read can fail-open and the strip step is skipped.

How do I avoid the Pika watermark bug?

Re-run the same prompt — the bug is request-level, not prompt-level. AVA flags watermark-present output before you publish.

Score your prompt

Score your prompt against this failure mode in 30 seconds

Paste your prompt and the platform you intend to use. AVA returns a red/yellow/green score against this specific failure mode plus a concrete rewrite if the risk is high.

Install free All 105 failure modes

AVA Pro · founders' round

$50 for 6 months of unlimited scoring across all failure modes + personal failure-history dashboard. Locks in $13/mo grandfathered after.

Claim $50 founders