Skip to main content
Version: v2

Split Tender Payment Business Rules

Overview​

Split tender transactions let customers pay for a single purchase using two different payment methods (e.g., Card + Card, Card + ACH, or ACH + ACH). This increases flexibility, supports higher-value purchases, and reduces cart abandonment due to insufficient funds on a single payment method.

Scope
  • Mode: Pay with Stored Card
  • API Endpoint: v2/payments
  • API Permission: merchant
  • Maximum Number of Payment Methods: 2
  • Payment Type: Sale
  • Transaction Type: Card/ACH + Card/ACH
Out-Of-Scope
  • Mode: One Time Pay/ Pay and store
  • API Endpoint: v2/sessions
  • API Permission: merchant-pci
  • Payment Type: PRE-AUTH

Early Failures​

This section outlines the validation rules that apply to split tender transactions.

Error Codes
Error TypeDescriptionImpact
⚠️ INVALID_REQUESTThe request will not be acceptedTransaction is rejected immediately
🚨 PAYMENT_METHOD_ERRORRequest will be accepted but error will be returned on pollingTransaction is accepted initially but fails during processing
⛔ FORBIDDENMerchantTransaction Id cannot be reusedTransaction is rejected due to duplicate ID

Payment Type Validation​

NOT ACCEPTABLE

  • Mixed Payment Type Compatibility:

    • If BANK ACCOUNT + CARD payment methods are used together, payment type requested cannot be PRE_AUTH.
    • Pre-authorization is not applicable for ACH Direct Debit transactions.
    • Example: A request with payment type PRE_AUTH and payment methods Bank Account + Card will be accepted initially but will fail during processing.

  • Payment Type Consistency:

    • Both payment methods must use the same payment type.
    • Example: Cannot mix SALE for one payment method with PRE_AUTH for the other.

Payment Method Validation​

INVALID REQUEST
  • Unique Payment Methods:
    • The same payment method cannot be used for both payments in a split tender transaction.
  • Maximum Payment Methods:
    • Limited to exactly two payment methods per transaction.
PAYMENT_METHOD_ERROR
Important Note

Each payment method in a split tender transaction is individually validated according to these rules. If any payment method fails validation, the entire transaction will fail.

  • Valid Payment Methods:
    • Both PM1 and PM2 must be in valid status to initiate the transaction.
  • Availability in Customer Wallet:
    • Both payment methods must be available in the CCG wallet and associated to respective customer.
  • Payment Method ID Required:
    • Each payment must have a valid paymentMethodId.
  • Payment Method Configuration:
    • The requested payment method type must be enabled in the merchant's configuration.
      • For example, if a merchant is configured to accept only card payments, a request for a bank account payment method will be rejected.
    • Manufacturer Card Configuration:
      • The manufacturer card must be enabled in the merchant's configuration.
  • Payment Type:
    • Payment Type should be SALE if any one of the payment method is BANK_ACCOUNT
  • Early Warning API
    Early Warning API check is not applicable for stored bank accounts
    • Early Warning API is primarily designed for real-time validation of newly entered bank account details to detect fraud or invalid accounts at the point of entry.
    • Stored bank accounts have already passed initial validation and have a history of successful use, reducing the risk of fraud or invalidity.
    • Re-validating stored accounts with Early Warning API can lead to unnecessary friction and false positives for returning users.
    • Industry best practices recommend using Early Warning API for new or updated bank account entries, not for accounts already on file.
    • Ongoing risk monitoring for stored accounts is handled through transaction monitoring and return/NOR events, not through repeated Early Warning API checks.

Amount Validation​

INVALID REQUEST
  • Explicit Amounts:
    • Merchants must explicitly specify the amount for each payment method.
    • Example: If total is $100, specify $60 for first payment and $40 for second payment.
  • Parent-Level Amount Consistency:
    • The total transaction amount (parent level) must exactly match the sum of individual payment amounts.
    • This requirement enables automatic fallback to single payment if split tender fails.
    • Example: If parent amount is $100, payment amounts could be $70 + $30, but not $60 + $30.
  • Amount Limit:
    • Total transaction amount must be ≥ 2 cents
    • Each individual payment amount must be ≥ 1 cent (Stripe minimum requirement)
    • Example: Cannot split $1.00 as $0.005 + $0.995

Merchant Transaction ID​

INVALID REQUEST
  • Uniqueness:
    • Each split tender transaction must have a unique Merchant Transaction ID to ensure accurate tracking and reconciliation.
  • Reprocess:
    • Merchant Transaction ID can be reused only when the parent transaction status is in FAILED status.
    • If the ID is reused for a failed transaction, only specific fields may be overridden (see Idempotency Handling here).
INVALID REQUEST
  • Bank Account Consent:
    • If either payment method is a BANK_ACCOUNT, user consent is required.
    • Consent must be explicitly collected and provided in the API request.
    • Missing consent for bank account payments will cause the transaction to be rejected.

Existing Validation Use Cases​

important
Existing Payment Validations

All validations for single payments also apply to split tender transactions:

Transaction Management Restrictions​

CAPTURE/CANCEL/REFUND TRANSACTION RESTRICTIONS
Learn More

Refer Transaction Management for more details

  • Capture Transactions:
    • Merchants are not allowed to capture sale transactions
    • Only CCG can capture sale transactions
  • Cancel Transactions:
    • Merchants are not allowed to cancel sale transactions if any payment method in the split tender is a CARD
    • Only CCG can cancel sale transactions involving card payments
    • Merchants cannot cancel ACH transactions if the transaction is in PENDING status
      • For ACH+ACH combinations, both transactions must be in ACCEPTED status for cancellation
      • For CARD+ACH combinations, cancellation is not allowed since the payment type is SALE
  • Refund Transactions:
    • Merchants are not allowed to refund any transactions if any payment method in the split tender is in PENDING status :::