Automate outbound payments by combining service accounts, policies, and webhooks. This solution covers service account setup, payment workflows, and high-volume considerations.Documentation Index
Fetch the complete documentation index at: https://docs.dfns.co/llms.txt
Use this file to discover all available pages before exploring further.
What you’ll need
- Understanding of policies
- Understanding of service accounts
- Webhook endpoint for status notifications
Components to configure
Service account
A service account provides machine identity for automated operations. Grant minimal permissions for payment operations. See the service account guide and API reference.Payment policies
Configure policies that control when automated payments need human review:- Small payments - May auto-approve with velocity limits for protection
- Large payments - Require human approval above threshold
- Unknown recipients - Require approval for addresses not in whitelist
Webhooks
Configure webhooks to track payment status in real-time:wallet.transfer.broadcasted- Transaction sent to networkwallet.transfer.confirmed- Transaction confirmedwallet.transfer.failed- Transaction failedpolicy.approval.pending- Approval needed
Transfer execution
Execute transfers via the API with your service account credentials. See how to create transfers and monitor status.Policy evaluation flow
When a payment is initiated, policies evaluate the transaction:Example configurations
Standard payment workflow
| Policy | Configuration | Action |
|---|---|---|
| Velocity limit | $100k/day | Block (safety cap) |
| Large payments | >$10k | Require 1-of-2 approval |
| New recipients | Not in whitelist | Require approval |
High-volume operations
For payment processors with high transaction volume:| Policy | Configuration | Action |
|---|---|---|
| Very large payments | >$500k | Require 2-of-3 approval |
| Hourly cap | $2M/hour | Block |
| Frequency limit | >1000 tx/hour | Block |
High-volume considerations
Rate limits
Dfns API has rate limits to ensure fair usage. For high-volume operations:- Check rate limits documentation for current values
- Implement queuing and backoff strategies
- Contact support if you need higher limits
Multiple hot wallets
Distribute load across multiple wallets for:- Higher throughput
- Balance management
- Risk distribution
Reliability
Build reliability into your payment system:- Use idempotency keys to prevent duplicates
- Implement retry logic with exponential backoff
- Set up monitoring and alerting
Related solutions
Automate deposits
User deposits and transfers
Define treasury policies
Spending limits and controls
Apply compliance controls
Transaction screening