Skip to main content
Toku keeps its roster in sync with Papaya Global so stablecoin elections always map to the right person — whether they’re an employee, an EOR worker, or a contractor. Sync is read-only and runs on a schedule agreed during implementation.

Data Feed

Papaya provisions the worker data feed for the Toku connection through its Integration Center — the in-platform hub Papaya uses to exchange HR and payroll data via pre-built APIs, file-based exchange, and custom API development. There is no public REST endpoint to call; the feed is configured per customer during onboarding. A trimmed example of the worker record in the Toku ↔ Papaya data contract:
Papaya’s public developer documentation lives at docs.papayaglobal.com; the exact feed configuration for your account is confirmed with Papaya’s integration support during implementation.

What Toku Reads

Sync Behavior

  • New workers appear in Toku automatically once they’re active in Papaya.
  • Updates (name, email, compensation, pay group) flow through on the next scheduled sync.
  • Inactive or offboarded workers are marked inactive and stop receiving stablecoin payments.
  • A manual sync can be triggered anytime from Settings → Payroll Integrations in Toku.
Worker sync never writes to Papaya. Toku does not modify worker records, compensation, or employment state — across all 160+ countries Papaya supports.

Next

Payroll Sync

How Toku tracks payroll cycles and G2N data

The Toku Deduction

How the deduction is delivered as payroll input