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
Global payroll that lets businesses pay teams in local currency or crypto.
Rise is a platform for paying international employees and contractors. My work focused on crypto funding: accepting different tokens, converting them to USDC and moving funds between supported networks. I built the contract and backend integrations using Uniswap v4 and Circle CCTP v1.
Delivered deposit and cross-chain payroll integrations across the contract and backend stack, covering 50+ input tokens and more than seven networks.
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.
Architected a Uniswap v4 integration for multi-token deposits that settle into USDC.
Implemented Circle CCTP v1 integration for the payroll flow across supported networks.
Worked from upgradeable proxy contracts through TypeScript APIs, database records and asynchronous jobs.
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.The integration converts the input into the settlement asset used by the payroll flow.
Input asset → USDCDownstream payroll logic works with a consistent asset.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.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.Connect token conversion and cross-chain transfer to the same payroll journey instead of pushing that complexity onto the customer.
Track the intermediate steps needed by a cross-chain transfer rather than treating it as one synchronous API call.
Public product context. The private implementation and contribution scope are described in this case.
Current public payment documentation. Product context; my 2025 implementation scope comes from the engagement record.
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.