Loops HouseOpenrail

NEAR HACKATHON
Links
Team
1 member- YOOwner
Young John
Overview
Problem: As a business owner, receiving payments across borders is still slow, costly and manual. A bank wire takes days and charges fees at each bank, plus an FX spread. Cards take about 3% and add chargebacks and payout holds. Either way, someone matches each payment to its invoice by hand. Invoices carry bank details by email, which is how "please pay our new account" fraud works. Stablecoins fix speed and cost, but bring new problems. The client holds USDT on Solana while the business wants USDC on Base. Payments arrive with no link to the invoice they pay. And on a public chain anyone can see a merchant's balance, revenue and clients. No business accepts that.
What we built: Openrail, a stablecoin payment rail on NEAR mainnet. A business sends an invoice or integrates it into their online store. The client pays in USDC or USDT from NEAR, Base, Arbitrum, Ethereum, Solana, Polygon, Optimism or BNB Chain without an account. The business is paid in USDC on its chosen chain. Funds from settled payments are moved to the NEAR Intents confidential balance of the business on their schedule, while every booking stays publicly verifiable. Openrail ships as a web app with receipts and statements, a REST API with signed webhooks, Shopify and WooCommerce plugins, a CLI and SDK, and an MCP server for AI agents. Real orders from both demo stores are booked on mainnet.
How NEAR fits in: every invoice is an NFT minted by openrail.near, and its token id names its own keyless sub-account. Money that lands there is a payment of that invoice: no memo, and no address anyone can swap. NEAR Intents swaps the client's coin into USDC on the way in, sends payouts out, and holds the confidential balance. A permissionless reconcile books each payment, takes a 0.25% fee and credits the NFT's holder. No Openrail service holds a business's money. The median from payment to booking is 30.5 s.
The README has step-by-step checks.