Transactions represent payment and invoice-related records tied to orders. In a standard Arcadier checkout, there are x+1 transactions, where x transactions to merchants (where x = number of merchants involved), and 1 transaction to the Admin for commission fees.
In standard marketplace configurations:
- Multiple merchant Transactions may be created.
- A separate commission Transaction may exist for the Admin.
Use transaction objects to reconcile payments, refunds, and external gateway states. If an integrated payment gateway is used, either platform’s pre-integrated gateways (e.g. Stripe) or external gateway:
- Unique string Transaction IDs are generated externally.
- Payment gateway lifecycle states must be mapped to Arcadier PaymentStatus (e.g. Processed, Paid, Failed, Refunded).
Transaction lifecycle states must be mapped to Order PaymentStatus values explicitly. Financial state progression does not occur automatically unless triggered via API or gateway callback.
Custom Transaction Use-Cases
- Payment reconciliation dashboards (invoice/order alignment).
- Refund and dispute workflows (track transaction state changes).
- External finance integration (sync transaction payloads into ERP/finance systems).