LuxHub DIALux freelancer payments: how are project earnings recorded?

What should a DIALux freelancer be able to verify about project payment?

A useful payment record should answer more than one question: what bounty was attached to the accepted project, whether any customer tip or approved adjustment was added, what QA and customer-acceptance stage has been reached, and whether settlement is pending or complete. LuxHub keeps those events attached to the private project instead of asking a freelancer to reconstruct them from emails and chat messages.

This is record visibility, not an income promise. Applying to LuxHub does not guarantee approval, projects, selection, earnings or immediate work, and a recorded bounty is not the same as money already settled. The purpose is to make the agreed exchange and its current state easier for an approved DIALux freelancer to inspect.

Start with the price route before accepting the project

An approved specialist can reach compatible work through a matched email alert or by browsing the private available-project board. The email is an entry point, not the whole experience. The project preview should be used to inspect the brief, supplied-material summary, required output, expected effort, deadline and applicable pricing route before any commitment is made.

For a Fixed Bounty project, an eligible freelancer may accept the displayed price after reviewing the project. For an Open Quote project, the freelancer may propose a price and proposed delivery time; that proposal is not an acceptance or an award. Not every project supports both routes, and the specialist remains free to decline unsuitable work.

Keep the original bounty and later changes in one record

Once a project is accepted, the recorded bounty should remain the baseline. A customer tip or a legitimate adjustment should appear as a separate approved event rather than silently replacing the original figure. That distinction helps the freelancer understand why the total changed and whether the change was requested, reviewed and accepted through the controlled project workflow.

An adjustment should never be assumed from an informal message. If the real project is materially different from the accepted brief, the freelancer should use the scope-report route and wait for a recorded decision. LuxHub oversight determines whether scope, bounty or deadline changes are justified; the freelancer should not rewrite accepted terms unilaterally.

USD records make worldwide projects comparable, not identical

LuxHub records Agent bounties and settlements in USD. A consistent record currency can make remote projects easier to compare for specialists working worldwide, particularly when customers and freelancers operate in different countries. It does not make the freelancer's final bank receipt identical to the displayed USD amount.

For an India-based freelancer, bank processing, supported payout methods, currency conversion, documentation, fees and local tax responsibilities may still affect the final outcome. Settlement timing also depends on QA approval, customer acceptance, payment operations and applicable requirements. LuxHub should therefore show the project record accurately without promising a payout date or a particular local-currency amount.

QA and settlement are related stages, not one status

A completed DIALux upload can still be awaiting technical review. The traceable record should distinguish production submission, QA outcome, customer acceptance and settlement status so that a freelancer can see which decision is actually pending. A file upload by itself should not be described as an approved payout.

This separation also creates a clearer escalation path. If a record appears inconsistent, the useful question is specific: which bounty or adjustment is affected, which QA or acceptance event is missing, and what settlement state is shown? Keeping that evidence with the project reduces ambiguity without exposing protected customer details or moving payment discussion into an unrecorded channel.

A quick decision check before you join

1. 01
   Confirm the pricing route

   Identify Fixed Bounty or Open Quote and read the complete private preview before accepting or proposing.

2. 02
   Record the accepted baseline

   Treat the accepted bounty, scope and deadline as the reference point for later project events.

3. 03
   Separate every approved change

   Check that tips and legitimate adjustments appear as their own recorded events instead of an unexplained new total.

4. 04
   Read USD as the record currency

   Allow for payout-provider processing, conversion, documentation, fees and local obligations outside the displayed project amount.

5. 05
   Distinguish QA from settlement

   A submitted file, an approved QA outcome, customer acceptance and settlement are separate stages.

6. 06
   Escalate with project evidence

   Reference the exact bounty, request and status inside the protected record rather than relying on private side messages.