You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When interacting with Bitcoin ATMs (and potentially other external systems) that generate precise crypto asset amounts with many decimal places.
Steps to Reproduce:
Go to a Bitcoin ATM and choose to withdraw, e.g., 100 PLN.
The ATM generates a QR code for a crypto amount, e.g., 26.434343543 ETH
Scan or manually input the USDT or ETH amount into our app's Send screen.
Actual Result:
The Send screen only accepts limited decimal places, so 26.43 (in case this is stablecoin) is allowed, but 26.434343543 is rejected.
This makes it impossible to send the exact required amount, which is often mandatory for successful ATM transactions.
ATM requires 8 decimals for ETH and USDT
Status app allows 6 decimals for ETH and 2 for USDT and other stablecoins
Expected Result:
The Send screen should allow higher precision for assets like USDT, ETH,, especially since USDT supports up to 6 decimals (or more depending on chain).
Ideally, the input precision should match the token’s allowed decimals, or be dynamically adjusted per asset.
ENV:
Nightly 23 Apr, 2025
The text was updated successfully, but these errors were encountered:
Description:
When interacting with Bitcoin ATMs (and potentially other external systems) that generate precise crypto asset amounts with many decimal places.
Steps to Reproduce:
Actual Result:
The Send screen only accepts limited decimal places, so 26.43 (in case this is stablecoin) is allowed, but 26.434343543 is rejected.
This makes it impossible to send the exact required amount, which is often mandatory for successful ATM transactions.
ATM requires 8 decimals for ETH and USDT

Status app allows 6 decimals for ETH and 2 for USDT and other stablecoins
Expected Result:
The Send screen should allow higher precision for assets like USDT, ETH,, especially since USDT supports up to 6 decimals (or more depending on chain).
Ideally, the input precision should match the token’s allowed decimals, or be dynamically adjusted per asset.
ENV:
The text was updated successfully, but these errors were encountered: