Billing
Manage balance, payments, checks, and API operations from one control desk.
My Orders
New OrderYour recent orders
| # | Status | Link | Address | Network | Date Created |
|---|
Billing
Current Balance
$0.00
Available funds
Price per Check
$20.00
Cost per verification
Available Checks
0
Based on current balance
Top Up Balance
Select Payment Method
Transaction History
| Date | Type | Description | Amount | Status | Balance After | Actions |
|---|
API Keys
API Documentation Available
Learn how to integrate Chainy API into your application with our comprehensive documentation. Find code examples, authentication guides, and endpoint references.
View API DocumentationCreate New API Key
Your API Keys
| Name | Key | Created | Last Used | Status | Actions |
|---|
Risk Models
Set up one model in six steps.
Use this page from top to bottom. In the usual flow you choose a template, create a draft, change thresholds, test the result, bind it, and only then activate it.
Choose where to start
Use a template if you want a safe baseline. Open an existing draft if you already started one earlier.
This panel only checks what model is currently applied for a given API key and check type. It does not edit anything.
Your drafts and active models
Open one of these if you want to continue editing or inspect what you already prepared.
Templates
Templates are read-only. Use one as the base for a new draft in Step 2, or preview its rules first.
Create a draft
Choose a base, fill in the basic metadata once, and create the draft you will edit below.
Draft setup
No popups. Everything stays on one page.
Edit how the draft decides
Start with the common settings below. Open Advanced JSON only when you need category weights, meta rules, or deeper tuning.
Common settings
These four numbers are the most common changes. Review means HOLD. Block means REJECT.
Changing these fields updates the JSON below automatically. Save Rules after you are done.
Advanced JSON editor
Test the result before you bind anything
Load one of the examples, tweak the payload if needed, and run a simulation to see the decision and score.
Choose where this model should apply
Bind by API key when only one integration should use the model. Bind by check type when you want a broader fallback.
Bind to one API key
Bind as a fallback for a check type
Use this when all wallet checks or all deposit checks should fall back to this model unless a more specific API key binding exists.
| Scope Type | Scope Value | Priority | Mode | Status | Actions |
|---|
Activate when you are satisfied
Activation affects only future checks, and only where the model is actually bound.
Referrals
Referral Links
0
Active and archived links
Referred Users
0
Users attached to your links
Rewards Earned
$0.00
Credited to your balance
Referred Revenue
$0.00
Revenue generated by referrals
Create Referral Link
Your Links
| Name | Link | Commission | Referrals | Rewards | Status | Actions |
|---|
Recent Referral Rewards
| Date | Referred User | Source Amount | Reward | Status |
|---|
USDT Transfers
Check USDT Transfers
Total Transfers
0
Total Sent
0 USDT
Total Received
0 USDT
Net Balance
0 USDT
Transfer History
Loading USDT transfers...
| Date | Type | From | To | Amount (USDT) | Transaction Hash |
|---|
Deposit Checks
address,network — supported networks: ETH,
BSC, TRX, BTC, SOL. Max 50 addresses.
Transaction Check Result
KYT Status:
—Decision:
—Risk Score:
—Deposit Checks History Auto-refreshing
| ID | Date | Network | Tx Hash | Address | KYT Status | Risk | Decision | Actions |
|---|
Manual Checks History
| ID | Date | Check Type | Target / Name | Network | Status | Actions |
|---|
Deposit Check Details
Tx Hash:
Address:
Decision:
Risk Score: