Connect your wallet and verify identity

Begin by linking your corporate wallet to the SplitPay Onchain interface and completing identity verification. Ensure your wallet holds sufficient native tokens for gas fees and that your organization’s compliance requirements are met before initiating any transactions. A clean baseline configuration prevents downstream settlement failures.

1
Confirm prerequisites
Verify wallet compatibility, network access, and gas balance before configuring any split parameters.
2
Link wallet and verify identity
Connect your corporate wallet to the dashboard and complete any required KYC/AML checks.
3
Verify connectivity
Test a small, non-critical transaction to confirm the wallet can interact with the SplitPay smart contracts.

Create a new split contract template

Designing a split contract requires defining the payment constraints, comparing distribution options, and selecting the most efficient path. This approach ensures that your B2B settlement logic is robust and cost-effective.

After defining the structure, verify that the template aligns with your specific invoicing and vendor management needs. If a complex multi-tier split is unnecessary, simplify the template to reduce gas costs and administrative overhead.

1
Define the constraint
Identify the specific invoice, vendor group, or project budget that dictates the split structure.
2
Compare realistic options
Evaluate single-recipient vs. multi-recipient splits based on gas efficiency and vendor requirements.
3
Choose the practical path
Select the template configuration that balances automation needs with transaction cost efficiency.

Fund the vault and trigger the split

Funding the vault and executing the split follows a precise sequence: deposit funds, verify recipient addresses, and submit the transaction. This order minimizes the risk of failed settlements due to insufficient funds or incorrect routing.

Ensure the deposited amount covers both the settlement value and the estimated gas fees. After submission, monitor the transaction status to confirm that funds are distributed according to the defined ratios.

1
Define the constraint
Confirm the total settlement amount and ensure it includes a buffer for network gas fees.
2
Compare realistic options
Review the recipient list and split percentages (e.g., 70/30) to ensure mathematical accuracy.
3
Choose the practical path
Submit the transaction only after verifying all recipient addresses and network compatibility.

Monitor transactions and manage liquidity

Effective monitoring ensures that B2B settlements are completed efficiently and that liquidity is managed optimally. Track transaction confirmations and recipient receipts to maintain trust with vendors.

Regularly review your vault balances to ensure sufficient funds are available for upcoming settlements. Proactive liquidity management prevents delays in vendor payments and maintains healthy supply chain relationships.

Common setup errors and fixes

Even with a streamlined onchain interface, small configuration mistakes can delay B2B settlements. The following troubleshooting steps address the most frequent errors encountered during the initial setup of SplitPay onchain transactions. Addressing these issues early ensures your split ratios and recipient data are processed correctly without unnecessary friction.

Verify that all recipient wallet addresses match the exact format required by the target blockchain. A single character error in a 42-character Ethereum address or similar format on other chains will cause the transaction to fail or send funds to an invalid destination. Always copy-paste addresses from your verified vendor records rather than typing them manually. Double-check the network prefix (e.g., 0x for Ethereum) to ensure the address belongs to the intended chain.

Onchain transactions require native tokens (such as ETH or MATIC) to cover network gas fees. If your settlement wallet lacks sufficient balance for these fees, the transaction will be rejected by the network, even if you have enough funds for the actual payment amount. Ensure your primary settlement wallet holds a small buffer of native tokens separate from the funds being split. Check current network congestion levels to estimate the required gas limit accurately.

SplitPay requires precise mathematical alignment of split percentages. If you configure a 70/30 split, ensure the sum equals exactly 100%. Rounding errors or misconfigured decimal places can cause the smart contract to reject the transaction. For B2B payments involving multiple vendors, verify that the total percentage across all recipients does not exceed 100% and that the remaining balance is correctly allocated to the payer or a designated escrow account.

All parties in a split transaction must operate on the same blockchain network. Attempting to split a payment where one recipient is configured for Polygon and another for Ethereum Mainnet will result in a failure. Confirm the target network for each recipient before finalizing the transaction. Use the network selector in the SplitPay dashboard to ensure consistency across all participants in the settlement chain.

Finalize your workflow with a checklist

Before you consider your first on-chain settlement complete, run through this final verification. A quick review prevents failed transactions and ensures your B2B partners receive their funds exactly as agreed.

  • Connect and Verify: Confirm your wallet is linked and the contract address is correct.
  • Fund the Escrow: Ensure the total settlement amount is deposited into the smart contract.
  • Set Split Ratios: Double-check that the distribution (e.g., 70/30) matches your invoice terms.
  • Execute Transaction: Submit the transaction and wait for the blockchain confirmation receipt.
  • Notify Partners: Send the on-chain receipt to your vendors or affiliates for their records.

Once these steps are checked, your workflow is ready for scale.

Frequently asked questions about SplitPay Onchain

These questions address the most common operational concerns for finance teams adopting onchain settlements.