Request statuses
Every verification request has a status, shown on Requests, on Customer Details and under Request Information on the request itself. Each asset row in a request also has its own status. This page explains both.
Open and closed requests
A request is either open or closed.
- Open requests (Pending and In_progress) are still active. The customer can submit or redo verifications, and a Business Admin can still close the request.
- Closed requests (every other status) are final. The customer can’t add or change addresses, and the status can’t change again. Checks that were already running may still finish. The customer’s portal shows the request as read-only.
Request statuses
The status badge reads, for example, Pending or In_progress.
| Status | What it means | How a request gets here | What to do |
|---|---|---|---|
| Pending | Waiting for the customer. | Every new request starts here. It stays here until the first address is verified or rejected. | Check the Activity card to confirm the email went out. Resend the invitation if the customer isn’t linked yet. |
| In_progress | Some addresses have a result, others don’t. | At least one address was verified or rejected while others are still outstanding. | Review the results so far. Wait for the rest. |
| Verified | Every address was verified. | The last outstanding address was verified and none were rejected. | Review the balances and download the certificate. |
| Rejected | Every address has a result and at least one was rejected. | Scrya’s team rejected an address, and every other address has a result. | Review the results. Contact the customer, or create a new request. |
| Completed | The customer finished the request early. | The customer clicked Complete request in their portal. This needs at least one verified address. | Review what was verified. Any address without a result stays unverified. |
| Closed | Your organisation or the customer closed the request. | A Business Admin clicked Close Request, or the customer closed it. | Nothing. Scrya support may be able to recover a request closed by mistake. |
| Cancelled | The customer cancelled the request. | The customer clicked Cancel request in their portal. | Contact the customer. Create a new request if you still need proof. |
| Expired | The request ended without a full result, and at least one address expired. | Every address was verified, rejected or expired, at least one expired and none failed, and no address changed for 7 days. | Create a new request if you still need proof. |
| Failed | The request ended without a full result, and at least one address failed. | Every address was verified, rejected, failed or expired, at least one failed, and no address changed for 7 days. | Create a new request if you still need proof. |
A request doesn’t change status as soon as an address fails or its monitoring window expires. It stays open so the customer can try again. Scrya closes it as Failed or Expired only when every address has a result and nothing on the request has changed for 7 days. You aren’t emailed when this happens. If Scrya’s team later verifies or rejects every address, the request changes to Verified or Rejected.
On Requests, a Failed warning next to the status means one or more asset verifications on that request have failed.
You can only delete a request while it’s Pending.
Address statuses
Each asset row on the request shows its own status.
| Status | What it means |
|---|---|
| Pending | The customer hasn’t submitted this address yet. |
| Monitoring | For a wallet, the signature has passed and Scrya is reading the balance. |
| Verified | The check succeeded. |
| Completed | The check finished successfully. |
| Failed | The check couldn’t be completed. The row shows the reason. For a wallet, this is usually a signature that doesn’t match the address, or a message that expired before it was submitted. The customer can click Start new verification to try again. |
| Expired | The 24-hour monitoring window ended without a result. The customer can start again. |
| Rejected | Scrya’s team rejected this address. |
See Reminders and expiry for how long monitoring lasts.
Troubleshooting
- A request is stuck on Pending. The customer may not have submitted anything, or their addresses failed or expired less than 7 days ago. Open the request to check each row.
- You can’t close a request. Only Business Admins can close requests, and only while they’re open. See Roles and permissions.