Refunds

Failed renders cost $0

FARPY is designed to charge for successfully completed rendered frames rather than failed render attempts. If a wallet-funded render fails after a debit was recorded, that debit should be returned to the FARPY wallet balance.

Cancelled work

Work cancelled before completion is not charged as completed output. The exact job record remains important because cancellation timing and job lifecycle state determine what the system recorded.

Completed-frame charges

A successful Blender Cycles frame is billed at the public completed-frame rate shown on the pricing page. One still image counts as one frame. A refund request is not created merely because a completed frame took longer than expected.

Wallet corrections

A wallet correction returns value to the FARPY account balance when a render debit, credit entry, or related wallet record is wrong. Wallet credits are intended for FARPY render jobs. This page does not promise that every reviewed issue will be returned to the original payment method.

Card and payment reviews

If a card payment, top-up, duplicate charge, or payment record appears wrong, FARPY reviews the available account, payment, wallet, job, and receipt evidence. Public-alpha refund handling is reviewed case by case rather than through a blanket automatic-refund promise.

Duplicate charges or credits

Report a duplicate card charge, duplicate wallet credit, repeated debit, or incorrect amount. Do not submit repeated payments while a payment result is still unclear. Include enough evidence to identify each affected transaction.

Bitcoin Lightning top-ups

Bitcoin Lightning top-ups can require different payment evidence from card payments. Include the FARPY account email, payment amount, approximate payment time, and any available Lightning invoice or payment identifier when requesting review.

Receipts and proof

A receipt can show the job identifier, completed-frame count, cost, renderer, and related verification details. Include the receipt identifier and job identifier when available. Receipt and proof records help review what the system recorded but do not by themselves guarantee a refund outcome.

What support needs

Provide the account email, job_id, receipt_id, affected amount, payment method, approximate date and time, and a plain description of what appears wrong. Include the payment intent or other payment identifier when available. Never send full card numbers, passwords, private keys, or account credentials.

How to check before contacting support

Review the workspace job state, wallet balance, receipt, completed-frame count, and available proof. Compare the recorded amount with the public pricing rules. This can distinguish a failed job, completed job, duplicate payment, delayed balance update, or misunderstood frame count.

No invented refund deadline

This public-alpha page does not publish a guaranteed review time, automatic approval rule, fixed refund window, or bank-processing deadline. Payment processors and financial institutions may also control when an approved payment-method correction becomes visible.

Contact FARPY support

Email support@farpy.com with the relevant job and payment details. Send one clear report per issue so the job, receipt, wallet, and payment records can be reviewed together.

Related billing resources

Review completed-frame pricing, inspect your workspace, check receipt guidance, read the files and delivery guide, or add credits through top-up.

Refund and billing questions

Are failed renders charged?

No. Failed renders cost $0.

What happens if a failed wallet-funded render was debited?

The debit should be returned to the FARPY wallet balance.

Are completed frames refundable automatically?

No automatic rule is stated. Incorrect payment, render, wallet, or receipt records are reviewed case by case.

What should I include in a billing report?

Include the account email, job_id, receipt_id, amount, payment method, timing, and payment identifier when available.

Should I send my complete card number or password?

No. Do not send complete card numbers, passwords, private keys, or account credentials.