Feature Request: Bulk void/commit API for inflight transactions

[ShivamGupta-SM]

Problem

Currently, to void or commit multiple inflight transactions, we need to make N separate API calls:

PUT /transactions/inflight/hold_001  → void
PUT /transactions/inflight/hold_002  → void
PUT /transactions/inflight/hold_003  → void
... N calls

This is inefficient for batch operations like:

• Cron jobs expiring multiple holds at once
• Bulk cancellations
• Mass void/commit processing

Proposed Solution

Add a new bulk endpoint:

PUT /transactions/inflight/bulk

Request Body

{
    "transaction_ids": ["txn_001", "txn_002", "txn_003"],
    "status": "void"
}

Response

{
    "batch_id": "batch_xyz",
    "status": "completed",
    "succeeded": 148,
    "failed": 2,
    "errors": ["txn_099: already voided", "txn_123: not found"]
}

Implementation Suggestion

Following the existing ProcessTransactionInBatches pattern with worker pools:

1. Add BulkInflightUpdate model in model/transaction.go
2. Add route transactions.PUT("/inflight/bulk", a.BulkUpdateInflightStatus) in api/api.go
3. Add handler in api/transactions.go that validates and delegates to service
4. Add BulkUpdateInflight method in transaction.go using existing VoidWorker/CommitWorker

This reuses the existing concurrent processing infrastructure.

Use Case

Any application with scheduled expiration of inflight holds needs to void them in bulk. Individual API calls create unnecessary overhead when processing 100+ transactions.

Happy to submit a PR if this feature is accepted!

[jerry-enebeli]

Hi @ShivamGupta-SM, you can achieve this by leveraging the bulk transaction feature.

You can batch your transactions using the bulk transaction endpoint, then call the commit (or void) endpoint with the batch ID. This will commit or void all inflight transactions in the batch at once.

Hope this helps!

[jerry-enebeli]

Additionally, for inflight expiry, you can pass an expiration_date, and any transactions that haven’t been committed by then will be automatically voided.

[ShivamGupta-SM]

Thanks @jerry-enebeli for the quick response!

I checked the bulk transaction docs, but unfortunately it doesn't solve my use case. Here's why:

My Scenario

Transactions are created individually over time, not in a single batch:

Day 1: User A enrolls → POST /transactions (inflight) → txn_001
Day 2: User B enrolls → POST /transactions (inflight) → txn_002
Day 3: User C enrolls → POST /transactions (inflight) → txn_003
... 
Day 30: 100 transactions created individually

Each transaction has its own unique ID, no common batch_id.

The Problem

When these expire, I need to void them:

PUT /transactions/inflight/txn_001  → void
PUT /transactions/inflight/txn_002  → void
PUT /transactions/inflight/txn_003  → void
... 100 API calls

Why Existing Solutions Don't Work

Solution	Why it doesn't fit
Bulk create + batch_id void	Transactions aren't created together - they come in over days/weeks
inflight_expiry_date	Expiry date can change midway (admin extends deadline, user gets extra time, etc.)

What I Need

Bulk void/commit by transaction IDs (not batch_id):

PUT /transactions/inflight/bulk
{
  "transaction_ids": ["txn_001", "txn_002", "txn_003"],
  "status": "void"
}

This would allow voiding multiple independently-created transactions in one call.

Is this something that could be added? Happy to submit a PR!

[jerry-enebeli]

Got it, @ShivamGupta-SM! It's clear now. Okay, I'd appreciate the PR for sure.

I'll be on standby to review it when ready. Thanks.