Security
easyway is a non-custodial gateway. Your customers pay straight into a wallet that only you control. This page says what we can and cannot do, what we store, and which parts of security are yours. It describes what exists today, nothing more.
Where the money goes
For each network you want to accept, you enter a receiving wallet in the dashboard. The checkout page shows your customer that wallet, and the transfer goes from them to you on the blockchain. It never passes through an address controlled by easyway. There is no balance held with us, nothing to withdraw, and no fee deducted from a payment.
Our part is to watch the blockchain: we see the transfer arrive at your address, wait for the confirmations the network needs, work out which invoice it pays, and tell you by webhook, in the dashboard and through the API.
What we can and cannot do
| We cannot | We can |
|---|---|
| Move, freeze, reverse or recover coins in your wallet | See transfers to the addresses you gave us, because blockchains are public |
| Sign a transaction for you, or send a refund for you | Mark an invoice as paid, underpaid, overpaid or late based on what arrived |
| Ask for, read or store a private key or seed phrase | Show your receiving address and the amount on the checkout page |
| Restore access to a wallet whose keys you have lost | Send you webhooks and emails about your invoices and your account |
One point deserves to be stated plainly: the checkout page is served by us and shows the wallet saved in your account. If that saved wallet were replaced, future customers would be shown the new one. That is why a wallet change is the most protected action in the product; see below.
Your receiving wallets
What you enter is public information only. Depending on the network it is either an address, or an account-level extended public key. An extended public key lets us work out the next receiving address of your wallet for each new invoice. It cannot spend. Anything that looks like a private key or a seed phrase is refused and is not saved.
| Network | Coins | What you enter | How an invoice is recognised |
|---|---|---|---|
| TRON | USDT, TRX | One address | Exact amount per invoice |
| BNB Smart Chain | USDT, BNB, USDC, FDUSD, CAKE, TWT | One address | Exact amount per invoice |
| TON | USDT, GRAM, NOT, DOGS, CATI, HMSTR | One address of your own wallet | Comment (memo) per invoice |
| Ethereum | USDT, ETH, USDC, DAI, SHIB, PEPE, PYUSD, LINK, UNI, AAVE, ONDO, ENA, CRV, GRT, SKY, USDS, USDe, MNT, ARB, WLD, MANA, SAND, IMX, GALA, FET, JASMY, SPX, XCN, APE, AXS, CHZ, 1INCH, PENDLE, ETHFI, ZRO, BAT, LPT, ZRX, SUSHI, BAL, COMP, RPL, ANKR, CVX, GLM | One address | Exact amount per invoice |
| Bitcoin | BTC | Extended public key (xpub / ypub / zpub) or one address | New address per invoice (extended public key); exact amount if you set a single address |
| Litecoin | LTC | Extended public key (Ltub / Mtub / xpub / ypub / zpub) or one address | New address per invoice (extended public key); exact amount if you set a single address |
| Dogecoin | DOGE | Extended public key (dgub / xpub) or one address | New address per invoice (extended public key); exact amount if you set a single address |
| XRP Ledger | XRP | One address of your own wallet | Destination tag per invoice |
| Solana | SOL, USDT, USDC, BONK, WIF, RENDER, JUP, PYTH, JTO, RAY, W, FARTCOIN, TRUMP, PENGU, POPCAT | One address | Exact amount per invoice |
| Polygon | POL, USDT, USDC | One address | Exact amount per invoice |
| Avalanche | AVAX, USDT, USDC | One address | Exact amount per invoice |
| Base | ETH, USDC | One address | Exact amount per invoice |
| Arbitrum One | ETH, USDT, USDC | One address | Exact amount per invoice |
| OP Mainnet | ETH, USDT, USDC | One address | Exact amount per invoice |
| Dash | DASH | Extended public key (drkp / xpub) or one address | New address per invoice (extended public key); exact amount if you set a single address |
Protection of wallet changes
Replacing an existing wallet requires two-factor authentication to be switched on and a fresh code from your authenticator app. Every wallet that is added, changed or removed is emailed to the account owner and written to the activity log with the time and IP address. Requests to change a wallet are rate limited. One address or key can belong to one account only.
Before you save an extended public key, the dashboard shows the first three addresses derived from it. Compare them with the receive addresses in your own wallet app; if they differ, the key or the address type is wrong and payments would not show up where you expect.
What an extended public key reveals
Whoever holds an extended public key can see every address and transaction of that wallet account, though they can never spend from it. We store it to derive addresses and show only its first and last characters in the dashboard. If you prefer to keep your other holdings private, create a separate account in your wallet app for easyway and export that account's key.
How a payment is matched to an invoice
A new address per invoice
With an extended public key (Bitcoin, Litecoin, Dogecoin, Dash), every invoice gets its own address from your wallet. A transfer to that address belongs to that invoice. An address that was shown to a customer but never received anything can be given out again later, which keeps your wallet app from losing track of addresses far ahead of the last used one.
One address and a memo
On TON and the XRP Ledger you enter one address and each invoice gets a numeric comment (TON) or destination tag (XRP). The checkout shows it and the customer must include it. Use a wallet of your own here, not an exchange deposit address: an exchange usually needs its own memo to credit you, and there is room for only one.
One address and an exact amount
On TRON, the EVM chains (Ethereum, BNB Smart Chain, Polygon, Avalanche) and Solana there is no memo field, so invoices that share your address are told apart by the amount. The checkout asks for an amount made unique with a few extra decimals, for example 25.001 USDT instead of 25. One step is worth about a tenth of a cent or less. The customer must send exactly the amount shown. The same method is used if you enter a single address on a Bitcoin-like network.
When a transfer cannot be matched
If a transfer to your address cannot be tied to exactly one open invoice (a missing or unknown memo, or an amount that fits none or several), it is never guessed. It is listed as an unmatched transaction in your dashboard, and you either assign it to an invoice or mark it as ignored. The coins are in your wallet in every case. Transfers that reach your wallet while no invoice is being watched on that address are not our concern and are not recorded.
When a payment counts as paid
An invoice is marked paid only after enough blocks have been built on top of the transfer for the network to treat it as final. Until then it shows as confirming.
| Network | Confirmations |
|---|---|
| TRON | 19 |
| BNB Smart Chain | 15 |
| TON | 1 |
| Ethereum | 12 |
| Bitcoin | 2 |
| Litecoin | 4 |
| Dogecoin | 6 |
| XRP Ledger | 1 |
| Solana | 1 |
| Polygon | 64 |
| Avalanche | 10 |
| Base | 30 |
| Arbitrum One | 240 |
| OP Mainnet | 30 |
| Dash | 4 |
Underpaid, overpaid and late payments are recorded as such on the invoice, and every invoice keeps a history of its status changes. A payment that arrives after an invoice has expired or been cancelled is still recorded and flagged as late, for as long as that invoice's address or amount is being watched: seven days after expiry for a per-invoice address, a few hours for a shared address.
Protecting your account
Two-factor authentication
Accounts support time-based one-time codes (TOTP, RFC 6238), which work with Google Authenticator, Authy, 1Password and similar apps. Switch it on before you add wallets: it is required to replace a wallet, and once it is on, a code is also asked for when you add or remove a wallet and when you create or rotate a live API key.
Activity log
Sensitive actions (wallets added, changed or removed, API keys created or revoked, webhook changes, 2FA changes, plan orders) are recorded with the time and IP address, and you can review them in the dashboard.
API keys
Secret keys are shown once, when you create them, and stored only as a keyed hash. Each key carries scopes (invoices:read, invoices:write, transactions:read) and an optional IP allowlist. No API key can change a wallet or move money: the API has no endpoint for either. A leaked key could create or cancel invoices and read your payment data, so revoke it as soon as you suspect it. Test and live keys are separate, and test keys never touch a blockchain.
Signed webhooks
Every webhook carries an X-Webhook-Signature: t=…,v1=… header: an HMAC-SHA256 of the timestamp and the raw body, made with your endpoint's secret. Checking it (and rejecting old timestamps) proves the event came from easyway and was not replayed. Failed deliveries are retried 8 times with growing delays over about 45 hours. Verification code for Node.js, PHP and Python is in the webhooks documentation.
What we store
Your sign-in email and business details; the public addresses or extended public keys of your receiving wallets; your invoices and the on-chain transfers matched to them (transaction id, sending address, amount, time); customer email addresses if you choose to send them with an invoice; API keys as hashes; webhook URLs and their signing secrets; your 2FA secret; and the activity log. We do not store private keys, seed phrases or wallet passwords, because we never receive them. The privacy policy has the full list.
What you are responsible for
Your wallet's keys and backups. If you lose the seed phrase or private key of a receiving wallet, nobody at easyway can recover the coins in it.
The addresses you enter. Check each address or key against your own wallet before saving it, and make sure the wallet supports the coin and network. Coins sent to a wrong or unsupported address cannot be brought back by us.
Access to your account and email. Turn on 2FA, keep API keys out of public code, and read the security emails we send when a wallet changes.
Refunds. A refund to your customer is a transfer you send from your own wallet.
Reporting a vulnerability
If you find a security problem, email support@easyway.cash with the details and how to reproduce it. Please give us a chance to fix it before telling anyone else.