$PAYCHECKCA pendingBuy@paycheck
$PAYCHECKCA pendingBuy@paycheck
$PAYCHECKCA pendingBuy@paycheck
$PAYCHECKCA pendingBuy@paycheck
$PAYCHECKCA pendingBuy@paycheck
$PAYCHECKCA pendingBuy@paycheck

Learn

Security

OCR is not money. The hard problems are partners, duplicates, returns, and compliance. Links below go to the primary rules and guidance we design against.

Image quality gates

Corners, resolution, glare, blur, cropping, front/back, MICR visibility, and frame coverage before OCR runs.

Duplicate presentment

MICR identity plus image similarity — because check numbers and metadata can be altered by scammers.

Risk score on every check

Fraud signals drive hold windows. Crypto leaves treasury only after clearance confidence is earned.

Returns-safe design

NSF, stop payment, altered, or unauthorized returns fail the deposit if crypto was never released.

Sensitive data minimization

Routing and account data are encrypted/tokenized with minimized retention — never stored casually.

Partner rails

Production uses sponsor bank / RDC processors and regulated crypto infrastructure — not DIY banking.