Frequently Asked Questions
Answers to common questions about fees, assets, settlement, and compatibility.
Answers to frequently asked technical and operational questions regarding the SplitPay protocol.
What assets does SplitPay support?
SplitPay supports any Stellar Asset Contract (SAC) conforming to the official SEP-41 token standard. On Stellar Testnet, native XLM and test tokens are supported. On Mainnet, native XLM, USDC, EURC, and any standard issued asset can be used.
Who pays blockchain transaction fees?
The entity signing and submitting the transaction pays the minimal Stellar ledger fee (in XLM). For pool creation or member updates, the pool owner pays. For payment creation and settlement, the payer or settlement invoker pays.
Why do pool shares have to equal exactly 10,000 BPS?
Basis points ensure 100.00% exactness without floating-point errors. If a pool were allowed to settle with only 9,000 BPS (90%), 10% of the funds would have undefined ownership. By asserting 10,000 BPS, 100% of the payment is mathematically accounted for.
How does SplitPay handle odd payment amounts and division remainders?
When integer division leaves a remainder difference between the gross payment and the sum of raw allocations, SplitPay deterministically awards the remainder stroops to the first pool member (index 0). Zero stroops are lost.
Can past payment distributions ever be altered?
No. When a payment settles, the contract takes an immutable snapshot of member shares and records individual distribution structs in persistent ledger storage. Subsequent changes to pool configuration have zero effect on historical distributions.
Does SplitPay hold or custody user private keys?
No. SplitPay is strictly non-custodial. All operations requiring authority are authorized using cryptographic signatures from browser extensions (e.g. Freighter) or local dev keypairs.