Feature

Stored partner information on the merchant file in DynamoDB for integration with the batch-coordinator-service.

Feature

Added userId to transaction records when initiated by a merchant, whether through a main action or a ledger transaction.

Bug Fix

Corrected event display issues on the timeline view and applied related UI updates for consistency.

Bug Fix

Fixed an issue where Error was returned as an empty object when null, which violated expected API contract behavior.

Bug Fix

Resolved marshalling errors by enabling removeUndefinedValues to clean up undefined fields during processing.

We’ve extended our parallel APPROVED status broadcast beyond CHARGED and CAPTURED. It now also includes:

• PAIDOUT for PAYOUT action.
• VOIDING for REVERSAL or VOID actions.
• REFUNDING for REVERSAL or REFUND actions.

This is part of our transitional support for downstream systems during the new status rollout.

Refer to our original update here for context on the 90-day support window, starting July 8, 2025.

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.

July 2025 – Product Action Mappings
Lock Date: 2025-07-01

Ticket: CC-727 – Implement CreditCard Mappings for Charge and Reversal of Bank of America Gateway
Date: 2025-07-01
Issue:
The Bank of America credit card gateway lacked product-action mappings for Charge and Reversal actions, limiting post-auth lifecycle handling.
Fix:
Product-action mappings were implemented for both Charge and Reversal to ensure compatibility with the platform’s credit card lifecycle logic.
Link: https://developer.authvia.com/v3.3/reference/payments-creditcard-bankofamerica

Ticket: N/A – Updated CRM mappings for Email for Stripe Gateway
Date: 2025-07-03
Issue:
The email field in CRM payloads was not properly mapped for the Stripe gateway, causing incomplete customer records during CRM sync.
Fix:
CRM mapping for Stripe has been updated to ensure email fields are consistently passed through the system.
Link: https://developer.authvia.com/v3.3/reference/payments-creditcard-stripe

Ticket: CC-749 – Add Payout Token Mock Product (Stripe)
Date: 2025-07-07
Issue:
Stripe’s tokenization lacked support for mocking payout tokens in development/test environments.
Fix:
Added a mock product definition to support payout token testing through Stripe mapping.
Link: https://developer.authvia.com/v3.3/reference/payments-token-stripe-authorizeonly

**Ticket: CC- 760 - Stripe – Charge Status Mapping Update (Authorize Only)
Date: 2025-07-08
Change:
Corrected the mapping for Charge status to return Approved for Stripe Authorize Only gateway configurations.
Link: https://developer.authvia.com/v3.3/reference/tokenize-creditcard-stripe-authorizeonly

Ticket: CC-727 – Implement CreditCard Mappings for Charge and Reversal of Bank of America Gateway
Date: 2025-07-09
Note:
This release reconfirms the 7/1 deployment and activation of mappings for Charge and Reversal.
Link: https://developer.authvia.com/v3.3/reference/payments-creditcard-bankofamerica

Ticket: CC-763 – Updated Mappings for Using Role as per new Syntax in Worldpay (Vantiv) and Bank of America
Date: 2025-07-14
Issue:
New role-based action syntax was not properly handled in Worldpay and Bank of America gateways, resulting in authorization mismatches.
Fix:
Updated mapping logic to align with new role-based syntax format.
Link (Worldpay): https://developer.authvia.com/v3.3/reference/payments-token-vantiv-creditcard
Link (Bank of America): https://developer.authvia.com/v3.3/reference/payments-creditcard-bankofamerica

Ticket: CC-765 – Update Mapping of Card Authorization for SessionID of Fingerprint Device for Bank of America Gateway
Date: 2025-07-16
Issue:
SessionID from fingerprint devices was not being passed during card authorization.
Fix:
Mapping now includes SessionID to support fingerprint device workflows.
Link: https://developer.authvia.com/v3.3/reference/payments-creditcard-bankofamerica

Ticket: CC-767 – Update Receive Mapping of Message Text Body for Infobip RCS
Date: 2025-07-17
Issue:
The Infobip RCS receive mapping did not properly handle the message text body, causing payload issues.
Fix:
Updated receive mapping to properly map text.body in Infobip RCS.
Link: https://developer.authvia.com/v3.3/reference/messaging-rcs-infobip

Mock – Load Mapping File for Payouts
Date: 2025-07-18
Ticket: CORE-4516
Change:
Added a load mapping file for the mock provider to support payout workflows.
Link: https://developer.authvia.com/v3.3/reference/payouts-token-mock

Orbital – Tokenization Authorization and Capture
Date: 2025-07-19
Ticket: CC-708
Change:
Implemented tokenization, authorization, and capture features for the Orbital gateway.
Link: https://developer.authvia.com/v3.3/reference/payments-creditcard-orbital

Bug Fix

Sanitized the messaging context by omitting excessively large values that could lead to message delivery failures.

Bug Fix

Filtered out disabled products when selecting a product for an Object to prevent invalid associations.