Accept SushiSwap (SUSHI) payments
SUSHI is the governance token of Sushi, the decentralized exchange that started in 2020 as a fork of Uniswap. easyway accepts SUSHI as an ERC-20 on Ethereum with the same checkout and API as ETH and the stablecoins. Below: the exact contract, what does not count as a SUSHI payment, and the numbers.
Token, network and limits
| Token | Network | Contract | Confirmations | Min. withdrawal | Withdrawal fee |
|---|---|---|---|---|---|
| SUSHI (SushiSwap) | Ethereum · ERC-20 | 0x6B3595068778DD592e39A122f4f5a5cF09C90fE2 | 12 | 3.5 SUSHI | 12 SUSHI (flat) |
Sushi's own docs (DAO → Tokenomics) give this contract as the SUSHI token on Ethereum, and CoinGecko and Trust Wallet's token list give the same one. It is the original SushiToken: a plain ERC-20 with 18 decimals, not an upgradeable proxy, and it takes no fee on a transfer, so the amount the customer sends is the amount that arrives. New SUSHI is still minted as liquidity rewards, so the supply grows slowly over time.
What counts as a SUSHI payment
Only a plain transfer of the Ethereum token to the invoice address counts. Staked SUSHI and SUSHI on other chains are different tokens to the checkout:
| What the customer holds | Where it is | Credited? |
|---|---|---|
| SUSHI in an Ethereum wallet or on an exchange | 0x6B3595068778DD592e39A122f4f5a5cF09C90fE2 | Yes |
| xSUSHI (SUSHI staked in the SushiBar) | 0x8798249c2E607446EfB7Ad49eC89dD1865Ff4272 | No — unstake to SUSHI first |
| SUSHI on BNB Smart Chain, Polygon, Avalanche, Arbitrum … | A bridged copy with its own contract | No |
This matters more than for most tokens: SUSHI has bridged copies on BNB Smart Chain, Polygon and Avalanche, which easyway also supports for other coins, and an easyway deposit address is the same on every EVM chain. A wallet set to one of those networks will accept the invoice address without a warning; the tokens then sit at that chain's copy of the address and the invoice stays open. Ask customers to pick SUSHI on Ethereum (ERC-20). When paying from an exchange, the withdrawal form decides the network; the guide to paying from an exchange shows where.
Amounts and fees
On a USD invoice the SUSHI amount is locked from the exchange rate when the customer selects the coin, and the checkout shows the exact amount to send. Transfers under 0.05 SUSHI are skipped as dust; several larger ones add up, and the invoice is paid after 12 confirmations, usually a few minutes. Short or late payments follow the underpaid and late payments guide.
SUSHI is not a stablecoin: the payment is credited and later withdrawn in SUSHI, so later price moves are yours. The platform fee is a flat 0.5% of each confirmed payment: 1000 SUSHI received leaves 995 SUSHI on your balance. A withdrawal costs a fixed 12 SUSHI, which covers the Ethereum gas of one token transfer, so withdraw in larger batches rather than many small ones. Every coin's numbers are on the pricing page.
Integrating
Nothing is SUSHI-specific: create an invoice with the API (or a payment link if you don't write code), send the customer to the hosted checkout and deliver when the signed invoice.paid webhook arrives. To price an invoice in SUSHI itself, pass currency = "SUSHI_ERC20"; to show only SUSHI at checkout, pass allowed_assets with "SUSHI_ERC20" (see limiting the checkout to some coins). Runnable examples are in the quickstart.
Common questions
Is easyway connected to Sushi? No. easyway is independent and does not route trades through Sushi; it only receives the SUSHI token on Ethereum as a payment for your own goods or services. It does not swap, stake or vote with it.
Where is the SUSHI kept after a payment? On your easyway balance until you withdraw it. Live withdrawals only go to addresses you whitelisted with two-factor authentication; see security. Other DEX tokens accepted include Uniswap (UNI), PancakeSwap (CAKE) and 0x Protocol (ZRX); the DeFi token guide compares them.