Issuance and sinks
Use configured negative-ID platform accounts for platform-owned issuance, collection, or settlement flows.
Game coins and in-app value
A virtual currency backend for app-defined value
Model coins, gems, or another digital unit without treating a balance update as an isolated counter change.
Digital purchase flow
Split one spend across several destinations
After configuring the coins asset, a buyer can fund a seller, the -2 spending platform account, a reward pool, or other recipients in one balanced transfer.
- One source or many sources
- One destination or many destinations
- Totals matched independently for every asset
- Transfer status available after interruption
{
"transfer_id": "purchase_8842",
"scene": "spend",
"from_accounts": [
{ "account_id": "player_42", "asset": "coins", "action": "spend", "amount": "100" }
],
"to_accounts": [
{ "account_id": "creator_7", "asset": "coins", "action": "spend", "amount": "85" },
{ "account_id": "-2", "asset": "coins", "action": "spend", "amount": "15" }
]
}Deterministic distribution
A platform account entry point can distribute transfers across its configured ID range using the transfer ID.
Not financial custody
XferAPI does not provide crypto wallets, exchange, payment processing, or real-money settlement.
Virtual-currency questions
The asset is defined by your app; XferAPI supplies the balance and movement layer.
Is this a blockchain or crypto wallet?
No. It is an API for balances defined inside your product. It does not custody or exchange external currency.
Can a purchase pay several recipients?
Yes. Add multiple destination entries and keep the per-asset destination total equal to the source total.
Can game currency expire?
Yes. Destination batches may start later or expire. Use this for product-specific grants, not for external financial instruments.
Model one in-app value flow
Use the quickstart to create the balance boundary, then adapt the transfer entries to your app's account and asset model.