$PENDRY · Solana
RECURRING
PAYMENTS
ONCHAIN.
Recurring payments, programmed once. Wallet owners define the recipient, amount, schedule, and spending limits. Pendry turns those terms into a clear recurring-payment mandate.
Set the terms once.
A standing order for self-custody. You decide the rules. Pendry keeps the schedule legible, limited, and verifiable.
A fixed recipient wallet chosen by the payer. Recipient changes require a new authorization.
Define the amount per payment plus a maximum lifetime authorization.
Daily, weekly, or monthly schedules with a clear start date and payment count.
Recurring payments should be narrow by design, with pause and cancellation available to the payer.
Readable from authorization to receipt.
The schedule is not hidden behind a broad spending permission. Every due payment has terms.
Create
Choose recipient, asset, amount, frequency, start date, and limits.
Authorize
The wallet owner approves the recurring-payment mandate under those defined limits.
Execute
When a payment is due, an executor can trigger execution. The protocol validates the original terms.
Verify
Completed payments can be represented as clear receipts and a schedule history.
Working utility · Local draft tool
Build a Pendry schedule.
Use the planner to calculate a recurring-payment mandate before any onchain action. It can read an injected Solana wallet public key, validate Solana addresses, calculate the schedule, copy a human-readable mandate, and export the draft as JSON.
Recurring money movement without monthly repetition.
Rent. Payroll. Suppliers. Treasury transfers. Savings. Allowances. One payment rail, defined by the payer.