Abandoned Payments

Overview

When a user closes their browser or loses connection during a split tender payment, the system can be left in an ambiguous state—one payment may be completed while the other fails. This section details the risks, system behaviors, and automated recovery mechanisms for handling such unattended or abandoned transactions.

BUSINESS RISK

Critical Edge Case: Browser closure or session loss during split tender processing can result in:

• Asymmetric transaction states (one payment succeeded, one failed)
• Financial reconciliation issues
• Customer confusion about charged/reserved funds
• Potential duplicate payment attempts

Session Timeout & Abandonment

CCG sessions have configurable timeout settings to automatically handle abandoned transactions:

Session Type	Default Timeout	Maximum Duration	Configurable
UI Session	15 minutes	30 minutes	Yes

info

When sessions time out, CCG's automated recovery process will initiate to resolve any pending or partially completed transactions.

Abandonment Scenarios

Common Abandonment Patterns

Scenario	Description	Risk Level
Browser Closure	User closes browser/tab during payment processing	High
Connection Loss	Network interruption during transaction processing	High
Session Timeout	User leaves page idle for extended period	Medium

Browser Closure During Split Payment

Browser Closure Flow Analysis

State Analysis & Resolution

Transaction States & Automated Resolution

Component	Initial Status	Automated Resolution	Final Status	Timeframe
Payment Method 1	AUTHORIZED	Cancel authorization	CANCELLED	Within 15 min
Payment Method 2	FAILED	No action required	FAILED	Immediate
UI Session	TERMINATED	Session cleanup	EXPIRED	15 min timeout
API State	PARTIAL	Roll back successful parts	FAILED	Within 15 min
Customer Funds	RESERVED	Funds released	AVAILABLE	1-5 business days*

*Fund availability timing depends on the financial institution's processing schedule.

CCG Automated Recovery Process

CCG implements a robust automated recovery process to handle abandoned split tender transactions:

1. Detection:
   • Session timeout/cancel triggers
2. Analysis:
   • Identify asymmetric payment states
   • Evaluate transaction completeness
   • Determine appropriate rollback strategy
3. Resolution:
   • Cancel authorizations for successful payment methods
   • Mark transaction as FAILED
   • Log recovery actions for audit trail
   • Generate merchant notification if configured
4. Notification:
   • Send webhook event PAYMENT_FAILED to merchant