Batch and Settlements

Learn how to manage batch processing and settlement operations with Koard's payment platform.

Get started with Koard

Koard 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, Koard offers flexible solutions to meet your settlement needs.

What you learn

In this guide, you'll learn:

  • How Koard'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 Koard's settlement APIs

Before you begin

This guide covers batch processing and settlement management in Koard. For a better understanding of how to process payments, see our Running Payments guide. If you're ready to start accepting payments, see our Getting Started guide.

Batch Processing Overview

Koard 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: Koard handles all timing and retries
  • Per-Merchant Batching: Batches are created per unique MID and TID combination

Two Main Workflows

Koard 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 Koard transactions to your already open batches
  • Trigger Batch Closure: Close batches using your existing system
  • Inform Koard: Update Koard'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 Koard's batching system.

Exception: If you've created specific MID and TID combinations for Tap to Pay through Koard, you can safely use Koard's batching system without the above concerns.

Everyone Else

Recommended approach: Use Koard's settlement system

If Koard is your sole authorization layer and you don't have existing batching infrastructure:

  • Full Settlement Management: Let Koard handle all batch processing
  • Automated Scheduling: Koard 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 Koard handles automatically
Settlement Scheduling Automated timing and retries Your existing schedule Koard manages timing
Error Handling Robust retry logic and error recovery Your error handling Koard handles retries
Reporting Batch and settlement analytics Your reporting system Koard provides reports
API Access RESTful APIs for batch management Limited to status updates Full API access

Getting Started

  1. Determine Your Workflow: Choose between enterprise or platform approach
  2. Set Up Integration: Configure your chosen workflow
  3. Test Batch Processing: Verify your implementation
  4. Monitor Operations: Track batch and settlement status

Best Practices

For Enterprise ISVs and PSPs

  • Maintain Existing Batches: Don't create separate batches for Koard transactions
  • Sync Settlement Data: Keep Koard 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 Koard APIs: Leverage Koard's comprehensive batch management
  • Monitor Settlement Status: Track batch processing through Koard'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: