improved

New Transaction Actions, Batch Support, Statuses & More

We’ve rolled out a major update to our transaction system to support more precise control, improved integrations, and richer status reporting. These changes follow the previous announcement of breaking changes to transaction statuses and are now live in production.


New Transaction Actions: AUTHORIZE, CAPTURE, VOID, and REFUND

We're introducing new explicit transaction actions to give you fine-grained control over payment flows:

  • AUTHORIZE
    Initiates a hold on the customer’s funds without queuing the transaction for settlement. This is the first step of the traditional CHARGE flow.

  • CAPTURE
    Captures a previously authorized amount and tells the payment gateway to begin the settlement process.

  • VOID
    Cancels an authorization before settlement. Commonly used for credit card transactions where funds were authorized but not yet captured.

  • REFUND
    Explicitly returns funds from a completed charge. You no longer need to rely solely on REVERSAL.

These actions provide greater transparency and flexibility compared to our previous abstraction layers.


Batch Processing Enhancements

We’ve introduced batch support to make processing multiple transactions easier and more powerful:

  • New Endpoint
    POST /v3/accounts/{account-id}/transactions
    Submit a collection of transaction actions in a single API call. These can include a mix of AUTHORIZE, CAPTURE, VOID, REFUND, and other supported actions.

  • SFTP File Support
    Our batch SFTP format has been updated to support all new action types. You can now intermix actions such as AUTHORIZE and CAPTURE within a single file.

Documentation coming shortly.


Expanded API Paths

New endpoints for managing transactions per customer:

  • GET/POST /v3/accounts/{account-id}/customers/{ref}/transactions
  • GET/POST /v3/accounts/{account-id}/customers/{ref}/transactions/{transaction-id}

Documentation coming shortly.


Expanded and Improved Status Handling

We've modernized and enriched our transaction status model:

  • Deprecated Status

    • APPROVED is now deprecated in favor of more specific statuses.
  • New Action-Centered Statuses

    • AUTHORIZED
    • CAPTURED
    • VOIDED
    • REFUNDED
    • PAIDOUT
  • External Lifecycle Statuses

    • SETTLED
    • FUNDED

These statuses reflect both internal process steps and externally sourced state transitions.


Real-Time and Near Real-Time Status Updates

We’ve significantly improved how often statuses are refreshed:

  • Transaction statuses are now kept in sync with external systems, typically within 15 minutes in the worst case.
  • We’ve also added support for real-time status updates and ledger transactions from providers.

Stay tuned to your provider’s integration roadmap as these capabilities roll out.


Looking Ahead

These updates are part of a broader initiative. Much of the underlying work has been architectural in nature, enabling both the features released today and additional enhancements planned in the near future. More changes are coming soon!


For migration guidance or historical context, refer to our previous changelog on upcoming transaction status changes.