Cloudy Business Ops 3600 Knowledge Bases

Transaction

The Transaction object in Cloudy Business Ops 360 represents the actual financial event recorded when a payment is processed through a selected Payment Gateway and Payment Method.

While a Payment object represents the intent to pay (customer or vendor side), a Transaction captures the execution details — including transaction ID, amount, method, and status. This distinction ensures accurate audit trails and integration with external payment processors.

Status Values Explained

  • Captured – Transaction successfully processed and amount secured.
  • Failed – Transaction attempt failed (error message provides details).
  • Pending – Transaction is initiated but awaiting confirmation.
  • Pending for Settlement – Payment captured but settlement with the bank/gateway is pending.

Use Cases in Cloudy Business Ops 360

  1. Successful Customer Payment
    • The customer pays $500 via credit card.
    • Transaction record created with Status = Captured, Gateway = Stripe, Amount = $500.
  2. Failed Transaction
    • Customer attempts ACH payment but bank rejects due to insufficient funds.
    • Transaction created with Status = Failed and Error Message logged.
  3. Vendor Payment Settlement
    • The company pays a vendor via bank transfer.
    • Transaction logs details, shows Pending for Settlement until cleared.
  4. Multi-currency Transactions
    • Different currencies are supported through the Currency field to ensure proper international operations.

Example Scenario

  • Payment Record: Customer intends to pay Invoice INV-2025 for $1,000.
  • Transaction Created:
    • Amount: $1,000
    • Method: Credit Card (Visa, ****1234)
    • Status: Captured
    • Gateway: Stripe
    • Transaction ID: txn_92kjad8s2

This ensures Cloudy Business Ops 360 has a reliable record of how the payment was executed.

Best Practices

  • Always check Error Message for failed transactions before retrying.
  • Use Transaction Id for reconciliation with the payment gateway dashboard.
  • Enable Sign Draw? when requiring customer authorization for compliance.
  • Use Captured vs Pending states to distinguish between confirmed and still-processing payments.