Transaction Management

Overview

Transaction Management in a Split Tender payment context refers to the system's ability to handle, track, and manage payment transactions that use multiple payment methods. This document outlines the permissions and restrictions for key transaction operations (capture, cancel, refund) based on payment method combinations and transaction states.

Capture Restrictions

Transaction capture refers to the process of finalizing a previously authorized payment for settlement.

CAPTURE TRANSACTION RESTRICTIONS

Payment Status

• Parent Payment Status should be AUTHORIZED to initiate capture transaction

Transaction Type	Payment Methods	Merchant	CCG	Condition
Sale	Any	❌	✅	CCG automatically captures sale transactions
Pre-AUTH	Any	✅	❌	Merchant must explicitly capture pre-auth transactions

Cancel Restrictions

Transaction cancellation refers to stopping a transaction that has been initiated but not yet settled. Different payment method combinations have specific rules for cancellation.

CANCEL TRANSACTION RESTRICTIONS

Payment Status

• Parent Payment Status should be AUTHORIZED or ACCEPTED to initiate capture transaction

Transaction Type	Payment Methods	Merchant	CCG	Condition
Sale	Card + Card	❌	✅	Only CCG can cancel sale transactions with cards
Sale	ACH + ACH	✅	✅	Merchant Initiated: Only if both ACH transactions are in ACCEPTED status. CCG Initiated: No status dependency for roll back process
Sale	Card + ACH	❌	✅	Merchants are not allowed to cancel sale transactions with mixed payment methods
Pre-AUTH	Card + Card	✅	❌	Merchants can cancel pre-authorization transactions

Refund Restrictions

Refunds are the process of returning funds to a customer after a COMPLETED transaction. Refund capabilities depend on the payment status and methods used.

REFUND TRANSACTION RESTRICTIONS

Payment Status	Payment Methods	Merchant	CCG	Condition
PENDING	Any	❌	✅	If any payment method is in FAILURE status, CCG issues refund as part of rolling back
PENDING	Any	❌	✅	If any payment is pending under a split tender transaction
✅ COMPLETED	Any	✅	❌	Only merchants can initiate refunds for ✅ COMPLETED transactions

Ambiguous Payment Status

STRIPE DASHBOARD INITIATED OPERATIONS

The Mixed payment method status scenarios only occur when captures or cancellations are initiated directly from the Stripe dashboard rather than through the CCG platform. In these cases, CCG is responsible for maintaining transaction integrity.

Transaction Integrity Impacts: Merchant-initiated transaction operations have significant implications for transaction integrity within the system. Since these operations can modify the state of financial transactions, they must be carefully controlled and monitored through the CCG platform rather than directly in Stripe.

Mixed Payment State Scenarios

Mixed Payment State Scenarios

Reconcilation Process

• CCG Responsibility: When a capture or cancellation event is received from Stripe (initiated from the Stripe dashboard), CCG will automatically initiate RollBack Process to maintain integrity. Merchants do not need to take any action in these scenarios.
• No Merchant Handling: Merchants are not required to handle refunds or reconciliation for Ambiguous status split tender transactions resulting from Stripe dashboard operations. CCG will process all necessary refunds and actions.

COMPLETED Vs FAILED/CANCELLED COMBINATIONS

Use Cases

Scenario	Payment Method 1	Payment 1 Status	Payment Method 2	Payment 2 Status	CCG Action	Payment 2 Status After CCG Action	Final Transaction Status
1	CARD	🚫 CANCELLED (via Stripe)	ACH	✅ COMPLETED	CCG automatically issues refund for ✅ COMPLETED ACH payment	💰 COMPLETED	🚫 CANCELLED
2	CARD	✅ COMPLETED (captured via Stripe)	ACH	❌ FAILED	CCG issue refund for ✅ COMPLETED CARD payment if required	❌ FAILED	❌ FAILED
3	ACH	🚫 CANCELLED (via Stripe)	ACH	✅ COMPLETED	CCG automatically issues refund for ✅ COMPLETED ACH payment	💰 COMPLETED	🚫 CANCELLED
4	CARD	🚫 CANCELLED (via Stripe)	CARD	✅ COMPLETED (captured via Stripe)	CCG automatically issues refund for ✅ COMPLETED CARD payment	💰 COMPLETED	🚫 CANCELLED

ACCEPTED/AUTHORIZED Vs FAILED COMBINATIONS

Use Cases

Scenario	Payment Method 1	Payment 1 Status	Payment Method 2	Payment 2 Status	CCG Action	Payment 2 Status After CCG Action	Final Transaction Status
5	CARD	🚫 CANCELLED (via Stripe)	ACH	⏳ ACCEPTED	CCG automatically initiates cancel on PENDING ACH payment	🚫 CANCELLED	🚫 CANCELLED
6	CARD	🚫 CANCELLED (via Stripe)	ACH	⏳ ACCEPTED	CCG automatically initiates cancel on PENDING ACH payment but cancellation failed	🚫 CANCEL_FAILED	🚫 CANCEL_FAILED
7	CARD	🚫 CANCELLED (via Stripe)	ACH	❌ FAILED	No additional action needed	❌ FAILED	❌ FAILED
8	ACH	🚫 CANCELLED (via Stripe)	ACH	❌ FAILED	No additional action needed	❌ FAILED	❌ FAILED
9	CARD	🚫 CANCELLED (via Stripe)	CARD	✅ AUTHORIZED	CCG automatically initiates cancel on AUTHORIZED CARD payment	🚫 CANCELLED	🚫 CANCELLED

COMPLETED Vs ACCEPTED/PENDING/AUTHORIZED COMBINATIONS

Use Cases

Scenario	Payment Method 1	Payment 1 Status	Payment Method 2	Payment 2 Status	CCG Action	Payment 2 Status After CCG Action	Final Transaction Status
10	CARD	✅ COMPLETED (captured via Stripe)	CARD	✅ AUTHORIZED	CCG automatically initiates capture on AUTHORIZED CARD payment	✅ COMPLETED	✅ COMPLETED
11	CARD	✅ COMPLETED (captured via Stripe)	CARD	PENDING	CCG wait for capturable state and initiates capture on AUTHORIZED CARD payment	✅ COMPLETED	✅ COMPLETED
12	ACH	✅ COMPLETED	ACH	ACCEPTED	CCG wait for ACH Final Event and Then send notification if Success	✅ COMPLETED	✅ COMPLETED

Handling Guidelines for Mixed Status Transactions

1. Stripe Dashboard Operations: These mixed status scenarios occur exclusively when captures or cancellations are initiated directly from the Stripe dashboard instead of through CCG.
2. CCG Automated Handling: Upon receiving a capture or cancellation event from Stripe, CCG will automatically issue refunds or take necessary actions on the other payment method to maintain transaction integrity. No merchant intervention is required.
3. Merchant Responsibilities:
   • Avoid initiating captures or cancellations directly from Stripe dashboard
   • Monitor split tender transactions for mixed status scenarios only for informational purposes
   • Split Payments in Stripe will have a flag to indicate the same through metadata.