Skip to content

Creating a verification request

A verification request asks a customer to prove they hold one or more crypto assets. You choose the assets and networks. The customer then verifies each one from their portal, using a private wallet or an exchange account.

Create and send a request

  1. Go to Requests and click New Request. You can also click New Request on Customers, or Create New Request on a customer’s Customer Details page.
  2. Under Customer, choose the customer. To add someone new, choose Create new customer. If you started from Customer Details, the customer is already filled in. See Adding customers.
  3. Optionally enter a Reason. It isn’t included in the email, but the customer can see it in their portal.
  4. Under Assets to verify, tick each asset: Bitcoin, Ethereum, Solana, USDC or USDT. Bitcoin is ticked to start with.
  5. If you tick USDC or USDT, choose the network under Chain for USDC or Chain for USDT. Pick the chain the customer holds the balance on.
  6. Optionally write a Message to customer, such as instructions. Click Preview email to see how it will look.
  7. Click Continue.
  8. Check the final email preview on Review verification email (or Review invitation for a new customer). Click Back to make changes.
  9. Click Create & send email, or Create & send invitation for a new customer.

Choosing networks

Bitcoin, Ethereum and Solana each have one network. The stablecoins can be held on several:

AssetNetworks you can choose
USDCEthereum, Solana, BNB Smart Chain, Polygon, Arbitrum One, Base
USDTEthereum, Tron, Solana, BNB Smart Chain, Polygon, Arbitrum One

You can choose one network per stablecoin in each request. If you’re not sure which one the customer uses, ask them first. See Supported assets and networks.

Requests don’t include an amount or minimum balance. You review the balances Scrya records in the results.

What the customer receives

If the customer already has a Scrya account, or you’ve already invited them, they get an email with the subject “[Your organisation] has requested asset verification”. It shows a request ID (VR- followed by eight characters), the assets to verify, the request date, your message and a Complete Verification button.

If the customer is new, they get only their Scrya account invitation. The request waits in their portal until they accept the invitation. Your message isn’t emailed in this case, but the customer sees it in their portal.

If the customer already has a pending request

Each customer can have only one Pending request with your organisation. If one exists, Scrya adds your new assets to it instead of creating another. You’ll see Added to existing request, or Already in existing request if it already covers everything you chose. If you entered a message, it replaces the old one.

Scrya doesn’t send another email when it adds assets to an open request, so let the customer know.

Delete a request

You can delete a request while it’s Pending. On Requests, click the bin icon on the request’s row, then click Delete. This can’t be undone.

Troubleshooting

  • Continue is greyed out. Choose a customer, tick at least one asset, and choose a network for each stablecoin.
  • The customer didn’t get an email. Check their email address on Customer Details. Scrya can’t email a customer who has no email address. See Reminders and expiry.
  • You see a reference such as ERR-XXXX-XXXX. See Error references.