RevLauncher Fees and Payments Schedule

1. Scope and definitions

This Schedule forms part of the Developer Terms and Content Creator Terms with EggBit Games LLC, the Iowa company operating RevLauncher. It describes the amounts retained by RevLauncher and the calculation, adjustment and payment of developer and creator earnings. It does not reduce customer rights under the Refund and Replacement Policy or applicable law.

All fees, ledger earnings and minimums below are in US dollars (USD). A business day is Monday through Friday, excluding US federal holidays. Calendar-day periods include weekends and holidays, subject to extensions required by law.

The Sale Base is the amount paid for the affected game keys after discounts and before customer sales tax, VAT or GST. The Platform Fee consists of a flat 15% component and a single $0.30 fixed component per checkout. Post-Fee Revenue is the Sale Base less the Platform Fee. Earnings are the developer or creator amounts allocated from Post-Fee Revenue, subject to the adjustments and payout conditions below.

2. Platform Fee

The Platform Fee is 15% of the Sale Base plus $0.30 once per checkout, irrespective of key quantity. There are no revenue tiers, lifetime thresholds or annual resets under this Schedule. Historical transactions governed by earlier schedules retain their original recorded economics; this revision does not reprice them or erase their history.

The percentage component is calculated on the affected keys using their discounted prices. RevLauncher locks the fee schedule, prices, attribution and revenue split when it creates the checkout reservation, through that reservation’s stated expiration. Payment retries within that reservation retain its economics. A new reservation receives a new calculation under its applicable schedule. No Platform Fee is earned for an unpaid or failed checkout.

The Platform Fee is earned when payment succeeds, subject to reversal for the refunded or disputed portion under section 6. RevLauncher funds the return of its percentage fee and the affected allocation of the once-per-checkout $0.30. These amounts are not charged back to the developer or creator as a retained-fee liability and do not reduce the customer’s applicable refund.

Amounts are rounded to USD cents, with midpoint rounding away from zero. The percentage component is accumulated across the applicable keys before rounding. Creator or additional platform allocations are rounded next, and the developer receives the remaining cents so the distribution balances. For a partial reversal, the original order fee, including the fixed component, is allocated to lines by discounted Sale Base, with any rounding residual assigned deterministically and recorded. Total allocations cannot exceed the fee originally charged. The $0.30 is never charged again for a replacement, refund review or retry of the same reserved transaction.

3. Creator share and additional platform allocation

When a valid creator code attributes the purchase, that creator receives the higher of 5% or the applicable published/accepted creator rate, calculated on Post-Fee Revenue. A higher accepted rate replaces the 5% floor; it is not added to it. The developer receives the remainder. The recorded agreement and transaction snapshot identify the applicable rate.

When no creator is attributed, RevLauncher instead retains an Additional Platform Allocation equal to 5% of Post-Fee Revenue, and the developer receives the remaining 95%. This amount belongs to EggBit Games LLC. We intend to use it for purposes including giveaways and covering fees but may use it for other business purposes. It is not owed to an unidentified creator, a customer escrow, a promise of a giveaway, or a refundable developer deposit. It is tracked separately from the Platform Fee for transparency.

Like the Platform Fee, the Additional Platform Allocation is reversed for the refunded or disputed portion of a sale. RevLauncher funds the return of this allocation; it is not charged again to a developer or creator. Previously attributed but unpaid creator earnings remain owed to the identified recipient subject to this Schedule; they do not become an Additional Platform Allocation because the recipient has not requested a payout.

4. Examples

Examples exclude customer tax and payout currency conversion.

Allocation	$20 sale, creator rate 20%	$20 sale, no creator
Sale Base	$20.00	$20.00
Platform Fee (15% + $0.30)	$3.30	$3.30
Post-Fee Revenue	$16.70	$16.70
Creator earnings	$3.34	$0.00
Additional Platform Allocation	$0.00	$0.84
Developer earnings	$13.36	$15.86

Two $20 keys in one checkout have a total Platform Fee of $6.30, not $6.60. If one of those equally priced keys is refunded, its original allocated Platform Fee is $3.15, including $0.15 of the checkout’s fixed component. Refunding both keys, together or in successive partial refunds, returns a total Platform Fee of $6.30, never two new $0.30 charges.

5. Included costs and permitted exceptions

RevLauncher absorbs ordinary customer payment-processing costs, Stripe Connect fees, standard payout charges and cross-border transfer charges within its commercial fees. They are not deducted a second time from ordinary developer or creator earnings. RevLauncher also bears original payment-processing costs that the provider does not return after a refund or dispute; it does not add a separate customer processing surcharge. The $0.30 component is a fixed part of RevLauncher’s fee, not a statement of Stripe’s actual charge for that transaction. An internal estimate of processing cost does not create an additional recipient charge.

Recipients bear actual provider charges for converting their payout into local currency and charges imposed by their recipient or intermediary bank. RevLauncher adds no markup to these charges. Required tax withholding and the actual dispute costs allocated in section 6 are separate permitted deductions. No internal refund-handling or administration fee is imposed.

6. Refunds, disputes and loss allocation

Every refunded or disputed sale can reverse the developer’s and creator’s original earnings and RevLauncher’s Platform Fee and Additional Platform Allocation for the affected portion, including after payout and even when a participant did not cause the problem. For an open dispute, a deduction may be provisional. A 60-day payout hold is not a promise that a payment cannot later be disputed. The customer’s remedy is not conditional on collecting from a participant first.

RevLauncher returns its original fee/allocation and absorbs original payment-processing costs as described above. The following allocation governs any remaining unrecovered creator earnings and actual dispute fees, rather than charging the customer refund or its components twice:

Reason	Unrecovered creator earnings	Actual attributable dispute fees
Invalid key, inaccurate listing, or developer failure to meet its product/support obligations	Developer fallback	Developer
Ordinary approved refund or dispute, including eligible change of mind, without a more specific cause below	Developer fallback	Allocated by documented cause; no automatic developer charge merely because a dispute exists
Additional discretionary goodwill authorized by the developer	Developer fallback	Developer only to the extent attributable to its authorized remedy or its own failure
Ordinary stolen-card fraud without participant complicity	Developer fallback	RevLauncher
Error by RevLauncher	RevLauncher	RevLauncher
Proven creator-caused fraud, without developer participation	Creator remains responsible; RevLauncher funds the unrecovered shortfall	Creator is responsible for documented fraud-caused losses; RevLauncher bears unrecovered amounts
Additional discretionary goodwill authorized by RevLauncher on its own account	RevLauncher	RevLauncher

Developer fallback means liability only for the portion of the creator’s reversed original earnings that remains unrecovered after documented recovery efforts and review, subject to section 7’s itemized notice and challenge process. It is separate from reversal of the developer’s own earnings. An unsuccessful transfer reversal alone does not establish that all recovery routes have been exhausted. The review must identify recoveries already made, outstanding recovery attempts, the reason for fallback and the remaining amount before assigning it to the developer.

Creator-caused fraud requires evidence of the creator’s knowing participation, such as manufacturing attributed purchases with stolen payment details or coordinating knowingly false chargeback claims. An unrelated fraudulent buyer’s use of a creator code, a genuine customer complaint, a refund or a lost dispute alone does not establish creator misconduct. A developer that knowingly participates in fraud is not protected by the innocent-developer exception; responsibility for its conduct remains subject to the role terms, applicable law and no duplicate recovery. Pending investigation may justify a documented risk hold but is not a final finding of fraud or an automatic cost assignment.

RevLauncher records the reason, responsible party, affected lines, original allocations, amounts recovered and actual third-party costs. Platform approval of an ordinary change-of-mind or invalid-key refund does not change its classification to platform-funded goodwill. A developer’s timely authorization of goodwill is recorded before additional costs are assigned to that developer. Unclear or mixed causes require review and itemization rather than automatically charging a participant. No fixed dispute penalty or hypothetical provider fee is imposed.

The original earnings reversal is not charged twice: restoring funds already collected by a Stripe transfer reversal, bank recovery, internal offset or repayment must reduce the same obligation. Any actual third-party refund of processor/dispute costs is also credited. RevLauncher does not charge a hypothetical fee, an internal administration cost, or both a full gross refund and an additional duplicate reversal of its components.

Funding a creator shortfall, whether by the developer or RevLauncher, does not release the creator’s obligation to repay its reversed earnings. If a developer has already covered an amount and the creator later repays or provider recovery succeeds, that recovery is credited to the developer to the extent it covered the same amount. Recovery from the creator before a developer pays reduces the developer’s outstanding fallback obligation instead. Any remaining valid debt is reconciled so the same shortfall is not collected twice. Developer insolvency or nonpayment does not delay a customer remedy; RevLauncher remains responsible for its merchant-of-record obligations while valid participant debts remain subject to recovery. Separate claims for intentional misconduct or other breaches remain subject to law and the role terms, without duplicate recovery or shifting the agreed allocation to an innocent participant.

For the attributed $20 example, a full refund reverses $13.36 of developer earnings, $3.34 of creator earnings and $3.30 of RevLauncher’s Platform Fee. If an ordinary approved refund leaves the entire $3.34 creator amount unrecovered after the documented process, the developer covers that $3.34 in addition to returning its own $13.36. If instead RevLauncher’s error or proven creator fraud caused that shortfall and the developer was uninvolved, RevLauncher covers the unrecovered $3.34. The creator remains liable for its reversed earnings in each case. Original processing costs remain with RevLauncher, and actual dispute fees follow the table. For the unattributed example, RevLauncher returns its $3.30 fee and $0.84 additional allocation and the developer returns $15.86; neither platform component is added to developer liability. Customer tax is refunded and reconciled separately as required.

Partial refunds use the original affected-line amounts and fee allocation, not current prices, rates or schedules. Cumulative partial adjustments cannot exceed the original component amounts. A replacement without a refund creates no new sale, creator commission or Platform Fee.

7. Recovery, challenges and recovered disputes

RevLauncher may withhold disputed amounts, reverse related earnings and offset amounts owed against the same recipient’s balances, reserves, pending funds or future earnings. Future earnings first reduce a negative balance. Payouts cannot be requested against a negative payable balance. This authority does not authorize offsetting an unrelated person’s or organization’s money.

We provide an itemized notice of a deduction and the basis for it. You have 90 calendar days after that notice to repay a remaining amount or challenge the deduction through support@eggbitgames.com. A timely challenge receives review and a reasoned response; contested collection is handled in light of that review and applicable law. The 90-day internal process does not shorten a mandatory legal claim period or waive rights that cannot be waived. It does not postpone necessary internal holds/offsets, payment-network deadlines, or Stripe’s separate recovery process. Corrected balances and all recoveries must be reconciled to prevent duplicate collection.

These terms do not themselves grant RevLauncher a new mandate to debit your external bank account. Stripe may recover negative connected-account balances under the Stripe agreements and authorizations you accept, including automatic external-account debits where permitted. The platform’s internal repayment/challenge window does not bind Stripe or guarantee that Stripe will wait 90 days.

When funds are actually recovered following a dispute, RevLauncher aims to credit the appropriate balances within five business days after confirming the recovery and transaction match. We restore the original allocations to the extent recovered and credit recovered third-party costs to whoever bore them; unrecovered costs and other valid amounts owed remain itemized. Developer-funded creator shortfalls are reconciled as described in section 6 before credits are issued. We do not begin a new ordinary 60-day hold solely because funds were recovered. Any unexpired original hold, specific risk hold, legal restriction or reconciliation exception can still apply, with notice as appropriate. Crediting a balance is distinct from completing a bank payout.

8. Eligibility, payout timing and reserves

New developer and creator earnings require an enabled payout country, completed identity/business/tax verification as applicable, and a supported and usable Stripe payout account. Permission to register or use non-earning features does not itself permit new earnings. The country list and provider readiness can change. If readiness is lost, new affected earnings activity is paused and existing entitlements remain recorded, subject to lawful holds and recovery. An ordinary transaction hold or minimum balance is a timing condition, not incomplete verification.

100% of both developer and creator earnings from each successful payment are held for 60 calendar days from that payment’s success. This per-sale rolling hold replaces the earlier proposed 30-day transaction hold; it does not add 60 days to it, run from key reveal/activation, or restart when another sale occurs. No additional ordinary post-transfer hold applies. The recipient organization must separately be at least 30 calendar days old. After both conditions and any other applicable checks are satisfied, the minimum ordinary payout request is $25 USD of eligible net earnings. Multiple eligible earnings can be combined. RevLauncher aims to review and initiate an eligible requested payout within five business days. Bank/provider settlement time is additional and any arrival date is an estimate.

High or irregular volume, unusual activity, elevated refund/dispute rates, fraud concerns, verification changes, insufficient source funds or legal/provider requirements may require an extended hold, reserve or manual verification. Holds must relate to a documented risk or restriction and identify the affected amount and release conditions. RevLauncher provides notice by email and in the dashboard, except details or timing that law or an active security investigation prevents us from disclosing.

Extended risk holds are reviewed at least every 30 calendar days, with status updates and release of amounts no longer reasonably needed for the stated risk. Provider/legal restrictions are tracked separately and may prevent release despite completion of our review. We do not impose a general permanent reserve repayable only when an account closes. A reserve is not a guarantee against later chargebacks. Provider holding limits and applicable law may require a different lawful resolution; this Schedule does not authorize indefinite retention contrary to them.

The platform balance, connected-account balance and bank payout are distinct stages, but transferring between balances is not treated as permission to restart or stack provider holding limits. The actual country, account and funds flow must support the proposed hold and payout process before it is offered. Participant earnings and customer taxes are not company-owned reserve capital. Any separately funded company reserve creates no additional deduction from participant earnings, customer surcharge or assurance that all losses are covered.

9. Currency and payment status

Earnings and requests are recorded in USD. Where the provider settles into a supported local currency, conversion occurs at the provider’s actual execution rate, rather than the rate when the sale occurred or when the request was submitted. The payout record identifies source amount, settled amount, currencies, actual rate and provider conversion charges available to us. Recipient/intermediary-bank charges may be visible only on the bank’s statement.

A failed payout, returned bank payment or later recovery may involve another conversion and a different rate. The recipient bears actual payout-conversion and bank charges/differences attributable to its payout, with itemized reconciliation; that does not override RevLauncher’s responsibility for its own error or authorize charging ordinary processing/Connect/cross-border transfer costs again. Customer refunds are processed in the original charge currency under the Refund Policy.

A request, transfer, pending provider status or dashboard estimate is not proof of a completed bank payout. RevLauncher reconciles provider confirmation, failures and returns, corrects errors and prevents duplicate payouts. Keep your bank and contact information current and report missing or misdirected payments promptly. We will investigate platform errors and do not treat a technical failure as forfeiture of earnings.

10. Taxes, closure and unclaimed earnings

EggBit Games LLC is the customer seller and merchant of record and is responsible for customer indirect-tax duties imposed on it by law. Developers and creators remain responsible for taxes and reporting imposed on their own income or supplies. Each party must provide required tax information and cooperate with lawful invoicing, reporting and withholding. Customer tax is not part of the Sale Base. Required withholding is separately identified and reported as applicable. Use of Stripe does not transfer every party’s tax duties to Stripe.

Declining new terms or closing an account stops new affected activity but does not accelerate held funds, eliminate valid debts or transfer earned balances to RevLauncher. We waive the ordinary $25 minimum for final settlement where a lawful, operational payout route is available. Cleared, undisputed amounts are processed promptly using the ordinary five-business-day initiation target once final instructions and verification are complete. Held amounts are released as their conditions are resolved; closure does not restart ordinary holds.

For death, incapacity or dissolution, we verify the lawful representative and payment entitlement. For failed verification, unsupported destinations, sanctions restrictions or nonresponse, we seek updated information and a lawful resolution, retain appropriate records, and follow applicable unclaimed-property/reporting/remittance requirements when they apply. We do not promise an alternative payment rail that has not been approved. An unanswered balance below $25 is not automatically forfeited or converted into an Additional Platform Allocation.

11. Limit on ordinary business-participation claims

11.1 Scope and amount

Subject to section 11.4 and only to the extent permitted by applicable law, EggBit Games LLC’s total liability to a contracting participant for Covered Claims assigned to one Liability Period is limited to the greater of $500 USD or the participant’s Qualifying Platform Fees for that period. Covered Claims are claims for monetary compensation for losses arising from our failure to perform our developer or creator service obligations under the role terms or this Schedule, excluding the matters in section 11.4. Describing the same covered failure under a different legal theory does not create another cap.

The contracting participant is the individual or legal entity that is party to the applicable developer or creator agreement, not each profile, organization record, game, key, order, employee or support ticket. An individual acting for a company does not receive a separate cap for the company’s claim. The same contracting participant’s developer and creator activity shares one cap. Separate legal entities are not treated as one participant merely because they have a common owner.

11.2 Qualifying Platform Fees

Qualifying Platform Fees are the Platform Fees earned under section 2 during the 12 calendar months immediately before the start of the Liability Period, determined from the applicable historical transaction records:

• For developer activity, count Platform Fees from sales for which that participant was the developer entitled to earnings, across its games.
• For creator activity, count Platform Fees generated by sales validly attributed to that participant as creator. The creator need not have paid those fees directly.
• If the same participant acts in both roles, combine the qualifying transactions without counting any fee or allocated fee component twice.

Count the percentage component and the applicable allocated share of the once-per-checkout $0.30 component, before deducting Stripe or other processing costs. For a checkout containing other participants’ lines, use the original proportional line allocation described in section 2; do not count the full fixed component for each line. Exclude customer taxes, participant earnings and the Additional Platform Allocation. Use original transaction economics, with corrections of proven recording or calculation errors; do not substitute current fee rates or retroactively reassign valid attribution to calculate the cap. Where the participant has less than 12 months of history, use only its actual history without annualizing or projecting fees. With no qualifying fees, the cap is $500.

Determine Qualifying Platform Fees net of Platform Fee reversals recorded before the Liability Period starts, including fee reversals associated with refunds and chargebacks. Use only the qualifying transactions in the preceding 12 calendar months, and subtract only the reversed fee components, not the refunded sale price, customer tax or participant earnings. A transaction’s qualifying fee cannot fall below zero or exceed its original applicable Platform Fee. Any corresponding fee reinstatement recorded before the period starts is included within those limits.

Once the Liability Period starts, later refunds, disputes, fee reversals and reinstatements do not change that period’s cap. Corrections of proven recording or calculation errors remain permitted; a later transaction event is not itself a recording error. The $500 minimum, shared-period rules and exclusions remain unchanged. This definition does not recalculate a cap for an incident governed by earlier terms.

11.3 Periods and shared limits

The first Liability Period starts with the earliest incident giving rise to a Covered Claim governed by this section and lasts 12 calendar months. Its cap is fixed using the preceding fee history described in section 11.2. All Covered Claims arising from incidents within that period share that cap, even if asserted, resolved or paid later. After a period ends, the next period starts with the next incident giving rise to a Covered Claim that is not assigned to an earlier period, using a new preceding 12-month fee calculation.

Claims arising from the same incident or a continuing or related series of incidents with a common underlying failure belong to the period containing the first such incident. Later effects, additional affected keys or later reporting do not create a new period for that series. Mere use of the same platform does not make otherwise unrelated incidents one series. Account closure and reopening, another profile for the same participant, or reacceptance of terms does not reset an existing period or create another cap for it. This section does not retrospectively limit an incident governed by earlier terms.

Amounts paid or payable to satisfy Covered Claims in a period count toward its shared cap; they are not multiplied by the number of claims or affected transactions. Amounts excluded under section 11.4 do not consume that cap. The cap is a ceiling on otherwise recoverable compensation, not an automatic payment or a minimum damages award, and it does not establish fault or loss. It creates no new fee, recipient deduction, payout hold or promise of a funded reserve.

11.4 Matters outside the cap

This section does not reduce or limit:

• Earned payouts or our payment, accounting, refund, reversal and loss-allocation obligations under sections 1–10, including correction of underpayments and the agreed responsibility for refund, dispute and unrecovered-creator costs.
• Required customer refunds, claims under the Customer Terms, or mandatory consumer rights that apply to an individual participant despite use of a developer or creator profile.
• Liability for our fraud, deliberate misconduct or gross negligence.
• Any liability, right or remedy that applicable law does not permit us to limit.

It does not cap a participant’s obligations to us under the role terms or this Schedule, change the third-party claims procedure, prevent a claim from being brought, or shorten a legal or payment-network deadline. It does not bind a regulator, payment provider or other person whose rights are not governed by this agreement. This is not a company-wide liability pool: each separate contracting participant has its own applicable cap, and payments for another participant’s claims do not reduce yours. Fees from the same sale can qualify for the separate developer’s and creator’s respective calculations; that overlap does not make their distinct caps one shared company-wide limit.

11.5 Examples

Qualifying Platform Fees	Shared cap for the Liability Period
$0	$500
$250	$500
$2,000	$2,000

If qualifying transactions generated $2,000 in Platform Fees and $400 of those fees had been reversed before the Liability Period started, the qualifying amount and shared cap are $1,600. If instead those $400 in fee reversals are first recorded after the period starts, that period’s cap remains $2,000. These figures concern the fee components, not the total value of the refunded purchases. The same $500 minimum applies when the net qualifying amount is below $500.

If an otherwise valid Covered Claim establishes $75 in recoverable compensation and the cap has not been used, a $500 cap does not increase that compensation to $500. Required earnings or refunds remain payable under their applicable rules in addition to any compensation subject to the cap.