Credit Refunds

Overview

Credits are automatically refunded when generations fail. This guide explains how credit refunds work, when they occur, and how to verify refunds.

When Credits are Refunded

Automatic Refunds

Credits are automatically refunded when:

Generation Fails: If a video or image generation fails
Processing Timeout: If generation takes too long (typically 150+ minutes)
System Errors: If platform errors cause generation to fail
API Failures: If external service (AI model) fails

Refund Timing

Immediate: Refunds typically occur immediately when failure is detected
Automatic: No manual action required
Processing Time: May take a few minutes to appear in transaction history

How Refunds Work

Refund Process

Generation Starts: Credits are deducted when you click "Generate"
Generation Fails: System detects failure
Automatic Refund: Credits are automatically refunded to workspace
Transaction Record: Refund transaction is recorded in history
Balance Update: Credit balance updates with refunded amount

Refund Amount

Full Refund: You receive the full amount of credits back
No Partial Refunds: All credits used for failed generation are refunded
Original Cost: Refund amount equals the original deduction amount

Viewing Refunds

Transaction History

Access Transactions: Settings → Credits tab → Transactions sub-tab
Filter Refunds: Use "Transaction Type" filter, select "Refund"
View Details: Expand refund transactions to see details
Verify Amount: Check that refund amount matches original deduction

Location: Settings → Credits → Transactions sub-tab, filter by "Refund" type.

Refund Transaction Display

Refund transactions show:

Title: Feature name (e.g., "Quick Video")
Type: "Refund" (with refresh/refund icon)
Amount: Positive amount (credits refunded)
Status: "Completed" (when refund processed)
Date: When refund occurred
Details: What was refunded and why

Credit Summary

When you expand a refund transaction, you'll see:

Balance Before: Credit balance before refund
Action: "Refunded X credits" with reason
New Balance: Updated balance after refund

Refund Reasons

Common Refund Reasons

Generation Failure: AI model failed to generate content
Processing Timeout: Generation exceeded time limits
System Error: Platform or service error
Invalid Input: Input parameters caused generation to fail
Service Unavailable: External AI service unavailable

Understanding Refund Messages

Refund transactions include error messages explaining why the refund occurred:

Technical Errors: Service or API failures
Timeout Errors: Generation took too long
Validation Errors: Input issues that prevented generation
System Errors: Platform infrastructure issues

Failed Generation Detection

Automatic Detection

The platform automatically detects failed generations through:

Status Monitoring: Tracks generation status
Timeout Detection: Monitors generation duration
Error Logging: Records errors and failures
Cron Jobs: Periodic checks for stuck/failed generations

Timeout Threshold

Standard Timeout: 150 minutes (2.5 hours)
Automatic Marking: Generations exceeding timeout are marked as failed
Automatic Refund: Credits refunded when timeout detected

Verification

Checking for Refunds

Review Failed Generations: Check generation history for failed items
Check Transactions: Look for refund transactions in credit history
Verify Balance: Ensure credit balance increased appropriately
Match Amounts: Verify refund amount matches original deduction

What to Check

Refund Presence: Is there a refund transaction for the failed generation?
Refund Amount: Does refund match the original deduction?
Balance Update: Did your credit balance increase by refund amount?
Transaction Status: Is refund status "Completed"?

Best Practices

Monitor Generations

Check Status: Regularly check generation status
Review Failures: Review failed generations to understand issues
Verify Refunds: Confirm refunds are processed for failures
Report Issues: Contact support if refunds don't occur

Understand Failures

Common Causes: Learn common causes of generation failures
Prevent Failures: Optimize inputs to reduce failure rates
Retry Strategy: Retry failed generations if appropriate
Contact Support: Reach out if failures seem unusual

Track Refunds

Regular Review: Periodically review refund transactions
Monitor Patterns: Identify patterns in failures and refunds
Budget Planning: Account for potential refunds in credit planning
Optimize Usage: Reduce failures to minimize refund processing

Troubleshooting

Refund Not Received

Check Status: Verify generation actually failed
Wait for Processing: Refunds may take a few minutes
Check Transactions: Look in transaction history for refund
Verify Balance: Check if balance updated
Contact Support: If refund doesn't appear after reasonable time

Incorrect Refund Amount

Review Original: Check original deduction amount
Compare Amounts: Verify refund matches deduction
Check Details: Expand transaction to see full details
Contact Support: If amounts don't match

Refund Status Issues

Pending Status: Refund may be processing (wait a few minutes)
Failed Status: Refund failed (contact support)
Check Error: Review error messages in transaction details
Retry: System may retry failed refunds automatically

Examples

Successful Refund

Original Transaction:

Type: Usage
Feature: Quick Video
Amount: -12 credits
Status: Failed

Refund Transaction:

Type: Refund
Feature: Quick Video
Amount: +12 credits
Status: Completed
Result: Full 12 credits refunded to workspace

Timeout Refund

Scenario: Generation took 160 minutes (exceeded 150-minute limit)

Process:

Generation marked as failed (timeout)
Credits automatically refunded
Refund transaction recorded
Credit balance updated

Result: Full credits refunded, can retry generation

Understanding Credits: Learn about the credit system
Credit Transactions: View refund history
Credit Costs: Understand original costs
Troubleshooting: Resolve generation failures