Logs
Transaction logs are detailed records of all actions and events related to a Payment Transaction. They are used to monitor, debug, and audit the payment lifecycle. These Logs help Payment Providers, Merchants, and technical teams understand what happens at each stage of a transaction.
Review Logs
- Navigate to the Transactions tab and click the particular Payment Request on the grid.
- The system redirects you to a page with payment details at each initiation level: Payment Request, Commit, and Transaction.
- Go to the Logs tab of the Payment Transaction level.
- Click a specific entity. The system should open a side-bar drawer with all the respective details.
- The details include: General information, Timeline, and Provider payloads.
Command & Flow action & Status
1. Commands
Payment Command is an entity that is a reflection of a single payment interaction with a Provider. The main task of the Payment Command is to control financial interactions, standardise interactions and the algorithm.
| Command | Description |
| Void | Cancels a previously authorised payment before it’s captured; no funds are moved. |
| Verify | Performs a card verification without charging the card. |
| Complete Verify | Finalises the card verification process. |
| Authorize | Reserves funds on the card without transferring them yet. |
| Authenticate Browser | Initiates browser-based authentication. |
| Authenticate 3DS | Starts a 3DS authentication process for the payment transaction. |
| Authenticate 3DS Finance | Initiates the financial step of 3DS authentication, which is linked to actual payment execution. |
| Complete Authorize | Completes the authorisation after the Customer authentication. |
| Complete 3DS Verifying | Finalises 3DS verification. |
| Complete 3DS Finance | Finalises the financial part of 3DS, ensuring the transaction is authenticated and ready for capture. |
| Google Pay 3DS Verify | Verifies a Google Pay transaction with 3DS authentication included. |
| Complete Sale | Finalises a sale transaction. |
| Refund | Returns previously captured funds to the Customer. |
| Get Refunds | Retrieves a list of Refund operations related to a specific transaction. |
| Initiate | Starts a new payment session. |
| Provide Invoice | Sends invoice data or attaches invoice details to the payment flow. |
| Get Redirect Form | Returns a form or redirect URL for browser-based flows. |
| Apple Pay Authorize | Initiates authorisation using Apple Pay credentials. |
| Capture | Captures funds previously held during authorisation. |
| Sale | Combines authorisation and capture into a single operation. |
| Sale By Token | Executes a sale using a saved Payment token. |
| Get Acs Form | Retrieves the Access Control Server form used for 3DS authentication challenges. |
| Apple Pay Charge | Executes a complete Apple Pay transaction. |
| Google Pay Charge | Executes a complete Google Pay transaction. |
| P2P Debit | Processes a peer-to-peer debit transfer between users. |
| Get Payment | Fetches the current status and details of the specified payment. |
| Authenticate | General authentication command. |
| Check 3DS Enrollment | Checks if the cardholder is enrolled in 3DS before initiating authentication. |
2. Flow actions
Flow action is an entire logical operation that can include multiple Payment Commands.
| Flow action | Description |
| Void | Cancels a previously authorised transaction before the funds are captured. |
| Verify | Performs a non-financial card validation to confirm the card is active and can be used. |
| Authorize | Reserves funds on the Cardholder's account without actually capturing them. |
| Check Status | Retrieves the current state of a payment or Command. |
| Initiate | Creates or starts a new payment session or flow. |
| Charge | Performs a payment that combines both authorisation and capture. |
| P2P Debit | Executes a peer-to-peer (P2P) debit transaction, where funds are moved from one Customer's account to another. |
| Refund | Returns funds to the Customer from a previously completed transaction. |
| Sale by Token | Performs a payment using a previously saved Payment token. |
3. Statuses
Payment Command status is an entity that represents the current state of a Command in a payment system.
| Status | Description |
| Queued | The Command has been received and placed in the execution queue, but has not yet started processing. |
| Processing | The Command is currently being executed. |
| Processed | The Command was successfully executed, and the expected outcome was achieved. |
| Failed | The Command could not be completed due to an error. |
| Terminated | The Command was intentionally stopped or cancelled before completion. |
Updated 4 days ago
