Loops HouseDuly

NEAR HACKATHON
Links
Team
1 member- HAOwner
Harshit Singh
Overview
Freelancers and small businesses get paid across chains in the wrong token, lose track of which invoice a payment was for, and spend money that belongs to the tax office or a subcontractor. Duly is pay-by-link invoicing: the client pays with any major token on any major chain, and the business receives USDC on NEAR with no wallet app and no NEAR for gas.
NEAR is how it works. NEAR Intents (1Click, exact output) converts the payment and delivers USDC to our contract by ft_transfer_call with the invoice id in msg, so the payment itself closes the invoice in ft_on_transfer. No server or webhook decides what is paid. In that same receipt the contract moves the tax share and each subcontractor's share into separate balances, before the business can spend them. Businesses sign in with a passkey that controls a NEAR implicit account and sign NEP-366 meta transactions; our relayer pays gas only for an allowlist of methods on our own contract. Client names and line items are encrypted in the browser: only the amount, dates and a SHA-256 fingerprint go on-chain, and the pay page refuses a document that does not match. Part payments, overpayments, refunds and a CSV an accountant can open are included.
It runs on NEAR mainnet as dulypay.near. On 2026-11-01 a 1.00 USDC payment from Base (https://basescan.org/tx/0x0429a3f18c6b1a8681afb92ab58fb595e82672d9f5ecd94af57204370c63fa9a) closed invoice 1-3 on-chain 31.8 s after the Base block and set aside 0.20 USDC in the same receipt (https://nearblocks.io/txns/GceCNYM3VvWnnN4x6ha7T9aU2j9PmzHyJnP6oc6pkreF); a payout and a refund went back to Base. node scripts/verify-mainnet.mjs re-checks every transaction from public RPCs (25 checks, no keys). Anyone can pay a real 0.10 USDC sample invoice at duly.swiftbotlab.workers.dev/i/1-4, or run the whole loop with test money and no wallet at /test/app. npm run reproduce runs 109 JS and 74 contract tests, positive controls, the mainnet check and a testnet loop.