Card + Card Transaction

Split tender transactions with two cards allow customers to distribute payment for a single order across two different payment cards. This functionality provides flexibility by letting customers combine different card types (credit/debit) or use multiple cards when a single card has insufficient funds.

Pre-Authorization Support

PRE-AUTH allows merchants to place a hold on funds across both cards, with capture occurring in a subsequent step. Both cards must use the same payment type for the transaction to proceed. Mixed payment types (e.g., SALE on one card and PRE-AUTH on the other) are not allowed.

Key Rules:

• Both cards must support pre-authorization for PRE-AUTH transactions.
• If either card fails pre-authorization, the transaction will be rolled back.
• Capture must be performed for both cards to complete the transaction.
• PRE-AUTH is not supported for ACH or mixed ACH/Card transactions.

Scope

• Mode: Pay With Wallet | API Scope: merchant | API Endpoint: v2/payments | Interaction mode: API
• Maximum number of payment methods: 2
• Payment Type: AUTH or PRE-AUTH
• Transaction Type: Card + Card

Out-Of-Scope

• Mode: One Time Pay Pay & Save | API Scope: merchant-pci | API Endpoint: v2/sessions | Interaction mode: UI
• Payment Type: PRE-AUTH is not supported for Card + ACH or ACH + ACH transactions.
• Transaction Type: Card + ACH / ACH + ACH

Transaction Processing

For detailed information about Card+Card transaction processing, see Split Tender Transaction Processing.

Business Use Case Scenarios

Payment Method Validation

Given Payment Method validation is passed for both the payment methods, refer to Payment Method Validation

Standard Scenarios

Positive Use Cases

ID	Scenario	User Type	CARD 1 Status	CARD 2 Status	CCG Transaction Status
1	Both Card Payments Successful	Customer	AUTHORIZED	AUTHORIZED	✅ AUTHORIZED

Positive Flow

Negative Use Cases

ID	Scenario	User Type	CARD 1 Status	CARD 2 Status	CCG Transaction Status	CCG Actions	CCG Transaction Final Status
2	Any one card fails	Customer/Agent	AUTHORIZED	FAILED	❌ PENDING	Transaction rolled back for Card 1	❌ FAILED
3	Any one card requires 3DS AUTH	Customer/Agent	AUTHORIZED	AUTH-REQUIRED	❌ PENDING	3DS challenge cannot be completed in API and roll back card 1	❌ FAILED

Edge Case Scenarios

Probability

RollBack/Cancel Failures

Edge Cases

ID	Scenario	CARD 1 Status	CARD 2 Status	CCG Transaction Status	CCG Actions	CCG Rollback Plan
6	CCG Rollback Failure	Authorized	FAILED	❌ PENDING	CCG Cancel fails on one card	Merchant should wait until authorization expires. Capturing from Stripe dashboard is not allowed; CCG restricts capture for ambiguous or any child payment under split tender transactions.

Webhook Handling

Refer WebHook management