Documentation Index
Fetch the complete documentation index at: https://docs.xentfi.com/llms.txt
Use this file to discover all available pages before exploring further.
Overview
Why Use Deposit Addresses?
๐ฏ Payment Tracking
Each address is unique per customer or invoice, making it easy to identify who paid and for what
๐ Automated Reconciliation
Match incoming payments to specific customers automatically without manual intervention
๐ Privacy & Security
Customers donโt share addresses; each transaction uses a unique address for better privacy
๐ Analytics
Track payment behavior per customer, identify trends, and optimize your payment flow
How It Works
Use Cases
Per-Customer Addresses
Assign a permanent deposit address to each customer for recurring payments:| Use Case | Benefit |
|---|---|
| Subscription billing | Same address for all subscription payments |
| VIP customers | Faster checkout experience |
| Business accounts | Easy reconciliation per client |
Per-Invoice Addresses
Generate a unique address for every invoice:| Use Case | Benefit |
|---|---|
| One-time payments | Clear payment-to-invoice mapping |
| Marketplace settlements | Track which order paid |
| Event tickets | Match payment to specific attendee |
Refund Addresses
Whitelist addresses for processing refunds:| Use Case | Benefit |
|---|---|
| Customer refunds | Pre-verified addresses only |
| Exchange withdrawals | Secure withdrawal destinations |
| Partner payouts | Automated distribution |
Creating Deposit Addresses
Basic Creation
Address Lifecycle
Whitelisting External Addresses
For addresses you own (exchange accounts, other wallets), you can whitelist them:Benefits of Whitelisting
| Benefit | Description |
|---|---|
| โ Security | Prevents sending to unauthorized addresses |
| โ Faster withdrawals | Pre-approved addresses skip verification |
| โ Audit trail | Track all withdrawal destinations |
| โ Compliance | Meet regulatory requirements |
Address Monitoring
Enable Monitoring
Get real-time notifications when your deposit address receives funds:What Gets Tracked
| Event | Description | Webhook Event |
|---|---|---|
| Payment received | First confirmation | payment.detected |
| Payment confirmed | Block confirmation | payment.confirmed |
| Payment completed | Settlement finalized | payment.completed |
| Payment failed | Transaction failed | payment.failed |
Transaction History
View all transactions for a specific deposit address:Address Management Best Practices
- Naming Convention: Use consistent naming like
customer_{email}orinvoice_{id} - Metadata: Store additional info (customer ID, order ID) in metadata field
- Monitoring: Enable for all production addresses
- Retention: Keep address records for audit purposes
- Cleanup: Deactivate unused addresses periodically
Address vs Payment Link
| Feature | Deposit Address | Payment Link |
|---|---|---|
| Best for | Recurring customers, API integration | One-time payments, marketing campaigns |
| Customer experience | Copy/paste address | Hosted payment page |
| Payment methods | Crypto only | Crypto + Wallet Connect |
| Tracking | Per address | Per link |
| QR code | Can generate manually | Auto-generated |
| Expiration | Permanent | Configurable |
Reconciliation Strategies
Per-Customer Strategy
Per-Invoice Strategy
Security Considerations
| Risk | Mitigation |
|---|---|
| Address reuse | Generate new addresses per customer/invoice |
| Typo errors | Validate addresses before whitelisting |
| Phishing | Use consistent naming and verification |
| Key compromise | Rotate API keys, monitor suspicious activity |
| Wrong network | Display network warnings to customers |
Dashboard View
The deposit addresses dashboard shows all your addresses with real-time status.
Common Patterns
E-commerce Checkout
- Customer places order
- Create deposit address with order ID in name
- Display address to customer
- Monitor for payment
- Update order status on webhook
Subscription Billing
- Customer signs up
- Create permanent deposit address for customer
- Store address in customer profile
- Customer uses same address for all payments
- Webhook triggers subscription renewal
Crypto Payroll
- Employee onboarded
- Whitelist employeeโs personal wallet
- Set up auto-settlement to whitelisted address
- Payroll automatically distributed
Troubleshooting
Address not receiving payments
Address not receiving payments
Possible causes:
- Wrong network selected
- Address not activated
- Blockchain congestion
- Verify network matches senderโs network
- Check address status in dashboard
- Wait for block confirmations
Webhook not triggered
Webhook not triggered
Possible causes:
- Monitoring not enabled
- Webhook URL not configured
- Network issues
- Enable monitoring for the address
- Verify webhook configuration
- Check webhook logs
Wrong amount received
Wrong amount received
Possible causes:
- Sender sent wrong amount
- Decimal place confusion
- Gas fee deduction
- Verify expected amount
- Check token decimals
- Review transaction details
Performance Metrics
| Metric | Target | Description |
|---|---|---|
| Address creation time | < 1 second | Time to generate new address |
| Payment detection | < 10 seconds | Time to detect incoming payment |
| Confirmation time | Network dependent | Time for block confirmations |
| Webhook delivery | < 5 seconds | Time to send webhook notification |
Pricing & Limits
| Plan | Max Addresses | Monitoring | Support |
|---|---|---|---|
| Starter | 100 | Basic | |
| Professional | 1,000 | Advanced | Priority |
| Business | 10,000 | Premium | Dedicated |
| Enterprise | Unlimited | Custom | 24/7 |
Related Products
Master Wallets
Parent wallet management and treasury
Payment Links
Hosted payment pages for one-time payments
Webhooks
Real-time payment notifications
Next Steps
- Set up webhooks for real-time payment notifications
- Configure auto-settlement for automatic fund distribution
- Review API Reference for complete endpoint documentation

