NearTap turns any NFC Android phone into a payment terminal. Hold two phones together, confirm with your fingerprint or passkey, and NEAR settles in about a second. Non-custodial, human-readable names, no card reader.
The receiver's phone emulates a card. The sender's reads it, confirms, signs on-device and broadcasts. Pick an amount and replay.
Animated simulation with sample data. On real devices it uses Android Host Card Emulation + reader mode.
Receiver types an amount. Their phone starts serving a one-time request: account, amount, token, nonce and a 5-minute expiry.
Sender holds their phone close. Reader mode selects NearTap's AID, reads the payload and shows a clear confirm sheet. Confirm with biometrics or passkey.
The transaction is signed on-device and sent to NEAR. The receiver watches the chain and shows a receipt with a NearBlocks link.
Already have a NEAR testnet account? Import it by secret key or seed phrase, or link a passkey so every payment needs your synced passkey too. No seed phrase living on the phone.
NearTapAddKey transaction signed by your original.Native Kotlin HostApduService with a custom AID serves the request; the payer's phone reads it with IsoDep reader mode. Payload is under 250 bytes, one short APDU. Handles NFC off and unsupported devices with settings shortcut and QR fallback.
Plain transfers over JSON-RPC with automatic fallback endpoint. Fast enough that the receipt lands while you're still holding the phones.
New testnet account, secret-key import, seed-phrase import, or passkey linking. Reveal or back up your secret key behind biometrics.
Non-custodial. Each key is AES-GCM encrypted by an Android Keystore key that needs fingerprint, face or PIN. Decrypted only in memory to sign.
Hold several accounts on one phone, switch in a tap and remove any of them. Removing deletes the key from the device.
Type bob.testnet, enter an amount on the built-in keypad. NearTap checks the account exists before you pay.
Every request is also a QR code. No NFC on one side? Scan instead. Receiver detects payment by watching the chain.
Recent transactions from NearBlocks plus on-device history, each row opens the testnet explorer.
Write a reusable pay-me request (fixed or open amount) to an NTAG213/215/216 sticker. A customer taps the sticker, not your phone, and NearTap opens straight to the confirm sheet.
Rust near-sdk contract: nonce replay protection, expiry and payment events for native NEAR. App works without it.
Tap phones (NFC), scan the receiver's QR, or send straight to a NEAR ID like cafe.testnet. Native NEAR on testnet.
Buzz on tap, success and failure. Pulsing NFC rings, a self-drawing check, soft transitions, switchable off.
System, White or Black, with NEAR green accents. True black for OLED.
Real screens captured from the NearTap app on testnet.
NearTap has no backend and no custody. Everything signs locally and talks straight to NEAR RPC.
Point NearTap at a small Rust contract and each tap becomes a one-time payment session.
payment events for indexerspayget_payment view gives the receiver an exact confirmationNeeds NFC with host card emulation, a secure screen lock, and arm64 (virtually every phone since 2017).
iOS doesn't let third-party apps act as a card toward another phone. Apple reserves card emulation for Apple Pay and approved partners, so a phone-to-phone tap like this can't run on iOS.
No NFC, or NFC off? The same request shows as a QR code that NearTap can scan. Emulators have no NFC, so test on real phones.
neartap.apk on your phone (or transfer it).No. NearTap only talks to NEAR testnet. Testnet NEAR has no value and is free from a faucet.
To try the NFC tap, yes: two Android 10+ phones with NFC, both running NearTap. With one phone you can still create accounts, send by name, show a QR and write a merchant sticker.
NEAR can't verify passkey signatures on-chain, so the passkey acts as a gate rather than the signing key. Linking proves ownership of your existing account once, adds a fresh device key on-chain, registers a passkey, and stores only that device key (encrypted in the Keystore). Each payment then needs the passkey and your biometrics. Restoring from a passkey alone on a new phone isn't supported — keep your backup. Passkeys need this site deployed on your own domain (it serves the assetlinks.json that proves the app owns the passkey domain); until then NearTap keeps the passkey switch off and everything else works. You can set your domain in Settings → Advanced.
Yes — with an ed25519: secret key or a 12/24-word seed phrase (derivation path m/44'/397'/0', same as common NEAR wallets). The account id is optional; NearTap can look it up from the key.
On your phone only. The seed is AES-GCM encrypted with a key held by the Android Keystore that requires biometric or PIN authentication, and is decrypted in memory just long enough to sign.
Requests carry a random nonce and a 5-minute expiry, and the payer confirms each one. With the optional session contract, the same nonce can never be paid twice. Merchant stickers are intentionally reusable.
Native NEAR on testnet. That's it for the hackathon build: one token, kept simple.
It's a hackathon build distributed as an APK. Sideload it by allowing unknown sources for the app you open it with.
Yes — the landing site is at github.com/abdulahaddayater/nearappweb.