Binance Direct Deposit and HyoNova Balances

Binance Direct Deposit receives USDT on TRON (TRC20) at HyoNova's own Binance deposit address and credits it to the paying company's HyoNova Balance. It is not Binance Pay: there is no merchant checkout and no webhook. HyoNova asks each payer for an exact amount, reads the Binance account's deposit history with a read-only API key and matches deposits itself.

Set up#

Credentials go to the provider secret store. Control Center shows only whether each is set (and a masked hint of the key), never the value; nothing is logged or audited with a credential.

Address mode#

• api_verified (default): the worker re-verifies the account — permissions, address, network status — every 10 minutes.
• manual_pinned: verified by the connection test and once a day.

In both modes a mismatch blocks the provider: routing reports it unusable, companies cannot start new crypto payments, and a critical alert opens.

How a payment is matched#

Each payment session gets an exact amount: the dollar value plus a unique fingerprint in the last four micro-digits (20.000000 + 0.003817 = 20.003817 USDT). A fingerprint is reserved per deposit address while the session is open and for the quarantine afterwards, so two recent sessions never share one. When a deposit arrives HyoNova checks asset, network and address, then looks for the one session whose fingerprint matches and whose reservation covered the deposit time. One candidate → matched; none → unmatched; several → review. There is no closest-amount guess and a transaction id claimed by a customer is never proof.

Money becomes available only when Binance reports the deposit Success (status 1). Pending, credited-but-locked and waiting-for-confirmation deposits show as pending.

Crypto deposits#

Payments & Billing › Crypto deposits lists every deposit read from Binance, with tabs All · Pending · Matched · Unmatched · Late · Review, amount, network, organization, credited value, received time, Binance status and transaction id.

• Sync now reads the account immediately (the worker does it every 10–15 s while payments are open).
• Reconcile compares Binance's successful deposits with HyoNova's records and the ledger (below).
• Assign to organization — for an unmatched or reviewed deposit that Binance finalized. Needs billing.manage, a step-up and a reason. The whole deposit goes to that company's balance once; a second assignment is refused by the database. Confirm the payer with the customer before assigning.
• Close — for money that is not a customer payment (for example HyoNova's own transfer). It never reaches a balance.

Review reasons: no fingerprint in the amount, no matching session, several sessions match, wrong asset, wrong network, another address, unexpected memo/tag, malformed amount, unusually large amount (over $100,000), the same transaction already credited, amount changed at Binance.

HyoNova Balances#

Payments & Billing › HyoNova Balances shows the total wallet liability (what companies hold — never revenue), top-ups today and this month, balance spending this month (counted as revenue through invoice payments), pending / unmatched / review / late deposits, Binance sync health with the last sync and free fingerprints, and the open alerts. Open a company for its ledger (every entry with operator and reason), deposits and payment sessions.

Adjust balance credits or debits a balance with a step-up, a reason and an idempotency key. A debit can never take a balance below zero. Every adjustment is a new ledger entry; history is never edited.

Reconciliation#

Runs every 6 hours and on demand. It reports — never repairs — these findings as reconciliation attention items and raises a critical alert:

Alerts#

Binance rejected the key · deposit sync stale · repeated rate limits · repeated sync failures · configured address differs · deposits or network suspended · key can withdraw · key has trading/transfer permissions · unmatched deposits older than a day · fingerprint pool low or exhausted · reconciliation mismatch. Alerts clear themselves when the condition is gone; an operator can also resolve one with a reason.

Incidents#

• Withdraw permission appears — the provider is blocked automatically. In Binance, delete the key, create a read-only one, configure it and test. Review the account's withdrawal history in Binance.
• Address mismatch — do not enable. Confirm in Binance which address is correct; payments already sent to the old address appear under Review for assignment.
• Sync failing — check the alert reason (credentials, IP restriction, rate limit). HyoNova backs off automatically and keeps the cursor; nothing is lost when sync resumes.
• Fingerprint pool exhausted — new crypto payments are refused safely. Shorten the quarantine only if you understand the risk of reuse; most often the pool recovers as quarantines end.

Status#