Test modeWhitechain Sepolia· WB Soul verification is simulated · test USDT only
tazor

Approvals

What an approval signs, when two are needed, and how a second approver joins.

An approval is a passkey signature over one exact payment: the invoice hash, the buyer account, the payee, the amount, an expiry and a nonce. The payment contract checks each approval before any USDT moves.

Before you sign

Your device rebuilds the payment from the invoice link and compares its digest with the contract's. Your passkey is only requested if they match, so you approve exactly what you see.

One approver or two

  • Below your company's threshold, one approver is enough.
  • Above it, two approvers must approve, and they must be different WhiteBIT-verified people.
  • For a payment run, the threshold applies to the run's total.

Add a second approver

  1. Approve on your device. The page shows your approval as a short block of text.
  2. Send it to the second approver, who opens the same payment link and approves.
  3. Paste their approval into the page, then choose Pay.

Rules that still apply

  • An approval expires 30 days after the invoice's due date.
  • An approver on the company's revocation list is refused, even with a valid signature.
  • A backup signer's approval counts the same as a passkey approval.
Approvals are bound to the invoice hash, so changing any detail of the invoice makes them invalid.