Security
Moving digital assets is irreversible. Payrolloc is designed so that every payment is checked, approved and recorded before it leaves a wallet whichever custody model you choose.
The request comes from a permitted user or API key.
Addresses, assets, networks and amounts are checked.
The destination is an approved beneficiary address.
Limits and rules for this payment are applied.
The required quorum has signed off.
The full history is written to the audit log.
Security controls
Rules by amount, asset, network, destination, team or source wallet evaluated on every request.
Separate permissions to create, edit, approve, execute and view, scoped per workspace and wallet.
The person who creates a payment cannot be the one who approves it.
Funds can only be sent to addresses approved on a beneficiary profile; changes require approval.
Caps per payout, per period and per wallet keep automation and people within agreed bounds.
Every login, edit, approval, rejection and execution recorded with user, time and context.
Multi-factor authentication for users and scoped, revocable keys for API access.
Separate wallets per entity, team or purpose, each with its own permissions and policies.
Event payloads are signed so your systems can verify they came from Payrolloc.
Custody models
Choose per wallet. Policies, approvals and audit logging apply identically across both.

Running a vendor assessment? Our team can walk your security and compliance stakeholders through Payrolloc's architecture and controls.
If you believe you have found a vulnerability, please report it privately to security@payrolloc.com so we can investigate.
get started
See how Payrolloc automates, approves, executes and reconciles recurring crypto payments for your team.