Add employees and their Stellar wallets, review one payroll with an exact total, and sign. Each employee gets their own transaction, and it only turns green once the ledger says so.
A slow answer or a timeout is never treated as paid. Before a payment turns successful, OrgPay reads the transaction back from Stellar and checks it, line by line.
Stellar charges a tiny fee in XLM per payment. Drag the slider to see a run your size.
OrgPay builds each transaction unsigned. You sign in Freighter. It never sees, stores or logs a secret key.
Double clicks, retries and slow answers get the same transaction back. A successful payment is never sent again.
Only the ledger’s record, checked against the payment, turns it green. Anyone can re-check it.
A wallet that can’t receive is caught before signing, with the reason and a one-click retry.
| Situation | Sending one by one | OrgPay |
|---|---|---|
| Total before paying | A spreadsheet | Exact, to 7 decimals, on a double rule |
| Wallet that can’t receive | You find out after | Caught at review; never sent |
| Clicked twice | Paid twice | Same transaction, sent once |
| Proof for each person | Dig through history | A hash and memo per payment, verified |
No. Money stays in your funding wallet until you sign. OrgPay builds each transaction unsigned; you sign it in Freighter and your secret key never leaves it.
Nothing extra. A run can be executed once, and while a transaction is open you always get that same one back. A successful payment is never sent again.
It’s caught at review, before anything is signed. That payment is marked failed with the reason, nothing is sent, and you can retry once their wallet is fixed.
Only after OrgPay reads the transaction back from Stellar and it matches: the hash, the funding wallet, the employee’s wallet, the asset and the exact amount.
Not yet. OrgPay runs on Stellar Testnet with Circle’s Testnet USDC, which has no value.
Free on Stellar Testnet. Bring a funding wallet and a few employees.