Welcome to USD1payrolls.com

USD1payrolls.com is an educational page about using USD1 stablecoins (stablecoins, meaning digital tokens designed to keep a steady value, intended to be redeemable one-for-one for U.S. dollars) in payrolls (the process of calculating and paying wages, taxes, and benefits). The phrase USD1 stablecoins is used here in a generic, descriptive way to mean any dollar-redeemable stablecoin token. It is not a brand name, and nothing on this page should be read as an endorsement of any specific issuer, blockchain network, exchange, wallet provider, payroll vendor, or financial institution. This page is for general information only and is not legal, tax, or financial advice.

Stablecoin payrolls can be a practical idea in some situations and a poor fit in others. The goal of this guide is to explain the moving parts in plain English: how payrolls work, how a blockchain (a shared database that records transactions and is maintained by many computers) changes the mechanics of paying people, and what risks and compliance obligations often come along for the ride. Where relevant, the guide points to primary sources from regulators and standards bodies. For example, the U.S. Internal Revenue Service (the federal tax agency) has published guidance on how virtual currency is treated for tax purposes, including when it is paid as wages.^[1]

What this page covers

Payrolls touch law, finance, technology, and human expectations all at once. When you add USD1 stablecoins as a payment method, you are not only adding a new way to move money, you are also adding new operational and compliance questions.

This page focuses on:

What payrolls are really doing behind the scenes (gross pay, net pay, and recordkeeping).
Where USD1 stablecoins can help (and where they do not).
A realistic end-to-end payroll flow using USD1 stablecoins, without trading jargon.
Common legal and compliance themes, especially for cross-border teams.
Tax and accounting themes, including why valuation time stamps matter.
Security and operational controls that reduce mistakes and fraud.
The employee and contractor experience, including off-ramps (ways to convert to local currency).

Payroll basics, in plain English

Even if you never pay someone with USD1 stablecoins, payrolls are already a structured system with deadlines and legal constraints. A typical payroll cycle includes:

Gross pay (the total amount earned before deductions). Gross pay can include salary, hourly wages, overtime (extra pay required by law in many places for hours above a threshold), commissions, bonuses, and reimbursements.

Withholding (amounts taken out before net pay). Withholding can include payroll taxes (taxes tied to employment), income tax withholding, social insurance, and benefit deductions (health plans or retirement plans). The exact list depends on the worker type and the jurisdiction.

Net pay (what the worker actually receives). Net pay is the amount that arrives in the worker's hands after the required deductions.

Pay statements (also called pay slips, meaning a document that shows how gross pay turned into net pay). In many places, the pay statement is not optional. It is part of the worker's ability to verify that payrolls are correct.

Remittance (sending withheld taxes and other required amounts to the correct government agency or benefit provider). Remittance deadlines can be separate from the payday itself.

A key distinction is employee vs contractor classification. An employee (a worker under an employment relationship) often triggers withholding and employer-side taxes. A contractor (an independent service provider) is often paid gross with less withholding by the payer, but the contractor may be responsible for their own taxes. Misclassification (treating an employee like a contractor to avoid obligations) can carry serious penalties in many jurisdictions.

Adding USD1 stablecoins does not remove any of these steps. It changes the payment rail (the path money takes), but payroll still needs a clear way to calculate pay, handle deductions, produce records, and meet deadlines.

Another payroll concept that matters is the payroll cut-off (the deadline after which changes apply to the next pay cycle). With bank transfers, cut-offs are often driven by banking hours. With USD1 stablecoins, cut-offs are more about internal processing time, compliance checks, and the time needed for workers to convert funds if they rely on local currency.

Why some teams consider USD1 stablecoins for payrolls

Using USD1 stablecoins for payrolls is usually discussed for practical reasons, not because the underlying technology is exciting. A few common motivations:

Cross-border speed and availability. Many banking systems are not truly 24 hours a day. International wires can take days, especially across time zones and holidays. USD1 stablecoins can move on public blockchains at any hour, often with settlement visible within minutes. That can matter for contractors who invoice weekly or for teams that span multiple regions.

Transparency in settlement status. A blockchain transaction can be checked by both the payer and the recipient without calling a bank. This does not guarantee the payment was legally compliant, but it can reduce "Where is my transfer?" uncertainty.

Programmable controls. In some setups, a smart contract (a program that runs on a blockchain and can move tokens based on rules) can enforce multi-person approvals, spending limits, or delayed releases. Not every payroll should use smart contracts, but the ability to enforce policy in the payment layer is real.

Worker preference for dollar exposure. In some countries, workers prefer to hold value linked to U.S. dollars rather than a volatile local currency. USD1 stablecoins can provide that exposure while still being relatively easy to convert.

Interest in stablecoin payrolls often shows up in global teams where workers are paid across borders. That can include North America and Europe when hiring international contractors, and it can also include parts of Latin America, Africa, the Middle East, and Asia-Pacific where workers may prefer exposure to U.S. dollars or need a faster alternative to local banking rails. The underlying reason varies: local currency volatility, limited access to foreign currency accounts, or simply the friction of international bank transfers. These are real payroll problems, but they do not erase the need to comply with local wage and tax rules.

At the same time, there are strong reasons some employers avoid USD1 stablecoins payrolls:

Legal constraints on wage payment. Some jurisdictions require wages to be paid in local legal tender (official government-issued money) or require "cash or its equivalent" in ways that may not match stablecoin transfers. For example, U.S. federal wage rules discuss paying wages in cash or a negotiable instrument payable at face value.^[9] That does not automatically make USD1 stablecoins disallowed, but it is a reminder that payroll is regulated differently than business-to-business payments.

Operational risk. Bank transfers can be reversed or recalled in some circumstances. Blockchain transfers are generally not reversible. If payroll sends USD1 stablecoins to the wrong address, there may be no practical way to recover the funds.

Compliance overhead. Screening for sanctions (legal restrictions on dealing with certain people, entities, or locations) and managing anti-money laundering expectations can be more complex when payments are sent on public blockchains. The U.S. Treasury's Office of Foreign Assets Control (the U.S. sanctions authority) has published compliance guidance tailored to the virtual currency industry.^[4]

Financial risk that is not obvious. A stablecoin can still fail to hold its value. Reserves can be mismanaged, redemptions can be paused, or a blockchain can face congestion. The Financial Stability Board (an international body that coordinates financial stability work) emphasizes that so-called stablecoins may pose risks and require effective regulation and oversight.^[7]

The practical takeaway is that USD1 stablecoins can be a useful payroll tool in specific contexts, but they are not a universal upgrade.

How a USD1 stablecoins payroll flow can work

It helps to separate the payroll calculation from the payroll payment.

The calculation step answers: "How much is owed to each worker, after deductions, for this pay period?"
The payment step answers: "How do we deliver net pay to each worker on time, with an audit trail?"

A USD1 stablecoins payroll flow often looks like this, even when a company uses a payroll provider:

1) Decide where USD1 stablecoins fit in the payroll policy

Some organizations only use USD1 stablecoins for contractors. Others allow employees to receive a portion of net pay in USD1 stablecoins if local law permits and the employee opts in (agrees voluntarily). A common pattern is "local currency as the standard option, USD1 stablecoins as an optional alternative," which reduces legal and employee-relations risk.

Key policy details usually include:

Eligibility (which countries, which worker types).
Payment frequency (weekly, biweekly, monthly).
Opt-in and opt-out process (how a worker changes their preference).
Supported wallet types (custodial vs self-custody).
Limits (for example, a maximum percentage of net pay in USD1 stablecoins).

A custodial wallet (a wallet where a service provider holds the private keys) can be easier for some workers, but it introduces counterparty risk (risk that the provider fails or freezes funds). A self-custody wallet (a wallet where the worker controls the private keys) gives the worker control, but it increases the risk of loss if the private keys are misplaced.

2) Run payrolls as usual: compute gross, deductions, and net pay

Even if net pay will be delivered in USD1 stablecoins, payrolls still need a base currency for calculations and reporting. Many employers use local currency for employees and U.S. dollars for global contractors. The payroll system should keep a clear record of:

Pay period dates.
The worker's legal work location.
Gross components (salary, overtime, bonus).
Deductions and employer contributions (where applicable).
Net pay amount.

3) Set a valuation moment and a conversion method

If payroll calculates net pay in local currency but delivers USD1 stablecoins, you need a valuation moment (the exact time you lock in the conversion rate). This matters for fairness and for records.

A common approach is:

Lock an exchange rate at a defined time (for example, at payroll approval time).
Convert the net pay amount into an equivalent amount of USD1 stablecoins based on that rate.
Record the rate source and the time stamp in the payroll record.

Tax agencies may care about fair market value (a reasonable price in an open market) at the time of payment when wages are paid using virtual currency.^[1] Even if USD1 stablecoins aim to track the U.S. dollar, documentation is still useful.

4) Source USD1 stablecoins and prepare the sending wallet

Organizations commonly source USD1 stablecoins through:

A regulated exchange (a platform that lets you buy and sell digital assets, typically with identity checks).
A broker or over-the-counter desk (a service that sources liquidity directly, often for large amounts).
A treasury platform integrated with a payroll vendor.

Sourcing introduces compliance considerations. In the United States, FinCEN (the Financial Crimes Enforcement Network, a bureau of the U.S. Treasury) publishes guidance on when virtual currency business models may fall under money services business rules (rules for certain regulated payment and money transmission providers).^[3] A company paying its own workers is not automatically a regulated exchanger, but the lines can blur if the company also offers conversion services to others or operates as an intermediary.

5) Collect worker wallet addresses and verify them safely

A wallet address (a public identifier used to receive tokens) is not like a bank account number. Sending to the wrong address can be irreversible. Common controls include:

Asking for an address in a structured form (not via a chat message).
Verifying the format and network compatibility (for example, matching the blockchain network used).
Doing a small test transfer (a minimal payment used to confirm the address) before the first full payroll payment, when practical.
Using address books with approval workflows.

This is also where privacy shows up. Public blockchains can be transparent, meaning that an address can reveal transaction history. Some workers may not want their payroll activity publicly linkable to their identity.

6) Approve and broadcast payroll payments

To broadcast (send) a blockchain transaction, the payer uses a private key (a secret cryptographic key that authorizes spending). Strong controls usually include:

Multi-signature (a setup where multiple approvals are required to send funds).
Separation of duties (different people prepare, approve, and release payments).
Daily and per-transaction limits.
Logging (keeping records of who approved what and when).

Blockchain settlement depends on the network's rules. Transaction fees (sometimes called gas fees, meaning fees paid to process a transaction) can fluctuate. Congestion can slow processing. These details matter when payroll has a hard payday deadline.

NIST (a U.S. standards agency) provides a technical overview of blockchain concepts such as immutability (hard-to-change records) and distributed consensus (agreement among many computers).^[8] You do not need to be an engineer to run payrolls, but it helps to understand why a blockchain transfer behaves differently than a bank transfer.

7) Deliver worker-facing records and support

Workers still need the normal payroll artifacts:

Pay statements.
A clear statement of the USD1 stablecoins amount delivered, the valuation method, and the time stamp.
Support workflows for lost access, address changes, and off-ramp questions.

In many regions, workers will want to convert part or all of their USD1 stablecoins to local currency. That conversion is often where fees, delays, and compliance checks show up most clearly.

8) Reconcile and audit

Reconciliation (matching what was sent to what was owed) is essential. A payroll team should be able to answer:

Which transaction corresponds to which worker payment?
Was the payment delivered in full?
Did any transaction fail or get delayed?
What was the exact amount and time stamp?

Because blockchains are transparent, it can be tempting to rely on a block explorer (a website that shows blockchain transactions). But payroll recordkeeping usually needs more than a link. Internal records should include transaction identifiers, valuation notes, and approvals.

Legal and compliance topics to understand

Payrolls are regulated because they affect livelihoods. When adding USD1 stablecoins, the key point is that payroll compliance does not disappear. It often becomes more complex.

Wage payment rules and worker consent

Many jurisdictions have laws about:

Allowed forms of wage payment.
Required pay frequencies.
Required pay statement details.
Rules about deductions.
Minimum wage protections.

In the United States, federal wage rules discuss payment in cash or a negotiable instrument payable at face value in the context of meeting minimum wage and overtime obligations.^[9] States may add their own requirements. In other countries, wage laws may reference legal tender, bank transfer requirements, or employee consent.

At an international level, the International Labour Organization (a United Nations agency focused on labor standards) has a long-standing "Protection of Wages" convention that discusses how wages should be paid and protected.^[10] Not every country has ratified every convention, but it illustrates why wage payment is treated as a worker protection issue, not just a payment preference.

A practical way to think about USD1 stablecoins in payrolls is as an option that may be easier to support for contractors and harder to support for employees, depending on local law. This is not a universal rule, but it matches how many compliance teams approach the topic.

Sanctions and restricted-party screening

Sanctions (legal restrictions imposed by governments) can apply to payrolls in several ways: the worker's location, the employer's location, the jurisdictions involved in the payment path, and the service providers used.

OFAC has published guidance for the virtual currency industry that highlights risk-based controls (controls sized to the level of risk) and the importance of screening and recordkeeping.^[4] Even outside the United States, companies often need some form of sanctions screening because banks and vendors can require it.

Anti-money laundering and identity checks

Anti-money laundering (AML, meaning processes to detect and prevent money laundering) rules usually focus on financial institutions and certain intermediaries. If a company only pays its own workers, it may not be an AML-regulated business. But payroll setups can involve third-party services that are regulated.

FinCEN guidance discusses how U.S. rules can apply to certain business models involving convertible virtual currency (a digital asset that can be exchanged for government-issued money or for other digital assets).^[3] Globally, FATF (the Financial Action Task Force, an intergovernmental body that sets standards for AML and counter-terrorist financing, meaning efforts to prevent funding for terrorism) publishes guidance on virtual assets and service providers, including the idea of applying a risk-based approach (matching controls to the level of risk).^[5] FATF also publishes targeted updates on implementation trends, which can affect how countries interpret obligations.^[6]

For payroll decision makers, the key idea is not to turn the payroll department into an AML team. It is to understand that the service providers you use (exchanges, custodians, payroll platforms) may have AML obligations that affect onboarding, transaction monitoring, and reporting.

Data privacy and payroll confidentiality

Payroll data is sensitive. Wallet addresses can be personal data when linked to a worker. On-chain transactions can be visible to the public. That creates privacy risks such as:

Exposure of compensation patterns.
Exposure of worker identities if addresses are linked.
Permanent visibility of transaction history.

Privacy laws vary by region. Even without quoting any specific statute, the general principle is consistent: collect only what you need, protect it, and be clear with workers about what is shared and where.

Consumer protection and dispute resolution

Traditional payroll disputes often rely on bank records and the ability to trace transfers. With USD1 stablecoins, some disputes become simpler (the transaction is visible), but others become harder (the transfer is irreversible). Payroll operations should plan for:

Address change disputes.
Claims of unauthorized wallet access.
Situations where a worker loses private keys.

Because payrolls are high-stakes for workers, the dispute process should be explained in advance. This is more about expectations than technology.

Stablecoin-specific regulatory oversight

Stablecoins that reference the U.S. dollar are increasingly a focus for regulators because of potential financial stability and consumer protection risks. The Financial Stability Board has issued high-level recommendations for global stablecoin arrangements, emphasizing consistent regulation and oversight.^[7] Even if your payroll use case is small, the broader regulatory direction can influence what service providers offer and what controls they require.

Tax and accounting considerations

Tax and accounting topics can be the difference between a "cool pilot" and a sustainable payroll program. The details vary by country, but a few themes show up repeatedly.

United States tax treatment, as an example

In the United States, the IRS has stated that virtual currency is treated as property for federal tax purposes, and it has provided examples that address wages paid in virtual currency.^[1] In Notice 2014-21, the IRS explains that the fair market value of virtual currency paid as wages is subject to federal income tax withholding and payroll taxes, and it must be reported on Form W-2.^[1] The IRS also maintains an FAQ page that expands on scenarios and recordkeeping expectations.^[2]

For payrolls using USD1 stablecoins, the practical implication is that you should be able to document:

The time of payment.
The fair market value at that time.
The amounts withheld and remitted.
The reporting outputs (such as wage statements).

Even if USD1 stablecoins aim to stay near one U.S. dollar, the IRS framework still treats the payment as virtual currency property. Small differences can matter at scale.

Non-U.S. tax themes

Outside the United States, tax agencies may treat stablecoins as property, as a financial asset, or in some cases as a form of foreign currency. The right treatment depends on local law. Common payroll-related questions include:

Is the payroll obligation measured in local currency or U.S. dollars?
When does taxable income occur: at payment, at conversion, or at spending?
Are employer payroll taxes calculated based on local currency value at payday?
What documentation is required to support the rate used?

Because tax rules are jurisdiction-specific and change over time, it is common for payrolls teams to start with a limited scope pilot (for example, contractors in a few locations) while they build a repeatable documentation process.

Accounting and treasury reporting

Accounting treatment can depend on whether the company holds USD1 stablecoins briefly (for immediate payroll) or keeps a larger treasury position. Key questions include:

How is the asset categorized on the balance sheet?
How are gains or losses recognized when conversion rates move?
How do you demonstrate controls over the wallets holding payroll funds?

Organizations also need to consider treasury risk (risk arising from holding assets and making payments). If payroll relies on USD1 stablecoins, the company may need policies for:

Minimum liquidity buffers.
Diversification of service providers.
Redemption plans (how to convert USD1 stablecoins back to bank deposits if needed).

The more payroll depends on USD1 stablecoins, the more treasury and payroll become connected.

Payroll reporting and audit readiness

Auditors and finance teams often look for a strong paper trail, even when the transfer itself is visible on-chain. Helpful records include:

Payroll approvals and sign-offs.
The address used for each worker and how it was verified.
Transaction identifiers and time stamps.
Fee accounting (network fees and service fees).
Exception handling (what happened when something went wrong).

Risk management and security controls

Payrolls are a target for fraud even in traditional systems. Adding USD1 stablecoins changes the threat model (the set of risks you need to plan for).

Key risks unique to USD1 stablecoins payrolls

Address errors. A typo can send funds to the wrong place, permanently.

Irreversibility. Many blockchain transactions cannot be reversed without the recipient's cooperation.

Wallet compromise. If a private key is stolen, an attacker can drain funds quickly.

Service-provider outages. If an exchange or custodian is down on payday, payroll can fail.

Stablecoin and reserve risk. A stablecoin can deviate from its target value or face redemption limits.

Blockchain network risk. Congestion and fee spikes can delay settlement. Network upgrades can also introduce unexpected behavior.

FSB work on global stablecoins emphasizes the need for robust governance, risk management, and oversight for stablecoin arrangements.^[7] While a payroll user is not the issuer, payroll teams still face the operational consequences of these risks.

Controls that payroll teams commonly use

Segregation of duties. Separate who prepares the payroll batch from who approves and who executes payments.

Multi-signature wallets. Require multiple approvals to move funds. This can reduce single-point-of-failure risk.

Allow lists. Maintain a vetted list of worker wallet addresses, with change controls.

Transaction simulation. Some tools can simulate a transaction before sending to catch obvious mistakes.

Rate limits and time locks. Put limits on how much can move in a day or require a delay for large transfers.

Incident response planning. Decide in advance what happens if a wallet is compromised or a provider goes down. Payroll deadlines do not pause for technical incidents.

Security basics for recipients

Workers receiving USD1 stablecoins face their own risks. A few common issues:

Phishing (tricking someone into revealing secrets) that targets wallet credentials.
Lost recovery phrases (the backup words that restore wallet access).
Confusing network addresses (sending on the wrong blockchain network).

Employers should be careful not to shift all risk to workers. A payroll option that increases worker risk can backfire in retention and trust.

Smart contract considerations

Some payroll setups involve smart contracts, but many do not need them. If smart contracts are used, they introduce additional risks:

Code vulnerabilities.
Upgrade risk (changes to the contract).
Dependency risk (reliance on external services, sometimes called oracles, meaning services that provide off-chain data to on-chain programs).

If your payroll concept requires complex smart contracts to function, that can be a sign that the design is too complicated for a high-stakes system like payrolls.

Employee and contractor experience

A payroll program is only as good as the worker experience. USD1 stablecoins can feel simple to people already familiar with wallets. For others, it can feel like being asked to become their own bank.

Onboarding: what workers need to receive USD1 stablecoins

To receive USD1 stablecoins, a worker generally needs:

A wallet address on the supported blockchain network.
A safe way to store wallet credentials.
A plan to convert USD1 stablecoins into local currency if they need to pay local expenses.

This is why many programs start with contractors who already use digital asset tools.

Converting to local currency

Workers often care less about the on-chain transfer and more about the last mile:

Can they convert to local currency reliably?
What fees will they pay?
How long does the conversion take?
Will the exchange or wallet require identity verification?

These questions are partly market-driven and partly regulatory. FATF guidance focuses on how virtual asset service providers may be regulated and supervised, which can shape the conversion experience across countries.^[5]

Managing volatility expectations

USD1 stablecoins are designed to be redeemable one-for-one for U.S. dollars, but the user experience can still include surprises:

Temporary deviations from one U.S. dollar on secondary markets.
Withdrawal delays from service providers.
Network fees that change day to day.

A good payroll explanation makes these realities clear without panic or hype.

Privacy and personal safety

In some places, a worker may not want their compensation visible on a public ledger. This can be a personal safety concern, not just a preference. Practical mitigations include:

Allowing workers to provide a fresh address that is not reused.
Avoiding public sharing of employee addresses.
Educating workers that on-chain transactions can be visible.

Support and dispute handling

A common operational challenge is that payroll teams are not built to provide wallet support. Programs succeed when:

The scope is clear (what payroll supports vs what the worker manages).
There is a documented process for address changes.
There is a defined time window for payroll corrections.

Because blockchain transfers are typically final, prevention matters more than recovery.

Operational details that matter in payrolls

USD1 stablecoins can move quickly, but payrolls still need predictable operations. A few details that tend to matter more than teams expect:

Timing and cut-offs

Even if blockchain settlement is fast, payroll still needs time for:

Approvals.
Compliance checks.
Batch creation.
Address verification.
Provider processing time (if using an exchange or custodian).

Many payroll teams set an internal cut-off earlier than payday to create buffer time.

Transaction batching

Some payroll tools can batch multiple payments into fewer transactions. This can reduce fees, but it can also complicate reconciliation if not done carefully. The operational requirement is a strong mapping between each worker payment and the transaction record.

Network fees and congestion

Network fees can rise sharply during high demand. Because payroll is time-sensitive, payroll operations often prefer predictable fee environments. Some teams choose specific blockchain networks or settlement layers (layer 2, meaning a system built on top of a base blockchain to improve speed or reduce fees) for this reason.

Treasury funding strategy

A payroll program needs a plan for how payroll wallets are funded:

Just-in-time funding (buying USD1 stablecoins close to payday).
Pre-funding (holding a buffer of USD1 stablecoins).

Just-in-time funding reduces balance sheet exposure but increases dependency on the exchange being available at the right moment. Pre-funding reduces dependency but increases holding risk.

Business continuity

Payrolls cannot miss payday without consequences. A continuity plan may include:

Multiple liquidity providers.
Multiple custody options.
A fallback plan to pay in local currency if USD1 stablecoins rails are disrupted.

FSB discussions of stablecoin arrangements highlight the importance of operational resilience and effective oversight.^[7] Even if your program is small, the resilience mindset applies.

Frequently asked questions

Are USD1 stablecoins payrolls legal?

Legality depends on where the worker is located, how they are classified (employee vs contractor), and what local wage payment rules require. Some places require wages to be paid in local legal tender or in specific forms. U.S. federal wage rules, for example, discuss payment in cash or its equivalent in a way that payroll teams must consider when designing any alternative payment option.^[9] Because these rules vary and can change, companies often treat USD1 stablecoins payrolls as an opt-in option for specific populations.

Can a payment be reversed if it is sent to the wrong wallet address?

In most cases, blockchain transfers are not reversible. Recovery is usually only possible if the recipient cooperates or if the payment was sent to a custodial provider that can intervene. This is why address verification and approval controls are so important.

Do workers owe taxes when they receive USD1 stablecoins?

Tax treatment depends on the worker's country. In the United States, the IRS treats virtual currency as property, and the fair market value paid as wages is subject to withholding and payroll taxes and must be reported like other wages.^[1] Other countries may treat stablecoins differently. Workers should understand their local reporting duties.

Is the stable value guaranteed?

No stablecoin value is guaranteed. USD1 stablecoins are intended to be redeemable one-for-one for U.S. dollars, but the stability depends on how the stablecoin is structured and managed, how redemptions work, and the resilience of the underlying infrastructure. International bodies have warned that stablecoins can still pose risks and require robust oversight.^[7]

What about sanctions screening if payroll is on a public blockchain?

Sanctions obligations are typically triggered by legal jurisdiction and the parties involved, not by whether a payment is on-chain or off-chain. OFAC guidance for the virtual currency industry describes the importance of risk-based compliance controls, recordkeeping, and screening.^[4] Many service providers also apply their own screening requirements.

Do we need to understand blockchain technology to run payrolls this way?

You do not need to be a protocol engineer, but you should understand the basics of how blockchain settlement differs from bank settlement, especially finality and irreversibility. NIST provides a clear technical overview that can help non-specialists build that understanding.^[8]