Regional Operations
Verification activity and active Web-Direct routes
Use your individual Verifier or Vendor account. Access remains in this browser tab only.
Verification activity and active Web-Direct routes
Last 30 days · privacy-safe milestones
Submitted, approved and rejected claims
Current voucher availability and release state
Active receiving routes
Newest claims needing attention
Latest claim decisions
Vendor onboarding, verifier coverage and operating health
New submissions and partners requiring super-admin action
Your organization can see only its own approved assignments. Receiving-account changes require Myalt.Cash review.
Commission and settlement activity recorded for your organization.
Sensitive changes never update production automatically. A Myalt.Cash super administrator must review them.
Potential and pending amounts are estimates. Confirmed earnings are based on the commission agreement set by Myalt.Cash.
Currencies remain separate so totals are never combined using an unstated exchange rate.
Your earning agreement and operational permissions are controlled separately.
Available stock can receive new assigned claims. Reserved stock is attached to a customer claim under review; issued stock has already completed release.
An exception means an active customer payment method has no enabled eligible vendor route.
New Claims chooses Primary first, then Fallback, then Overflow. Capacity is measured against each vendor’s configured daily cap.
Invitations expire after 48 hours. The recipient creates an individual password and must activate MFA before access begins.
Approval records the decision only. Apply any authorized vendor or payment-route change separately so it remains auditable.
Verifier promotions may be approved by the submitting super admin. Funded-settlement promotions require a different super admin to approve and activate them.
Pause stops new routing. Recall returns unused reserved vouchers to central inventory; issued vouchers remain attached for audit.
Referral vendors only refer customers. Verifier vendors review assigned payments. Funded settlement vendors require verified identity, agreement and banking checks before activation.
Assign one partner to one regional payment method. Active routes require verified partner checks, a matching country, verified customer deposit details, matching inventory and available route capacity. Primary routes are tried before fallback and overflow.
When recording a partner payout request, select Commission paid, use the exact approved amount and currency, include the external transfer reference, and link its approved request ID. This records evidence after a transfer; it does not initiate one.
Append-only operational entries. Float entries are limited to funded settlement vendors; every entry is audited.
Ledger reporting separates potential and pending estimates from confirmed earnings, accounting adjustments, and recorded payouts. The balance is an accounting total only. This screen does not send funds; enter a payout only after an external transfer is confirmed and include its reference.
Reviewing or approving a request does not transfer funds. Use the settlement form only after an external payment is confirmed; link the approved request and record the transfer reference.
Partners may register crypto or fiat destinations. Review the details with fresh MFA before verification. Reveals and decisions are recorded in the audit trail; this page never initiates a transfer.
Customer claims preserve an exact invoice and receiving-account snapshot. Choose the primary or backup account for new claims only; existing claims never change. Backup details are never returned by the public payment-route endpoint.
Paste copied issuer rows below. Codes are encrypted before storage and never shown again in this dashboard. Used, expired, inactive and duplicate vouchers are rejected.
Use individual accounts. Vendor accounts are scoped to their assigned organization and claims. Referral partners cannot view evidence, inventory or payment controls.
Read-only activity history. Voucher codes and full payment references are excluded.
Claims has its own authenticator setup. You can add this as a separate Myalt.Cash Claims entry in the authenticator app you already use. Your existing Myalt.Cash admin entry will remain unchanged. Setup requires your current Claims password and confirmation with a fresh 6-digit code.
Online: active within 5 minutes. Idle: 5–30 minutes. Offline: no activity for more than 30 minutes.
Successful and failed sign-ins, MFA failures, sign-outs and administrative session actions.
The server enforces these scopes even when a restricted URL is entered manually.
Acceptance records appear here when versioned partner or staff policies are acknowledged. Missing records are clearly identified; access is not silently inferred.
Delivery status for verifier Telegram and email alerts.
Select a template to preview, edit or send a clearly marked test.
Use a recognizable name and select the closest purpose. A safe internal key is generated automatically.
Internal key: new_template
Approved variables: {{recipient_name}} {{reference_number}} {{amount}} {{status}} {{expiry_time}}
Optional. A Super Admin may register one exact official HTTPS channel destination. Campaigns from that channel can then use it, while all other external redirects remain blocked.
Privacy-minimized funnel counts only. No customer handles, wallet addresses, payment references, voucher codes, IP addresses or receipt data are collected here.
Review inventory, OTC, settlement, marketing, team-access and support requests. Replies remain visible to the partner and are recorded in the audit history.