Member balance, across sites. Instant and on record.
Balansfer lets independent sites offer their members balance transfers between each other's accounts. Verification, one-time confirmation codes, an immutable ledger and daily settlement happen centrally; sites connect to a small API.
One transfer, four steps
The member does everything in your interface. They never see Balansfer.
Member picks a destination
When your transfer page opens, they see their matched sites and balances there, then choose a destination and an amount.
Amount goes on hold
You place the amount on hold from the member's balance and send Balansfer a single request.
Member confirms
If the same ID and phone match at the destination, the member receives a one-time code. Nothing is written until it is verified.
Balance moves
The destination credits instantly; you deduct permanently. Every step is in the ledger, every day in settlement.
What the operator gets
Instant transfers
No bank transfer to wait for, no support ticket. Members use their balance where it is; fewer of them walk away.
Network view
How much a member holds on which site, what they moved where — one screen, with history.
Daily settlement
One net figure per site at the end of the day. Who pays whom, undisputed and documented.
For your engineering team
One integration, two parts: a handful of endpoints you call and six small callbacks you serve. Typical integration takes two working days. Sandbox and a simulator site are ready from day one.
- POST/v1/members/upsertRegister a member, get verification status
- GET/v1/members/{ref}/networkMatched sites and balances
- POST/v1/transfersStart a transfer, triggers the code
- POST/v1/transfers/{id}/confirmVerify the code, commit
- GET/v1/settlements/{date}Your daily settlement line
Security, by default
| Measure | What it gives you |
|---|---|
| Signed requests, both directions | Every request carries an HMAC signature; a timestamp and single-use nonce block replay. |
| IP restriction | Only declared IPs are accepted from sites; sites only ever see Balansfer's IPs. Sites never connect to each other. |
| Double match | An account is linked only when national ID and phone number match together. ID alone is not enough. |
| A code on every transfer | Over Telegram, through a phone-ownership-verified channel; SMS otherwise. No exceptions. |
| Immutable ledger | Entries are never updated or deleted. Corrections are reversing entries, approved by two operators. |
| Personal data protection | ID and phone data are stored encrypted, never returned to sites, never logged. |
Let's connect your site
Tell us your stack; we'll send sandbox access and the integration guide the same day.