Endpoint
Overview
Use this endpoint to process tokenized payments and automatically split the proceeds between two merchant accounts. This is ideal for marketplace and platform applications where you need to collect fees or distribute revenue.Split payments require a TokenEx token from the embedded checkout and multiple merchant accounts configured for split processing.
Authentication
| Header | Value | Required |
|---|---|---|
x-api-key | Your API key from onboarding | Yes |
Authorization | Bearer {appToken} | Yes |
appId | Your application ID | Yes |
Content-Type | application/json | Yes |
Request Body
Container for API data
UUID for idempotency to prevent duplicate transactions
Must be
"payments"Container for payment attributes
Must be
"tokenv3Split" for split paymentsPrimary merchant account identifier (receives the net amount after split)
Optional JSON string with additional metadata
Tokenized payment method information
Transaction details
Split configuration
Billing address information (optional but recommended)
Example Request
Response
Success Response (201 Created)
Unique payment transaction identifier
Payment type -
"card"Transaction details including split information
Example Response
Code Examples
Understanding Split Payments
Split payments automatically distribute transaction proceeds:- Customer pays total amount: e.g., $5.00
- Platform fee is split: e.g., $1.00 goes to secondary merchant
- Processing fees applied: Standard 2.9% + $0.30
- Primary merchant receives net: Remaining amount after split and fees
Calculation Example
For a 1.00 split:- Gross: $5.00
- Split to secondary merchant: $1.00
- **Processing fee on 0.45 (2.9% + $0.30)
- Net to primary merchant: $3.55
Error Responses
Common Error Scenarios
Split amount exceeds transaction amount
Split amount exceeds transaction amount
Error: 400 Bad RequestSolution: Ensure split.amount is less than transaction.amount. The split cannot be equal to or greater than the total.
Invalid secondary merchant
Invalid secondary merchant
Error: 400 Bad RequestSolution: Verify the secondary merchantId exists and is configured for receiving split payments.
Merchant not configured for splits
Merchant not configured for splits
Error: 403 ForbiddenSolution: Contact Digitzs support to enable split payment functionality for your merchant accounts.
Important Notes
Pre-configuration Required: Both merchant accounts must be configured for split payments. Contact Digitzs support to enable this feature.
Processing Fees: Standard processing fees (2.9% + $0.30) apply to the gross transaction amount, not the split amount.
Use Cases: Split payments are ideal for marketplaces, platforms, and applications where you need to collect platform fees or distribute revenue to vendors.
Best Practices
- Validate Split Amounts: Ensure split amount is reasonable and less than total transaction amount
- Track Both Accounts: Monitor transactions in both primary and secondary merchant accounts
- Clear Communication: Inform users about how payment will be distributed
- Handle Refunds Properly: Use split refund endpoint to properly reverse split transactions
- Test Thoroughly: Verify split amounts are correctly distributed in your test environment
Next Steps
Create Second Split
Add an additional split to an existing transaction
Refund Split Payment
Learn how to refund split payments

