Home / Guides / Contractor payments

Payment processing guide

How AI training contractors get paid

The listing rate is only the beginning. Work may need to be tracked, submitted, reviewed, or approved before a platform releases a payout through its documented provider. Provider processing and bank settlement happen after that platform step.

Compare advertised rates Track applications locally

Advertised pay versus approved earnings

An hourly rate does not guarantee hours. Logged time can be excluded when it falls outside project rules or an approval window. Task and deliverable payments can depend on completion and review. Referral compensation is never treated here as applicant pay.

Evidence coverage: 3 documented, 2 partial, 1 not publicly documented.

The usual path from work to payment

STEP 1

Project terms

Confirm the rate or task amount, payable activity, time rules, approval path, and provider.

STEP 2

Track or submit work

Record time or deliverables using only the method required by the engagement.

STEP 3

Review and approval

The platform or client may review work before it becomes approved earnings.

STEP 4

Release and settlement

The platform releases funds; the provider and bank then complete their own processing.

Cross-platform payment comparison

This compares publicly documented payment processes, not the amount advertised by a listing. Expand a platform for full caveats and sources.

Platform	Model	Provider	Cadence	Evidence	Details
Mercor	hourly, deliverable, mixed	Stripe Connect, Wise	Mercor documents weekly Wednesday processing for hourly contractors, covering the preceding Saturday-to-Friday IST work week. Other payment types can use separate release windows.	Officially documented	Open notes
Handshake	hourly, project	Stripe	Handshake says it typically sends payouts to its payment partner by Wednesday afternoon for the preceding Monday-through-Sunday PST period.	Officially documented	Open notes
Micro1	unknown	Not documented	Not publicly documented; confirm during onboarding or in the current project agreement.	Not publicly documented	Open notes
Turing	project, mixed	Direct bank transfer, Deel for some engagements	Not publicly documented; confirm during onboarding or in the current project agreement.	Partially documented	Open notes
Alignerr	hourly, project, mixed	Stripe Connect, PayPal	Not publicly documented; confirm during onboarding or in the current project agreement.	Partially documented	Open notes
SME Careers	hourly, per task, mixed	Deel	SME Careers documents weekly payouts that bundle approved earnings and send them through Deel.	Officially documented	Open notes

Mercor

Officially documented

Payment model: hourly, deliverable, mixed
Provider: Stripe Connect, Wise
Payout cadence: Mercor documents weekly Wednesday processing for hourly contractors, covering the preceding Saturday-to-Friday IST work week. Other payment types can use separate release windows.
First-payout caveat: Payment setup is part of project onboarding. The first arrival can depend on completing the contract, provider setup, identity checks, bank details, and the next applicable release window.

Full notes and sources

Handshake

Officially documented

Payment model: hourly, project
Provider: Stripe
Payout cadence: Handshake says it typically sends payouts to its payment partner by Wednesday afternoon for the preceding Monday-through-Sunday PST period.
First-payout caveat: A first payout depends on completing the Handshake and Stripe setup, required identity and tax details, bank or payout method, and the next processing cycle.

Full notes and sources

Micro1

Not publicly documented

Payment model: unknown
Provider: Not publicly documented
Payout cadence: Not publicly documented; confirm during onboarding or in the current project agreement.
First-payout caveat: Micro1's public expert page describes onboarding before work, but it does not publish a complete first-payout sequence. Confirm the contract, provider, approval rules, and timing during onboarding.

Full notes and sources

Turing

Partially documented

Payment model: project, mixed
Provider: Direct bank transfer, Deel for some engagements
Payout cadence: Not publicly documented; confirm during onboarding or in the current project agreement.
First-payout caveat: Turing documents more than one contracting flow. Confirm whether the engagement uses the Turing payment workspace or Deel and complete the applicable contract before expecting payment.

Full notes and sources

Alignerr

Partially documented

Payment model: hourly, project, mixed
Provider: Stripe Connect, PayPal
Payout cadence: Not publicly documented; confirm during onboarding or in the current project agreement.
First-payout caveat: Approved applicants complete contract and billing setup. The provider can depend on location, and a project must exist before onboarding creates earnings.

Full notes and sources

SME Careers

Officially documented

Payment model: hourly, per task, mixed
Provider: Deel
Payout cadence: SME Careers documents weekly payouts that bundle approved earnings and send them through Deel.
First-payout caveat: A contractor needs an active Deel contract and verified identity before payment. First payment also depends on project placement, approved earnings, and the weekly payout cycle.

Full notes and sources

Mercor payment notesOfficially documented

Applicant pay basis: The controlling contract can be hourly or deliverable-based. A listing rate is not the final earnings record; the contract and approved work determine payment.
Work approval: Hourly payment depends on tracked and approved hours inside the documented pay period. Deliverable-based contracts use the deliverables and completion terms in the contract.
First payout: Payment setup is part of project onboarding. The first arrival can depend on completing the contract, provider setup, identity checks, bank details, and the next applicable release window.
Provider settlement: Mercor documents different arrival times for Stripe bank transfer, eligible Stripe Instant Payout, and Wise. A platform release is not the same moment as bank settlement.
Time or work tracking: Hourly projects can use Mercor's documented time-tracking process. Only time inside the relevant period and accepted under the project rules is considered for payout.
Invoice requirement: Mercor's public talent documentation describes earnings and payment processing but does not establish one contractor-created invoice rule for every contract.
Payout threshold: Not publicly documented; confirm during onboarding or in the current project agreement.
Currency notes: Mercor states that contracts are denominated in USD and that the assigned provider converts funds where local-currency settlement applies.
Country or provider limits: Mercor assigns Stripe Connect or Wise based on the supported country and bank account; provider features and payout speed can vary.
Identity and tax setup: Contract, identity, payment-account, and any required tax setup are onboarding steps. Follow the current official flow for the specific engagement.
Payment concern path: Check the Mercor earnings record and provider status first, then use Mercor support for missing or incorrect platform payment information.
Known unknowns: A universal payout threshold is not stated in the reviewed public documentation.

Official sources · reviewed 2026-07-19

View current Mercor opportunities

Handshake payment notesOfficially documented

Applicant pay basis: Handshake AI earnings depend on the applicable project terms and recorded work. An advertised rate does not guarantee hours or an approved payment amount.
Work approval: The public payment guide describes a prior weekly work period and payment processing after required onboarding and project participation steps.
First payout: A first payout depends on completing the Handshake and Stripe setup, required identity and tax details, bank or payout method, and the next processing cycle.
Provider settlement: Handshake says processing can often take about 48 hours after funds are sent to the payment partner before they appear for withdrawal.
Time or work tracking: Project work can require the Handshake AI time-tracking process. Use the current project instructions for which activity is payable.
Invoice requirement: Not publicly documented; confirm during onboarding or in the current project agreement.
Payout threshold: Not publicly documented; confirm during onboarding or in the current project agreement.
Currency notes: Not publicly documented; confirm during onboarding or in the current project agreement.
Country or provider limits: Stripe availability, supported payout methods, banking details, and tax onboarding can vary by contractor location.
Identity and tax setup: Handshake requires Stripe setup and documents identity and tax-detail steps for payment eligibility. This page does not tell an individual which form to submit.
Payment concern path: Review the Handshake payment tracker and Stripe payout method, then contact Handshake AI support when a documented payment remains missing or reversed.
Known unknowns: A universal invoice requirement is not stated in the reviewed public documentation. A universal payout threshold and currency-conversion policy are not stated.

Official sources · reviewed 2026-07-19

View current Handshake opportunities

Micro1 payment notesNot publicly documented

Applicant pay basis: Not publicly documented; confirm during onboarding or in the current project agreement.
Work approval: Not publicly documented; confirm during onboarding or in the current project agreement.
First payout: Micro1's public expert page describes onboarding before work, but it does not publish a complete first-payout sequence. Confirm the contract, provider, approval rules, and timing during onboarding.
Provider settlement: Not publicly documented; confirm during onboarding or in the current project agreement.
Time or work tracking: Not publicly documented; confirm during onboarding or in the current project agreement.
Invoice requirement: Not publicly documented; confirm during onboarding or in the current project agreement.
Payout threshold: Not publicly documented; confirm during onboarding or in the current project agreement.
Currency notes: Not publicly documented; confirm during onboarding or in the current project agreement.
Country or provider limits: Not publicly documented; confirm during onboarding or in the current project agreement.
Identity and tax setup: Not publicly documented; confirm during onboarding or in the current project agreement.
Payment concern path: Use Micro1's current official support or project contact. Do not send banking or identity information to an unofficial requester.
Known unknowns: Payment provider, payout cadence, approval timing, invoicing, threshold, settlement timing, currency handling, and universal tracking rules were not publicly documented in the reviewed pages.

Official sources · reviewed 2026-07-19

View current Micro1 opportunities

Turing payment notesPartially documented

Applicant pay basis: Compensation and payable work depend on the matched engagement and contract. Turing's public contract help does not establish one universal rate or approval rule.
Work approval: Not publicly documented; confirm during onboarding or in the current project agreement.
First payout: Turing documents more than one contracting flow. Confirm whether the engagement uses the Turing payment workspace or Deel and complete the applicable contract before expecting payment.
Provider settlement: For the direct Turing flow, payments are described as going to the contractor's bank. For the Deel flow, payment history and withdrawal handling are in Deel.
Time or work tracking: Not publicly documented; confirm during onboarding or in the current project agreement.
Invoice requirement: Turing says invoices are available through the developer portal in its direct flow. It does not state that every contractor must create and submit an invoice manually.
Payout threshold: Not publicly documented; confirm during onboarding or in the current project agreement.
Currency notes: Not publicly documented; confirm during onboarding or in the current project agreement.
Country or provider limits: The contracting and payout flow can vary by engagement and location; not every contractor uses Deel.
Identity and tax setup: Complete only the contract and payment setup requested in the official Turing or named Deel flow.
Payment concern path: Check the applicable Turing workspace or Deel payment history, then use Turing support for a missing contract or payment-path issue.
Known unknowns: A universal payout cadence, approval window, threshold, currency policy, and work-tracking rule are not stated in the reviewed public pages.

Official sources · reviewed 2026-07-19

View current Turing opportunities

Alignerr payment notesPartially documented

Applicant pay basis: Open roles can display hourly ranges, while actual paid work depends on a project, contract, approved activity, and the applicable billing setup.
Work approval: Alignerr's public FAQ discusses completed projects, performance, data quality, and payment concerns, but the reviewed pages do not publish one approval sequence for every project.
First payout: Approved applicants complete contract and billing setup. The provider can depend on location, and a project must exist before onboarding creates earnings.
Provider settlement: Not publicly documented; confirm during onboarding or in the current project agreement.
Time or work tracking: Not publicly documented; confirm during onboarding or in the current project agreement.
Invoice requirement: Not publicly documented; confirm during onboarding or in the current project agreement.
Payout threshold: Not publicly documented; confirm during onboarding or in the current project agreement.
Currency notes: Not publicly documented; confirm during onboarding or in the current project agreement.
Country or provider limits: Alignerr says payment details use Stripe Connect or PayPal depending on location. Project and country availability can vary.
Identity and tax setup: Alignerr's process includes identity verification, contract signup, and billing setup before paid project work.
Payment concern path: Use Alignerr's official support path for completed-project or payment concerns. Keep account and payment details inside verified official flows.
Known unknowns: A universal cadence, settlement time, tracking rule, invoice requirement, payout threshold, and currency-conversion policy are not stated in the reviewed public pages.

Official sources · reviewed 2026-07-19

View current Alignerr opportunities

SME Careers payment notesOfficially documented

Applicant pay basis: SME Careers documents project earnings based on approved hours and hourly rate, plus qualifying exam earnings. Referral earnings are separate and are not applicant pay.
Work approval: Earnings move through review statuses. Approved project and exam earnings are included in the applicable payout cycle.
First payout: A contractor needs an active Deel contract and verified identity before payment. First payment also depends on project placement, approved earnings, and the weekly payout cycle.
Provider settlement: After SME Careers marks a payout paid, Deel handles the transfer and the contractor's selected withdrawal method. Bank arrival is a separate provider step.
Time or work tracking: Project earnings can include approved on-platform and off-platform hours under documented project time categories and tracking rules.
Invoice requirement: The reviewed public workflow describes finance entries and weekly payouts rather than a universal contractor-created invoice requirement.
Payout threshold: Not publicly documented; confirm during onboarding or in the current project agreement.
Currency notes: Not publicly documented; confirm during onboarding or in the current project agreement.
Country or provider limits: Deel account, identity, contract, and withdrawal-method availability can depend on location.
Identity and tax setup: SME Careers requires Deel contracting and identity verification before paid work. Follow Deel and the current contract for any required tax setup.
Payment concern path: Check the SME Careers Finance page and payout status first. Once marked paid, check Deel; use official SME Careers support for missing or incorrect earnings approval.
Known unknowns: A universal payout threshold and currency-conversion policy are not stated in the reviewed public documentation.

Official sources · reviewed 2026-07-19

View current SME Careers opportunities

Provider setup and identity verification

A platform may require a contract, identity check, tax setup, and payout account before it can release money. Complete those steps only through the verified platform or the provider it names. Do not send identity or banking information to Specialist AI Work.

Hourly, task, and deliverable work

Hourly work can depend on accepted tracked time. Task work can depend on a completed unit and quality review. Deliverable work can depend on contract milestones. The model and approval rule in the current engagement control.

Approval and first-payout delays

Review queues, corrections, project cutoffs, incomplete onboarding, bank details, identity verification, and the next payout cycle can all delay a first payment. A platform processing date is not a bank-arrival promise.

Currency conversion and provider limitations

Supported currencies, conversion rates, fees, withdrawal methods, and settlement times can vary by provider, country, and bank. Confirm the current provider screen before accepting a conversion or withdrawal.

When payment appears late or incorrect

1. Check whether the work is submitted, pending review, approved, released, or already with the provider.
2. Compare the work date with the documented cutoff and payout cycle for that engagement.
3. Check the provider for a failed bank method, verification request, withdrawal step, or settlement status.
4. Contact official platform support with the project, non-sensitive status, work dates, and expected cycle.

Never pay a fee to unlock wages, send cryptocurrency, share a one-time code, or move a payment dispute to an unofficial chat. Specialist AI Work does not process payments and cannot resolve platform disputes.

Tax and contractor boundary

Tax and contractor obligations depend on the individual, country, and engagement. Use the platform's current onboarding instructions and seek qualified local advice when needed. This page does not decide which form you should submit, what you owe, your classification, treaty eligibility, or business-registration requirements.

Possible applicant journey

From first application to a possible first payment

These stages are not guaranteed or universal. A platform may reject an application, add steps, pause matching, or use different project and payment rules.

Stage 1 · Possible next stage
Understand the work
Learn the task families, evidence standards, and screening formats before choosing a role.
Stage 2 · Possible next stage
Choose suitable platforms
Compare current inventory, application paths, and platform-specific limitations.
Stage 3 · Possible next stage
Prepare the application
Connect real professional evidence to one current role without inventing experience.
Stage 4 · Possible next stage
Complete screening
Follow the rubric, use only permitted tools, and explain judgments from your own expertise.
Stage 5 · Possible next stage
Complete identity and payment setup
Use verified official domains for any identity, contract, tax, or payout-provider step.
Stage 6 · Possible next stage
Receive a project or task
Acceptance can lead to matching or more qualification; it does not guarantee immediate work.
Stage 7 · Possible next stage
Track and submit approved work
Follow the engagement rules for time, tasks, deliverables, review, and approval.
Stage 8 · Possible next stage
Receive the first payment
Separate platform approval and release timing from the provider's bank-settlement timing.

Payment-process FAQ

Does an advertised hourly rate guarantee earnings?

No. A rate does not guarantee hours, task availability, approval, project duration, or a final payable amount.

Why can a platform show paid while the bank has not received the money?

Platform approval and release are separate from provider processing, withdrawal, currency conversion, and bank settlement.

Can Specialist AI Work resolve a payment dispute?

No. Specialist AI Work does not process platform work or payments. Use the official platform and named payment provider.