Integrations · For payroll operations and IT

Add stablecoin payroll to ADP, Workday, Gusto or Rippling.

Toku adds USDC stablecoin payroll payouts to existing payroll workflows, with provider-specific setup, employee elections and reconciliation. Explore payroll APIs for stablecoin integration and how to add stablecoin payroll to ADP, Workday, Gusto or Rippling.

Book a Demo

Stablecoin-native payroll workflows designed for finance and payroll teams

Compliance-first controls and reporting readiness across 100+ countries

Global coverage for teams paying in fiat or stablecoins

ADP logo

ADP

How Toku Brings Stablecoin Payroll to ADP

Payroll & HR Management
BambooHR logo

BambooHR

How Toku Brings Stablecoin Payroll to BambooHR

Payroll & HR Management
Gusto logo

Gusto

How Toku Brings Stablecoin Payroll to Gusto

Payroll, HR & Benefits
NetSuite logo

NetSuite

How Toku Brings Stablecoin Payroll to NetSuite

ERP & Accounting
Paychex logo

Paychex

How Toku Brings Stablecoin Payroll to Paychex

Payroll & HR Management
QuickBooks logo

QuickBooks

How Toku Brings Stablecoin Payroll to Quickbooks

Accounting & Payroll
Ramp logo

Ramp

How Toku Brings Stablecoin Payroll to Ramp

Expense Management & Finance
Ripple logo

Ripple

The Future of Payroll Runs on XRPL

Stablecoin Payments
Rippling logo

Rippling

How Toku Brings Stablecoin Payroll to Rippling

HR, Payroll & IT Management
Workday logo

Workday

How Toku Brings Stablecoin Payroll to Workday

Payroll & HR Management
Xero logo

Xero

How Toku Brings Stablecoin Payroll to Xero

Payroll & HR Management

Customer story · Figure

An existing payroll system, connected to employee payouts.

Figure uses Toku for a live Workday-integrated payroll flow involving YLDS. The published case shows an existing enterprise payroll workflow connected to payroll payment infrastructure.

Read Figure’s story

For payroll operations and IT

Start with one payroll cycle.

Bring your current provider and configuration. Confirm the integration scope before choosing a first payment date.

Toku integration settings showing payroll and payment connections

  1. Map the current flow

    Identify the system of record, worker populations, payment methods, countries, payroll approvals, and finance reports. Confirm the provider product and configuration you use.

    First working document: a flow map with data and responsibility owners.

  2. Confirm the connection

    Review supported interfaces, access requirements, data exchange, funding, and payment status handling. Agree who owns tax calculations, filings, and reconciliation for your setup.

    Before implementation: a scoped integration plan and acceptance criteria.

  3. Validate a complete cycle

    Agree how to test approvals, payment outcomes, exception handling, and finance records before setting a production date.

    Before launch: an agreed test cycle and operational handover.

Read the documentationExplore a custom API integrationReview platform security

Rollout guide · Payroll, finance and IT

Add a payment route without replacing your payroll software.

Use this planning checklist to scope a settlement change with your implementation team. It is not a universal setup procedure or a guarantee of availability in every country.

  1. 1. Record what stays in place

    List your payroll product, countries, worker groups, pay calendar and current payment routes. Assign owners for gross-to-net calculations, tax filings, payslips and approvals. Changing settlement is not the same as replacing those responsibilities.

    Before moving on: A current-state flow and responsibility map, approved by payroll and finance.

  2. 2. Confirm the provider-specific connection

    Review the guide for your exact provider and product with the implementation team. Confirm data fields, access permissions, sync direction and the mechanism for payment instructions. Do not assume that one provider’s configuration applies to another.

    Before moving on: An agreed interface and access scope, including which system can write each record.

  3. 3. Agree the payment choices and costs

    Confirm country and worker eligibility, any required consent, available assets and networks, recipient details, funding deadlines and conversion terms. Identify payroll-service, payment, network and recipient fees separately. Confirm when the recipient can use the funds, not just when a network transfer settles.

    Before moving on: A written scope, fee schedule and communication plan for the selected workers.

  4. 4. Rehearse the full cycle

    Agree a test plan before moving real payroll. Cover worker changes, elections, approval, funding, payment status and reconciliation. Include rejected details, held payments and mismatched records. Compare expected amounts with payroll records and define who resolves each exception.

    Before moving on: Documented acceptance criteria and a test record reviewed by payroll, finance and IT.

  5. 5. Approve the first live cycle

    Choose a controlled first group and a launch date only after the agreed checks pass. Define a fallback payment process and decision deadline. Confirm payment status before retrying or using an alternative route so that a worker is not paid twice.

    Before moving on: A launch decision, named support contacts and an exception escalation path.

  6. 6. Reconcile before expanding

    Match payroll instructions, fees and payment references to the final records. Resolve differences and collect worker feedback before adding countries, assets or groups. Reconfirm scope whenever the provider configuration or payment route changes.

    Before moving on: A signed-off first-cycle reconciliation and a decision on the next rollout group.

Use a documented provider example

The Workday guide describes a dedicated integration user, worker sync and a Toku payroll deduction. Review its setup requirements separately from any other provider’s configuration.

Read the Workday implementation guide
Plan your integration rollout

All Toku Integrations

Stablecoin payroll FAQs

Keep the payroll provider as the system of record and review the supported integration with Toku. Map worker data, payroll approvals, employee USDC elections, funding and reconciliation before the first payout; confirm the provider-specific setup and responsibilities.
Toku offers a payroll API for embedding stablecoin payroll and payouts in an existing product. Review supported interfaces, USDC payout routes, approval controls, reporting and implementation requirements with Toku before launch.
Stablecoin payroll is the practice of compensating workers in dollar-pegged digital assets - such as USDC or USDT - using automated workflows that mirror how traditional payroll runs. Unlike ad-hoc crypto payments, stablecoin payroll includes proper approval chains, tax handling, and audit trails.
Yes, with the right platform. Toku supports split payments within a single payroll run, so a worker can receive a base salary in their local fiat currency and a stablecoin bonus in the same cycle. The two amounts are reconciled together in one record.
It can be - but compliance depends on the platform and jurisdiction, not the asset type. Stablecoin payroll is compliant when KYC/AML requirements are met, tax obligations are honored, and the platform maintains audit-ready records. Toku is built around these requirements, not retrofitted for them.
EOR becomes relevant when you need to hire a full-time employee in a country where your company has no legal entity. In that case, the EOR structure is necessary regardless of how the worker is paid. Some teams choose a combined EOR + stablecoin payroll setup; others use stablecoin payroll with existing entities or contractor relationships.

See Toku in action

Review your provider and payroll flow.

Bring your payroll provider, product configuration, worker locations, and payment requirements. Confirm fit and implementation scope with Toku.

Book a Demo