Skip to main content
Version: v2

Split Tender Transaction Processing

This section describes how split tender payments are processed for different payment method combinations in the Convenient Checkout API.

Processing Strategies

The Convenient Checkout Gateway (CCG) uses two distinct processing strategies for split tender transactions:

  • Parallel Processing: Used for Card+Card and ACH+ACH. Both payment methods are processed simultaneously for faster transaction time and improved customer experience.
  • Sequential Processing: Used for Card+ACH. Card is authorized first, then ACH is only initiated if card authorization succeeds. This prevents complex rollback scenarios and eliminates unreliable ACH cancellation.

Card + Card​

Parallel Processing
  • Both card payments are authorized in parallel for faster checkout.
  • If either payment fails, rollback logic is triggered.
Card + Card Process Flow

ACH + ACH (Bank Account + Bank Account)​

Parallel Processing
  • Both ACH (bank account) payments are processed in parallel.
  • ACH payments have delayed feedback (Notice of Return/NOR) that may take 2-3 business days, increasing the risk of late-detected failures.
  • If either payment fails, rollback logic is triggered.
ACH + ACH Process Flow

Card + ACH (Card + Bank Account)​

Sequential Processing
  • Card and ACH payments are processed sequentially: card is authorized first, then ACH is only initiated if card authorization succeeds.
  • If card fails, ACH is not attempted. If ACH fails, card is cancelled.
  • CCG initiates card capture or cancellation only after receiving the final event for the ACH payment due to the ACH processing window.
ACH Processing Considerations
  • ACH payments have delayed feedback through NOR (Notice of Return) which may take 2-3 business days
  • This creates a higher risk of late-detected failures compared to card transactions
  • Sequential processing for Card+ACH helps mitigate some of these risks
ACH Cancellation Reliability
  • ACH cancellation is not reliable in production environments
  • ACH cancellation can only be issued when payment intent is in processing status
  • In production, transactions often move from processing to pending status where cancellation becomes impossible
  • For Card+ACH transactions, this is why the card is only captured after ACH success is confirmed
Card + ACH Process Flow
Flow Diagram
Card + ACH Sequence Diagram

Error Handling and Retry Strategies​

Split Tender Error Handling

Retry Mechanisms​

  • CCG implements automatic retry mechanisms for transient failures
  • Card authorization/capture retries: Up to 3 attempts with exponential backoff
  • ACH processing retries: System will retry failed ACH initialization attempts

Rollback Failures​

  • Card Authorization Cancellation Failure: Rare but possible; tracked for manual intervention
  • ACH Refund Failure: When ACH refunds fail in rollback scenarios:
    • Resolution Options:
      • Alternative Refund: New payment method retrieved from customer to issue credit
      • Partial Success: Merchant can accept partial success and provide service accordingly

Error Notifications​

  • All split tender errors generate appropriate webhook events
  • Detailed error information is provided in API responses
  • Critical failures trigger alerts for operations teams