Skip to main content
Toku tracks your Papaya payroll calendar so the Toku deduction is always delivered to the right payroll cycle — and so on-chain delivery lines up with each country’s pay date.

​
Data Feed

Payroll calendar and cycle data is exchanged through Papaya’s Integration Center, using the feed provisioned for the Toku connection. Papaya also sends webhook notifications for cycle events, so Toku learns immediately when a cycle is finalized instead of waiting for the next scheduled sync. A trimmed example of the payroll cycle record in the Toku ↔ Papaya data contract:
Once a cycle is finalized, Toku receives the corresponding gross-to-net (G2N) report data — including per-worker gross and net amounts — through the same feed. See docs.papayaglobal.com for Papaya’s public developer documentation; your feed configuration is confirmed during implementation.

​
What Toku Reads

​
Sync Behavior

  • Upcoming payroll cycles appear in the Toku dashboard as soon as they exist on the Papaya payroll calendar.
  • While a cycle is open, Toku delivers the Toku deduction as payroll input ahead of the cutoff.
  • When a cycle is finalized, a webhook notification triggers reconciliation: Toku checks the G2N report against the applied deductions and releases the corresponding stablecoin payments.
  • Off-cycle runs are detected and skipped by default (configurable during onboarding).
Payroll sync is read-only. Toku never opens, calculates, or approves payroll cycles in Papaya — your team and Papaya’s in-country partners (ICPs) keep full control of running payroll.

​
Next

The Toku Deduction

How the deduction is delivered as payroll input

Authentication

Credentials, token exchange, and environments