Operation Concept

An Operation represents a discrete event or action taken on a Transaction. Multiple operations can accumulate on a single transaction, providing a detailed audit trail of how the transaction progresses from the initial authorization to capture, void, refund, and beyond. This granular record is accessible in the Portal’s transaction details view, offering insight into every step of the transaction’s lifecycle.

Key Fields (Portal View)

Field	Description
id	Unique identifier for this operation.
Operation Type	The specific action taken. See Operation Types below.
Transaction ID	The original transaction to which this operation belongs.
Amount	The monetary amount associated with this operation (in the smallest currency unit, e.g., cents for USD).
Currency	The three-letter ISO currency code for the operation’s currency (e.g., USD, EUR).
Created At	Timestamp (UTC) indicating when the operation was performed.
Reason	(Optional) Additional information explaining why the operation occurred (e.g., reason for a void or partial capture).
Operator	(Optional) Identifies who or what initiated the operation (e.g., user in the Portal, automated process, or API call).

Note: In the database, operations may also track internal fields like TrxID, TrxType, Operation Origin, and more. However, these internal details are not directly exposed via public API endpoints. Merchants can view a subset of this information when viewing transaction history in the Portal.

Operation Types

• authorize: A request to hold funds (no immediate capture).
• authcap: An authorization combined with an immediate capture of the total amount.
• partial_capture: Capturing only a portion of the total authorized amount.
• capture: A full capture of all authorized funds.
• void: Canceling the authorization before capture.
• refund: Reversing funds back to the customer for a completed (captured) transaction.
• expire: Automatically releasing the hold on funds after the authorization period lapses.

How to View Operations

Since the API does not expose an endpoint to fetch operations directly, the Portal serves as the primary tool for merchants to view these records. Within a transaction’s details page, you’ll find a timeline or list of all operations performed on that transaction, along with timestamps, amounts, and any relevant notes.

Why Operations Matter

• Audit Trail:
  Operations document every state change, enabling thorough reviews or investigations.

• Clarity & Debugging:
  If a transaction was partially captured or voided unexpectedly, the operation history explains exactly when and how it happened.

• Lifecycle Tracking:
  From initial authorization to final capture, each step is logged as a separate operation, providing a chronological account of the transaction’s journey.