Reviewing results
Each verification request has a details page showing what the customer submitted and what Scrya confirmed. Results update as the customer works through each asset.
Open a request
- Go to Requests.
- Click the request’s row, or click View.
You can also open a request from the customer’s Customer Details page.
The top of the page shows two cards:
- Request Information: the date it was Requested, its Status, the number of Assets, and any Message to customer or Reason you added.
- Customer Information: the customer’s name, email and date of birth. Click View Customer Details for their full record.
Read the asset results
Under Asset Verification, there’s one card for each asset and network, such as USDT on Tron. Each card shows how many addresses are verified (for example, 1 of 2 verified) and a total balance once Scrya has recorded one.
Each row in the card is one address or exchange account:
- A wallet row shows the full wallet address.
- An exchange row is named after the exchange, for example “Kraken account”.
- A row that says Waiting for customer to submit verification hasn’t been started yet.
- A row in Monitoring shows how long is left in its 24-hour window.
- A Failed row shows the reason the check didn’t complete.
- A verified row shows Address Verified, the date it completed and, when Scrya recorded one, the Verified balance.
See Request statuses for every row status.
Understanding balances
- The balance is what Scrya read when the check ran. The US dollar figure (“at verification”) is a snapshot from that moment, not a live value.
- Verified doesn’t mean the balance meets a particular amount. A wallet can be verified with a zero balance, so always check the balance itself.
- An exchange holds one balance per asset, so an exchange balance covers the customer’s whole account for that asset. The network label comes from the request, not from the exchange.
- For a wallet, Verified means two things were checked. First, Scrya confirmed the signature was made by the key for that exact address, over a one-time message it issued. Then it read the address’s balance from the public blockchain. A balance read on its own never marks a wallet verified. The exception is an address Scrya’s team approves by hand, which may have no balance recorded.
Approving and rejecting
You don’t approve or reject addresses yourself. Wallet and exchange checks run automatically, and only Scrya’s team can reject an address. The request status updates on its own as results come in.
What you can do:
- Click Download Certificate once at least one holding is verified. See Verification certificates.
- Click Close Request to stop a request (Business Admins only). Closing is meant to be final.
- Create a new request if you need more proof. See Creating a verification request.
Check an address on a blockchain explorer
To check a wallet yourself, copy the full address from its row and search for it on the explorer for that network: Mempool.space (Bitcoin), Etherscan (Ethereum), Solscan (Solana), Tronscan (Tron), BscScan (BNB Smart Chain), PolygonScan (Polygon), Arbiscan (Arbitrum One) or BaseScan (Base).
Activity and change history
The Activity card lists the key milestones: Request sent, Email sent to customer, Customer first submitted, and whether the request was approved or rejected. Change History below it records every change to the request.
Email sent to customer only tracks the request email. For a new customer who got an account invitation instead, this step keeps waiting.
Emails about results
When every address has a result, the person who created the request gets one email per address. If every address is verified, the certificate is attached to the first email. See Notifications and emails.
