Keep the product flow coherent
Connect token conversion and cross-chain transfer to the same payroll journey instead of pushing that complexity onto the customer.
Case 06 · Cross-chain payroll
Rise
Making payroll work when deposits arrive in different tokens and chains.
I worked across contracts and backend services for crypto payroll, implementing multi-token deposits into USDC and Circle CCTP v1 transfers across more than seven networks.
Result
Delivered deposit and cross-chain payroll integrations across the contract and backend stack, covering 50+ input tokens and more than seven networks.
My part
What I did
Payroll needs one usable payment flow even when customers hold different tokens on different chains. Contract execution must connect to asynchronous backend work and destination-chain completion.
01
Deposit contracts
Architected a Uniswap v4 integration for multi-token deposits that settle into USDC.
02
Cross-chain transfers
Implemented Circle CCTP v1 integration for the payroll flow across supported networks.
03
Backend orchestration
Worked from upgradeable proxy contracts through TypeScript APIs, database records and asynchronous jobs.
How it worksSimplified walkthrough. No live transactions.
Different input assets. One payroll settlement flow.
Wallet + deposit contracts
The customer starts with a supported ERC-20 token rather than first managing a separate conversion outside the payroll product.
Supported input token → depositThe product accepts the customer’s starting asset.Example state, not live data
- Asset
- Input ERC-20
- Chain
- Source
- Stage
- Deposited
Uniswap v4 integration
The integration converts the input into the settlement asset used by the payroll flow.
Input asset → USDCDownstream payroll logic works with a consistent asset.Example state, not live data
- Asset
- USDC
- Chain
- Source
- Stage
- Converted
Circle CCTP v1 + async jobs
The backend coordinates the source-chain burn, attestation and destination-chain mint steps through asynchronous processing.
Burn → attestation → mintCross-chain completion is a multi-stage process.Example state, not live data
- Asset
- USDC burned
- Chain
- Source → destination
- Stage
- Awaiting attestation / mint
API + database
The service tracks transfer progress through to the destination so the payroll application can represent the result.
Source transaction → destination completionThe source transaction alone is not the whole payroll outcome.Example state, not live data
- Asset
- USDC
- Chain
- Destination
- Stage
- Transfer complete
Trade-offs
Decisions I made
Use asynchronous orchestration
Track the intermediate steps needed by a cross-chain transfer rather than treating it as one synchronous API call.
Links and records
See the work
Product contextRise payroll platform
Public product context. The private implementation and contribution scope are described in this case.
Career record
50+ tokens · 7+ networks
Scope recorded in my CV for the February to August 2025 engagement; historical figures, not current platform-wide claims.
Historical scope from the February to August 2025 engagement, as documented in my CV. Rise’s website provides public product context.
The flow explains my integration work without exposing customer transactions or private payroll data.