Cloudy Revenue Inventory Knowledge Base

Transaction

The Transaction object records and tracks every payment transaction processed through a configured Payment Gateway. It captures detailed information about online and offline payment activities, including payment amount, payment method, transaction status, captured amount, processing fees, browser information, customer payment method, and refund details.

The Transaction object provides a complete audit trail for payment processing, enabling organizations to monitor successful, pending, failed, cancelled, and refunded transactions. It integrates with Payment, Payment Gateway, Payment Method, and Refund objects to ensure secure and transparent payment management.

Key Purpose of Transaction

The Transaction object helps organizations:

• Record every payment transaction processed through a payment gateway.
• Track payment authorization and capture status.
• Maintain a complete payment audit trail.
• Record customer payment method and gateway information.
• Monitor transaction processing fees.
• Support online and offline payment processing.
• Track refunds associated with transactions.
• Capture browser and customer information for security and compliance.
• Simplify payment reconciliation and reporting.

Use Cases in Cloudy Inventory

💳 Payment Processing

• Records every payment processed through the configured Payment Gateway.
• Stores transaction details for customer and vendor payments.

🔒 Payment Gateway Integration

• Integrates with payment gateways such as Stripe and Authorize.Net.
• Stores the gateway used to process each payment.

💰 Payment Capture Tracking

• Tracks authorized and captured payment amounts.
• Calculates the net captured amount after processing fees.

💳 Payment Method Tracking

• Records the payment method used for the transaction, such as:
  • Credit Card
  • ACH / Direct Debit
  • Bank Transfer
  • Cash
  • Other

📊 Transaction Status Monitoring

• Tracks the complete transaction lifecycle, including:
  • Pending
  • Captured
  • Pending for Settlement
  • Failed
  • Cancelled

💲 Processing Fee Management

• Stores processing fee percentage and processing fee amount.
• Supports automatic creation of processing fee invoice line items.

🔄 Refund Tracking

• Links transactions to Refund records.
• Tracks refunded and pending refund amounts.

🛡️ Security & Compliance

• Stores browser details, IP address, E-Signature, and customer payment method information to support secure payment processing and auditing.

Checkbox Functionality

The Transaction object includes checkbox fields that control transaction processing behavior. 

Example Business Scenario

• Test Customer Inc. purchases 10 Sedan Cars and an Invoice is generated for USD 1,000.
• The customer receives a secure Payment Link and opens it to make the payment.
• The customer selects Credit Card as the Payment Method, chooses Full Payment, and provides the required payment details and E-Signature.
• The payment is processed through the configured Stripe Payment Gateway.
• After successful payment authorization and capture, Cloudy Inventory automatically creates a Transaction record with the following details:
  • Transaction Name: TRN-2026-0001
  • Payment: PAY-2026-0001
  • Payment Gateway: Stripe
  • Payment Method: Credit Card
  • Transaction Date: 09/07/2026
  • Amount: USD 1,000.00
  • Captured Amount: USD 1,000.00
  • Net Captured Amount: USD 990.00 (after processing fee)
  • Processing Fee: USD 10.00 (1%)
  • Currency: USD
  • Status: Captured
  • Transaction ID: txn_123456789ABC
  • Credit Card Last Four Digits: **** 4589
  • Browser Name: Google Chrome
  • Browser Version: 138.0
  • IP Address: 192.168.xxx.xxx
• Once the Transaction is successfully created, the related Payment status is updated to Paid, the Invoice status changes to Paid, and the transaction becomes available for payment reconciliation and future refund processing if required.

Transaction Creation:

Note:   Transaction records are created automatically when a payment is processed through a configured Payment Gateway. Users cannot create Transaction records manually. 

Best Practices

• Allow Transaction records to be created automatically through payment processing.
• Always configure a valid Payment Gateway before processing online payments.
• Monitor Failed and Pending transactions regularly.
• Review processing fees during payment reconciliation.
• Maintain Transaction IDs for gateway reconciliation and auditing.
• Use Transaction records as the source of truth for payment history.
• Link refunds to their original transactions for complete traceability.
• Regularly review gateway error messages to identify payment issues.
• Verify captured amounts against Payment and Invoice records.
• Use Transaction reports to monitor payment success rates and settlement status.