Batch and Settlements
Learn how to manage batch processing and settlement operations with Netevia's payment platform.
Merchant setup and production configuration are coordinated by Netevia during partner onboarding.
Netevia provides comprehensive batch processing and settlement management for transactions processed through our system. Whether you're an enterprise ISV, PSP, or building a payment platform, Netevia offers flexible solutions to meet your settlement needs.
What you learn
In this guide, you'll learn:
- How Netevia's batch processing system works
- The two main workflows for different business types
- How to retrieve batch information and settlement data
- Best practices for enterprise vs. platform implementations
- How to integrate with Netevia's settlement APIs
Before you begin
This guide covers batch processing and settlement management in Netevia. For a better understanding of how to process payments, see our Running Payments guide. Merchant setup and production configuration are coordinated by Netevia during partner onboarding.
Batch Processing Overview
Netevia can run batches and settlements for transactions processed through our system. Our platform handles all scheduling and retries automatically, providing you with:
- Batch Lists: Retrieve comprehensive batch information
- Batch Components: Detailed breakdown of batch contents
- Settlement Breakdown: Success and failure analysis
- Automated Scheduling: Netevia handles all timing and retries
- Per-Merchant Batching: Batches are created per unique MID and TID combination
Two Main Workflows
Netevia supports two distinct workflows based on your business model and technical requirements.
Enterprise ISVs and PSPs
Recommended approach: Use your own batching solution
For enterprise ISVs and PSPs with existing batching infrastructure, we recommend maintaining your own batch processing and settlement management:
- Append to Existing Batches: Add Netevia transactions to your already open batches
- Trigger Batch Closure: Close batches using your existing system
- Inform Netevia: Update Netevia's systems when settlements occur
- Avoid Duplicate Issues: Prevents duplicate batch IDs and synchronization problems
Important: For TSYS, Fiserv, and Elavon processors, there's a high risk of duplicate batch IDs, out-of-order synchronization, and missing/invalid tags that may fail batches when using Netevia's batching system.
Exception: If you've created specific MID and TID combinations for Tap to Pay through Netevia, you can safely use Netevia's batching system without the above concerns.
Everyone Else
Recommended approach: Use Netevia's settlement system
If Netevia is your sole authorization layer and you don't have existing batching infrastructure:
- Full Settlement Management: Let Netevia handle all batch processing
- Automated Scheduling: Netevia manages timing and retries
- Simplified Integration: Single API for all settlement operations
- Comprehensive Reporting: Built-in analytics and monitoring
Key Features
| Feature | Description | Enterprise ISVs | Platform Users |
|---|---|---|---|
| Batch Creation | Automatic batch creation per MID/TID | Use your own system | Netevia handles automatically |
| Settlement Scheduling | Automated timing and retries | Your existing schedule | Netevia manages timing |
| Error Handling | Robust retry logic and error recovery | Your error handling | Netevia handles retries |
| Reporting | Batch and settlement analytics | Your reporting system | Netevia provides reports |
| API Access | RESTful APIs for batch management | Limited to status updates | Full API access |
Getting Started
- Determine Your Workflow: Choose between enterprise or platform approach
- Set Up Integration: Configure your chosen workflow
- Test Batch Processing: Verify your implementation
- Monitor Operations: Track batch and settlement status
Best Practices
For Enterprise ISVs and PSPs
- Maintain Existing Batches: Don't create separate batches for Netevia transactions
- Sync Settlement Data: Keep Netevia informed of settlement status
- Handle Edge Cases: Implement proper error handling for processor-specific issues
- Monitor for Duplicates: Watch for duplicate batch IDs across systems
For Platform Users
- Use Netevia APIs: Leverage Netevia's comprehensive batch management
- Monitor Settlement Status: Track batch processing through Netevia's dashboard
- Implement Webhooks: Set up real-time notifications for settlement events
- Regular Reconciliation: Verify settlement data against your records
Integration Points
- API Integration: RESTful APIs for batch management and status updates
- Webhook Notifications: Real-time batch and settlement status updates
- Dashboard Monitoring: Visual tracking of batch processing and settlements
- Reporting Tools: Comprehensive analytics and settlement reports
See also
This wraps up the batch and settlements overview. See the links below for detailed implementation guides:
- Running Batches - Step-by-step batch implementation
- Running Payments - Payment processing fundamentals
- Setting up Webhooks - Configure webhooks to receive real-time batch and settlement event notifications
