Transaction lock across authorize, capture, charge, refund, reversal, void, and payout

Transactions: authorize, capture, charge, refund, reversal, void, and Payout handling now apply a transaction lock on every path, so retried or concurrent requests for the same payment are less likely to run twice.

• Overlapping authorize, capture, or charge calls are blocked before a duplicate hold, capture, or charge is processed.
• Overlapping or repeated refund, reversal, or void calls are blocked before a duplicate action is processed.
• Retried or concurrent payout calls for the same payment are blocked before a second disbursement is created.
• Transaction history stays aligned with the payment action you intended to run.