Avoylo

Avoylo Host Earnings & Payout Policy

Version: 0.1 Last Updated: September 28, 2026 Effective Date: [TBD BEFORE PUBLICATION]

This Host Earnings & Payout Policy defines how Host earnings are created, mature, become available, are grouped into payout batches, adjusted, and paid.

This Policy applies to the initial Avoylo pilot economics unless Avoylo publishes a later pricing or payout version or a more specific written agreement applies.

This Policy should be read together with the Avoylo Operations Policy, Host Services Policy, Seller Services Policy, Billing & Payment Policy, Claims & Incident Policy, Equipment & Rewards Policy, Privacy Policy, and applicable Terms of Service.

This Policy does not determine employment or independent-contractor status, does not guarantee any minimum earnings or Opportunity volume, and does not itself activate live payouts.

1. Core Principles

Avoylo Host earnings follow these principles:

  1. Authoritative operational events create earnings.
  2. Displayed estimates are not earned money.
  3. Every earning has a traceable source event.
  4. The underlying financial journal remains immutable or append-only.
  5. Retries do not create duplicate earnings.
  6. Host earnings mature before becoming payout-eligible.
  7. One earning may be included in only one successful payout.
  8. Corrections are auditable; paid history is not silently rewritten.
  9. Storage compensation belongs 100% to the Host under the current pilot.
  10. PAYOUTS_LIVE remains false until Avoylo intentionally activates a real payout provider and completes the required verification.

2. Currency

Unless Avoylo expressly supports another currency, Host earnings under the initial pilot are denominated in United States dollars (USD).

Avoylo must not silently combine earnings denominated in different currencies into one payout amount.

If additional currencies are supported later, they require separately defined payout and reconciliation rules.

3. Authoritative Earnings Ledger

The authoritative source for Host earnings is Avoylo's server-side financial record system.

A Host-facing balance, notification, dashboard estimate, email, or payout-provider screen does not replace the authoritative ledger.

Each earning must remain linked to the operational event and Accepted Terms that created it.

Where an earning must be corrected, Avoylo uses an auditable correction, compensation, reversal, or adjustment rather than silently editing the historical earning.

4. Pilot Host Earnings

Under the current pilot pricing policy:

Earning typeHost earning
Inbound handling$0.25 per Parcel
Outbound handling$1.00 per Parcel
Storage100% of the Seller's accepted storage charge

The Seller-facing pilot charges corresponding to the handling events are:

The internal Avoylo allocations are:

These amounts belong to the applicable pilot pricing version and must not silently rewrite historical Accepted Terms.

5. Opportunity Estimates Are Not Earnings

Amounts displayed on a Host Opportunity are estimates or applicable terms for the proposed Placement.

The Host does not earn money merely by:

An earning exists only after the authoritative operational event that creates it has occurred and Avoylo records the corresponding financial entry.

6. Accepted Terms

When a Host validly accepts an Opportunity and Avoylo commits the Placement, Avoylo records or may record the applicable Accepted Terms.

These may include:

Later changes to general pricing do not retroactively alter the Host's historical Accepted Terms for an already committed Placement.

7. Inbound Earning Event

The pilot inbound Host earning is:

$0.25 per Parcel

The earning is created once when the commercially accepted Parcel completes the required Host receipt workflow and reaches its first authoritative STORED event for that inbound Placement.

No inbound earning is created merely because:

8. No Duplicate Inbound Earning

The same inbound event must not generate duplicate Host earnings because of:

A safely retried inbound action returns or reconciles the original financial result.

9. Outbound Earning Event

The pilot outbound Host earning is:

$1.00 per Parcel

The normal outbound earning is created once when the assigned Parcel successfully completes Avoylo's required Host-side outbound workflow and reaches authoritative HANDOFF_READY.

The work ordinarily includes:

This is one earning event.

10. No Duplicate Outbound Earning for Retries

A Host does not earn another $1.00 merely because the Host:

A retry of the same outbound task does not create a new normal outbound earning.

11. Failed Pickup

If the Host correctly completes the outbound work and the Parcel reaches HANDOFF_READY, a later missed carrier pickup does not erase the already completed normal outbound earning.

It also does not create another normal outbound earning merely because the Host must secure or re-stage the same Parcel.

Any extraordinary additional paid service must be separately defined and authorized before it creates another Host earning.

12. Storage Earning

Under the current pilot:

Seller storage charge = Host storage earning

and:

Avoylo storage allocation = $0

Avoylo does not take a hidden percentage or undisclosed margin from the accepted storage charge under this pricing version.

13. Storage Earning Calculation

Storage earnings use:

The economic formula is:

Parcel volume in cubic feet × accepted USD per cubic foot per day × elapsed storage seconds ÷ 86,400

Avoylo maintains high-precision source accounting.

Display rounding does not replace the underlying high-precision earning record.

14. Storage Start

Storage earning begins at the authoritative STORED timestamp.

It does not begin at:

15. Weekly Storage Earning Segments

Long-lived storage is divided into deterministic UTC segments so Hosts do not need to wait until final Parcel exit for all storage earnings to exist.

The weekly boundary is:

Monday 00:00:00 UTC

Rules:

Each successfully closed storage segment creates the corresponding immutable Seller charge and equal Host earning.

16. Normal Outbound Storage Exit

For ordinary customer fulfillment, Host storage earning stops at the authoritative CARRIER_ACCEPTED provider occurrence time.

Storage does not stop at:

If the carrier event reaches Avoylo later, the trustworthy provider occurrence time controls.

17. Transfer Storage Exit

For an authorized Host-to-Host transfer:

A transfer request, transfer label, or staging event does not stop source Host storage earning.

18. Seller Removal or Return-to-Seller Storage Exit

For an authorized Seller removal or return:

Missing or ambiguous exit evidence does not create an invented earlier exit time.

19. Customer Return Entering Avoylo

A customer return creates a new Host storage lifecycle only after:

  1. the return is authorized for an Avoylo-managed destination;
  2. the Parcel arrives;
  3. the required receipt workflow succeeds; and
  4. the Parcel becomes authoritatively STORED.

A return shipment in transit does not create Host storage earning.

20. Earning Event Time

Every Host earning has an authoritative earning-event timestamp.

Examples:

The earning-event timestamp controls maturation.

A later database job, batch process, or UI refresh does not restart the maturation period.

21. Seven-Day Maturation

Each Host earning matures for 7 full calendar days after its authoritative earning-event timestamp.

For implementation clarity:

available_at = authoritative earning event time + 7 × 24 hours

Avoylo uses UTC timestamps for this calculation.

An earning created at 14:30 UTC becomes eligible for AVAILABLE status at 14:30 UTC seven days later, assuming no applicable hold, correction, reversal, or other blocking condition exists.

22. Why Earnings Mature Before Payout

The maturation period allows time for:

Maturation does not allow Avoylo to silently rewrite an earning.

Any correction remains auditable.

23. Earnings State Model

Host earnings may be represented through the following functional states or their system equivalents:

PENDINGMATURATION → AVAILABLE → INCLUDEDIN_PAYOUT → PAID

Additional exception states may include:

The state model must not erase the underlying immutable earning event.

24. PENDING_MATURATION

An earning is PENDING_MATURATION after the authoritative earning event is recorded but before its seven-day maturation period has completed.

Pending earnings:

25. AVAILABLE

An earning becomes AVAILABLE when:

AVAILABLE means payout-eligible under Avoylo's accounting rules.

It does not mean the banking or payout provider has already transferred money.

26. INCLUDEDINPAYOUT

When Avoylo creates a payout batch, the eligible earnings assigned to that batch become INCLUDED_IN_PAYOUT or an equivalent auditable state.

The same earning must not be included in two active or successful payout batches.

A payout batch must reference the immutable earning entries it contains.

27. PAID

An earning becomes PAID only after Avoylo has sufficient authoritative evidence that the corresponding payout was successfully completed under the enabled payout provider or approved payout process.

A browser message or operator assumption alone does not create PAID.

Avoylo must preserve the payout reference and audit history where available.

28. HELD

A specific earning or payout may be placed on HELD where a real unresolved condition materially affects whether it should be paid.

Examples may include:

A hold must not silently delete the earning.

The hold should preserve:

29. No Arbitrary Blanket Hold

Avoylo should scope a hold as narrowly as reasonably possible.

An issue involving one Parcel does not automatically require every unrelated Host earning to be frozen unless a broader account-level risk genuinely justifies it.

Any broader suspension or payout hold is governed by the applicable Host agreement and law.

30. FAILED

A payout may become FAILED where an attempted provider transfer fails or cannot be completed.

Failure may result from:

A failed payout does not destroy the underlying Host earnings.

The eligible balance remains subject to a supported retry, correction, or destination-update workflow.

31. Weekly Payout Cycle

The pilot Host payout cycle is weekly.

The weekly eligibility cutoff is:

Monday 00:00:00 UTC

Earnings that are AVAILABLE by the cutoff may be considered for that week's payout batch.

Earnings that become AVAILABLE after the cutoff roll forward to the next weekly payout cycle.

This cutoff is an accounting boundary. Actual provider arrival time may depend on the payout rail, banking system, weekends, holidays, destination account, and provider processing.

32. Payout Initiation Window

When live payouts are eventually activated, Avoylo's pilot operating target is to initiate the weekly payout batch within 2 business days after the Monday 00:00 UTC cutoff.

This is an initiation target, not a guarantee that the Host's bank or payout account will receive funds within two business days.

Before PAYOUTS_LIVE is intentionally enabled, no live payout promise is active merely because this Policy defines the intended pilot cycle.

33. Ordinary Minimum Payout Threshold

The ordinary pilot minimum payout threshold is:

USD $10.00 of net AVAILABLE Host earnings

If the Host's eligible available balance is below $10 at the weekly cutoff, the balance rolls forward.

No earning is forfeited merely because the threshold has not yet been reached.

34. Exact Threshold Boundary

A net eligible available balance of exactly:

$10.00

meets the ordinary payout threshold.

The threshold test is applied after applicable matured financial corrections and eligible adjustments are reflected.

35. Sub-Threshold Roll-Forward

If the Host has less than $10 of net eligible AVAILABLE earnings:

The roll-forward does not restart the maturation period.

36. Account Wind-Down Exception

When a Host completes a legitimate account wind-down and no unresolved operational or payout condition remains, Avoylo may include an otherwise eligible sub-$10 balance in a final payout.

This avoids indefinitely trapping a small eligible balance solely because the Host will no longer receive future Opportunities.

The payout provider may still impose a technical minimum that Avoylo must follow.

37. Payout Batch

A payout batch or payout statement should record at minimum:

The batch must be auditable.

38. One Earning, One Successful Payout

One immutable Host earning may be included in at most one successful payout.

The same earning must not be paid twice because of:

Avoylo must use idempotency, durable payout-attempt records, provider reconciliation, or equivalent controls before live payouts are enabled.

39. Payout Batch Replay

Re-running payout-batch creation for the same Host and cutoff must not silently create a second independent batch containing the same earnings.

A safe replay should:

40. Compensation Before Payout

If an auditable correction or compensation is posted before the affected earning is included in a successful payout, Avoylo calculates the eligible net amount using the source earning and applicable correction.

The original earning is not deleted.

The correction remains linked and auditable.

41. Correction After Payout

If a valid financial correction is discovered after an earning has already been paid, Avoylo must not silently rewrite the historical payout.

Instead, Avoylo records a new adjustment.

Where the adjustment reduces the Host's future balance, the negative amount may be carried forward against later eligible earnings as permitted by the applicable agreement and law.

Avoylo must not represent a historical paid amount as if it never occurred.

42. Negative Available Balance

A post-payment correction may cause the Host's net payout-accounting balance to become negative.

A negative balance:

If no future earnings are expected, recovery is governed by the applicable Host agreement and law.

43. No Silent Clawback

Avoylo does not silently remove money from a previously completed payout record.

Any recovery after payment must occur through an auditable adjustment, authorized provider reversal where legally and contractually available, voluntary repayment, setoff permitted by the applicable agreement, or another lawful process.

44. Host Disputes About Earnings

A Host that believes an earning is missing or incorrect should use Avoylo's designated earnings-support or dispute process.

The Host should identify the affected:

Avoylo may review authoritative operational and financial evidence.

Submitting a dispute does not create a new earning by itself.

45. Earnings Corrections

If Avoylo verifies an earnings error, the correction must be auditable.

Examples include:

The correction must preserve the original event where reasonably practical.

46. No Earnings for Fabricated Activity

A Host is not entitled to an earning created through intentionally fabricated or manipulated activity.

Examples include:

Any correction or restriction must remain auditable and follow the applicable agreements.

47. Incident Does Not Automatically Cancel Earnings

An operational Incident does not automatically erase Host earnings.

Avoylo must determine whether the Incident actually requires:

Incident creation alone is not a financial reversal.

48. Seller Billing Dispute Does Not Automatically Cancel Host Earnings

A Seller billing dispute does not automatically delete or reverse a Host earning.

The Seller charge and Host earning are linked through authoritative financial events, but a correction must be separately established and recorded.

49. Storage Earnings and Seller Payment Timing

A Host earning is not dependent on whether the Seller has already paid the corresponding billing statement unless a specific later policy expressly makes that dependency part of the payout program.

Under the current pilot accounting design:

Avoylo may later adopt risk controls for unpaid Seller balances prospectively, but must not silently apply an undisclosed rule to historical earnings.

50. No Direct Seller-to-Host Payment

A Host must not demand or accept direct payment from a Seller for ordinary Avoylo storage or handling in order to bypass Avoylo's financial system.

Seller charges are collected through Avoylo's billing process.

Host compensation is recorded through Avoylo's Host earnings and payout process.

51. Payout Method

Before live payouts are activated, Avoylo may require the Host to provide or connect an eligible payout destination.

The specific initial payout provider remains an implementation and operational activation decision until Avoylo completes the applicable provider verification and live-payout approval.

A Host must not rely on a displayed provider placeholder as a guarantee that the provider will be available in the Host's jurisdiction.

52. Payout Destination Ownership

The Host must provide a payout destination that the Host is legally authorized to use.

Avoylo may require identity, name, business, tax, or provider verification before enabling payout.

A Host must not intentionally route payouts through an account belonging to an unrelated person in order to evade verification, tax reporting, sanctions controls, account restrictions, or another applicable requirement.

53. Failed Payout Destination

If a payout fails because the Host's payout destination is invalid, closed, restricted, unsupported, or otherwise unusable:

Avoylo does not create a second earning merely because payout transmission failed.

54. Payout Provider Fees

Avoylo will disclose any Host-facing payout fee before applying it.

Under the current policy version, no specific Host payout-provider fee is fixed because the live payout rail has not yet been activated.

Avoylo must not invent or silently deduct an undisclosed provider fee.

55. Currency Conversion

The initial pilot earnings ledger is USD.

If a payout provider later converts USD into another currency for the Host, the conversion rate, provider fee, and settlement currency may depend on the enabled provider.

Avoylo will disclose the applicable payout-currency treatment before live activation.

This Policy does not promise a particular foreign-exchange rate.

56. Taxes

Host earnings may be taxable.

The Host is responsible for the Host's own tax obligations except for withholding, information reporting, or remittance obligations that applicable law expressly places on Avoylo or another payer.

Avoylo may require:

57. U.S. Tax Information

For U.S. payout relationships, Avoylo may request tax documentation such as Form W-9 or another applicable form and may issue or file information reporting where required by law.

The actual form and reporting obligation depend on the legal relationship, payment type, amount, and then-current tax rules.

This Policy does not itself determine whether a Host is an employee, independent contractor, business entity, or another legal classification.

58. Tax Hold

If Avoylo is legally required to obtain valid tax information before payout, Avoylo may hold otherwise available earnings until the required information is provided or the legal issue is resolved.

The earning remains recorded.

A tax-information hold must not silently erase Host compensation.

59. Identity and Compliance Hold

Avoylo may temporarily hold payout where reasonably necessary to resolve a material identity, sanctions, fraud, legal, or payout-provider compliance issue.

The hold should be documented and scoped as narrowly as reasonably practical.

Avoylo does not promise that every compliance issue can be resolved immediately.

60. Sanctions and Restricted Destinations

Avoylo will not knowingly transmit a payout where doing so would violate applicable sanctions, payment restrictions, or other law.

A Host may be required to provide additional information where needed to determine payout eligibility.

61. Account Suspension

Host account suspension does not automatically erase earned compensation.

Avoylo may place affected amounts on hold where permitted and reasonably necessary while resolving:

The financial history remains auditable.

62. Host Exit

A Host requesting exit must continue to satisfy existing custody obligations until inventory is resolved through the applicable Host exit workflow.

Host exit does not eliminate valid earnings.

After:

Avoylo may include an otherwise eligible sub-threshold balance in the final payout.

63. Host Death or Incapacity

If a Host dies or becomes unable to manage the account, Avoylo may require lawful documentation before releasing unpaid funds to an estate, representative, successor, or other legally authorized recipient.

No unrelated person is entitled to payout merely because they have access to the Host's device or property.

Physical inventory recovery and financial payout are handled as separate processes.

64. No Assignment of Earnings Without Approval

A Host must not assign, sell, transfer, or pledge an Avoylo payout balance to another person through an unsupported arrangement.

Any legally required assignment, court order, estate process, or business succession must use an authorized process.

65. Earnings Dashboard

The Host interface may display:

The interface must clearly distinguish an estimate from an authoritative earned amount.

66. Pending Versus Available Display

The Host dashboard should not combine PENDING_MATURATION and AVAILABLE into one unlabeled number that suggests all displayed earnings can immediately be paid.

The interface should clearly identify:

Pending and Available

as separate concepts.

67. Estimated Opportunity Earnings

Before acceptance, Avoylo may display an estimated earning for an Opportunity.

Such an estimate may depend on assumptions such as:

It is not guaranteed income.

Only authoritative completed earning events create ledger earnings.

68. No Guaranteed Monthly Income

Avoylo does not guarantee a Host:

Examples shown in marketing, onboarding, or educational material must be described as examples or estimates unless Avoylo has expressly guaranteed a specific amount in a binding agreement.

69. Equipment Rewards Are Separate From Cash Earnings

A label printer, supplies, discount, equipment subsidy, or other reward is not automatically part of the Host's cash payout balance.

Equipment and reward eligibility is governed by the Equipment & Rewards Policy.

An earned equipment reward must not silently reduce a Host's cash earnings unless the specific reward terms clearly disclose and authorize that treatment.

70. No Required Proprietary Hardware Purchase

Avoylo does not require a Host to purchase proprietary Avoylo hardware merely to receive ordinary Host earnings, unless a specific service level expressly requires compatible equipment and clearly states the requirement.

Where a compatible ordinary printer or device is sufficient, Avoylo may permit it.

71. Payout Security

Avoylo should protect payout changes as a high-risk account action.

Where supported, changing payout destination may require:

A payout-destination change must not silently redirect an already transmitted payout.

72. Compromised Account

If a Host reasonably believes the Host account or payout destination has been compromised, the Host should notify Avoylo promptly.

Avoylo may temporarily hold an untransmitted payout while verifying the destination.

A security hold does not erase the underlying Host earnings.

73. Provider Reconciliation

Once a live payout provider is implemented, Avoylo should reconcile:

Missing or contradictory provider evidence should create a reconciliation exception rather than a fabricated PAID state.

74. Lost Provider Response

If Avoylo sends a payout request but loses the provider response, Avoylo must not immediately create another independent payout.

Avoylo should first recover or query the existing provider attempt where technically supported.

The same payout batch must not be transmitted twice merely because of an ambiguous response.

75. Duplicate Payout

If Avoylo verifies that the same payout obligation was successfully transmitted more than once, the duplicate must be recorded as an exceptional financial event.

The duplicate is not a new Host earning.

Recovery or reconciliation must use an auditable lawful process.

76. Provider Reversal

If a payout provider later reverses, returns, or rejects a previously transmitted payout, Avoylo records the provider reversal or failure separately.

The original earning history remains intact.

A returned provider transfer may become eligible for retry after the underlying issue is resolved.

77. No Browser-Controlled Payout Amount

A Host browser or client application does not determine:

The server derives these values from authoritative records.

A manipulated client request cannot create additional payout entitlement.

78. Payout Audit Trail

Avoylo should preserve an auditable history of:

Where practical, history should be append-only rather than silently overwritten.

79. Privacy

Host payout records are private financial information.

Seller users do not receive unrestricted access to:

A Seller may see only the service pricing necessary for the Seller's own commercial relationship.

80. Live Activation Gate

No policy language in this document means that real payouts are currently active.

Before live Host payouts are enabled, Avoylo must separately verify at minimum:

Until that activation occurs:

PAYOUTS_LIVE=false

81. Policy Versioning

Avoylo may change prospective Host earnings or payout rules through a later policy or pricing version.

A later version must not silently rewrite:

Where legally required or contractually promised, Avoylo will provide appropriate notice before a material change becomes effective.

82. Related Policies and Contact

This Host Earnings & Payout Policy should be read together with:

Host Earnings Support: [TBD] Payout Support: [TBD] Tax Information Contact: [TBD] Legal Contact: [TBD] Company Legal Name: [TBD] Business Address: [TBD]