You set the terms.
Choose the recipient, exact amount and optional executor. Fund the job in your wallet.
PAYMENT CONTROL FOR AGENT WORKFLOWS
Let agents work.
Keep payouts
under control.
Approve who gets paid and how much. Your agent can release that payout—but cannot change it or pay the same job twice.
Live on NEAR testnet. Test tokens only.
THE PAYOUT LATCH01 → 01
Owner approves0.001 NEAR
PL
Permission, locked in.Recipient + amount + executor
↳First executionPAID
↳Repeated executionBLOCKED ×
One job · one successful transferNEAR
A clear division of control.
Read the field guideThe agent follows them.
The owner or authorized executor releases the fixed payment. The job locks before the transfer.
The chain keeps the record.
Inspect the final state. Confirmed failures can be retried or refunded by the owner.
FOR TEAMS PAYING CONTRIBUTORS
Useful when an agent retries a task.
Essential when that task moves money.
YOUR PAYMENT DESK
Payouts.
Create, release and inspect your approved payments.
READY TO PAY—
PAID—
AVAILABLE PRINCIPAL—NEAR · loaded jobs
| PAYOUT / RECIPIENT | AMOUNT | STATUS | Details |
|---|
Your next payout starts here.
Connect your NEAR testnet wallet to approve your first job.
Already an executor? Look up the job below.
VERIFIABLE, NOT A SIMULATION
Show the receipts.
Real testnet transactions from our end-to-end verification.
DEPLOYED CONTRACT
Open explorer Loading contract…
Every wallet owns its own approvals. A job’s recipient and amount are immutable.
Loading recorded evidence…
What this proves
A concurrent execution race pays once. Replays are rejected. Confirmed transfer failures restore an approval. Only its owner can refund or change the executor.
Where the boundary is
This is a testnet prototype, not an audited financial product. A deployer upgrade key still exists. Protection applies per job ID; a new ID is a new approval.
Read the contract sourceA SHORT FIELD GUIDE
From approval
to paid.
A payment tool for humans and the agents they authorize.
THE WORKFLOW
01 — 04
01 — 04
Connect a testnet wallet.
Use Meteor Wallet on testnet. Create a separate test account and fund it with test NEAR. Your wallet approves transactions; PayoutLatch never asks for your seed phrase.
Open testnet walletApprove the exact payment.
Give the work a unique reference, choose an existing recipient and enter a NEAR amount. Optionally name an executor account for your agent. The wallet deposit is the principal plus a retained 0.02 NEAR storage reserve. Network gas is additional.
Release it—or delegate.
Open the job and release it yourself, or share its job ID with the named executor. The executor can call the contract’s execute method from code or this interface. It cannot change the amount or recipient.
Agent integration instructionsFollow the chain state.
Pending means the transfer is in flight. Paid means the callback confirmed delivery. If delivery fails, Approved means you may retry or cancel. Cancellation returns the principal to its original owner; storage and gas are not refunded.
The details that matter.
Why NEAR testnet?
The hackathon FAQ allows testnet-only projects in every track. This prototype uses a native NEAR contract, not a mainnet-only integration. Testnet lets reviewers exercise the complete flow without real-money exposure.
Can I undo a payment?
Only an Approved job can be cancelled. Paid transfers are final. While a transfer or refund is pending, the contract rejects another attempt. There is no manual force-unlock.
What does the executor get permission to do?
Only execute that job. Its recipient and amount are fixed. The owner can replace or revoke the executor while the job is Approved. The executor does not receive the owner’s wallet key.
Is PayoutLatch an AI agent?
PayoutLatch is the payment-control contract and interface. It includes a command-line executor that any agent can call. It does not claim to judge work quality or run an autonomous AI model.