Concurrent capture and refund

Concurrent handling of captures and refunds allows DEUNA to manage multiple financial operations — specifically partial captures and refunds — that occur concurrently or in rapid succession on the same transaction.

This capability is essential for merchants operating in high-concurrency environments, where API calls may overlap in time.

This mechanism ensures that each operation is processed atomically and sequentially, avoiding race conditions and maintaining transaction state consistency across all involved services.

Key Capabilities

✅ Sequential locking mechanism: Guarantees that only one financial operation is processed at a time for the same transaction.
🔄 Support for concurrent requests: Allows handling multiple capture or refund requests for the same transaction without compromising integrity.
🧾 Audit and traceability: Each operation (capture or refund) is recorded with its timestamp, origin, and result.
💳 Compatibility with all PSPs: Works with all current integrations (for example, Fiserv, Kushki, MercadoPago) through a unified orchestration layer.

Integration Notes

1. No changes are required from the merchant side.
2. The existing /capture and /refund endpoints are fully compatible.
3. Concurrency handling is completely managed by DEUNA's internal infrastructure.

Limitations

This mechanism currently supports capture and refund operations. Authorizations and voids are not affected.