tetherMax keeps a lifetime rebate ledger for every linked UID

Enter a UID, pick an exchange, and tetherMax starts crediting a share of every futures trading fee back to that account — an average of 55% of fees, per the app's own Play listing. Behind that one-line setup sits the part an integrator cares about: a per-user ledger that accrues for the lifetime of the account, keyed to each exchange UID the trader has linked. The numbers in it are a reconciliation of many exchanges' affiliate data, blended into a single cashback balance. Reaching that ledger, and proving each line of it against the venue it came from, is the work this page describes.

The bottom line is short. Everything a third party would want from tetherMax lives behind a single authenticated account, and almost all of it traces back to a known source — the exchange that paid the commission. So the route we would actually stand up reads the app's own ledger and payout views for what the trader sees, then totals each line against the per-UID figures the exchange itself reports, so a discrepancy surfaces at read time rather than at payout. The rest of this page maps the surfaces, the routes, and what we hand over.

What sits behind a tetherMax account

These are the surfaces the app actually exposes to a logged-in user, named the way the app frames them where possible.

Authorized routes into the rebate data

Three routes genuinely apply here, and they complement rather than compete.

Protocol analysis of the app's authenticated session

tetherMax is a Swing2App build, which means the interface is a WebView shell talking JSON to a backend over HTTPS. With the account holder's authorization, we capture the session handshake once and read the ledger, linked-UID list and payout views the same way the app's client does. This is the surface that matches what the trader actually sees, and it is where a user-facing integration gets its numbers.

Upstream exchange affiliate feeds

Because each cashback line traces to an exchange commission, the source of truth is the venue's own affiliate data. Bybit, for example, exposes a per-referred-user list (its v5 affiliate endpoint) that an affiliate-permission key can total. Reconciling the app ledger against these feeds is what turns a displayed number into a verified one. Coverage here varies by exchange — some report richly, some thinly.

User-consented session access

Where a project only needs one consenting trader's own records, that account holder can authorize us to drive their session and export their ledger and payout history directly. It is the lightest path and a good fit for a single-account proof before a wider build.

For tetherMax specifically, the build worth paying for combines the first two: read the app session for the trader-facing ledger, then settle every line against the exchange affiliate feed so a missing or mis-rated rebate is caught the moment it is read, not a fortnight later at payout. The third route is how we prove the approach on a single account first.

What lands at the end of the build

Each deliverable is tied to a real tetherMax surface, not a generic checklist:

• An OpenAPI / Swagger spec for normalized endpoints — linked accounts, rebate ledger, payouts, and the fee-overpayment estimate — so the data reads the same regardless of which exchange a line came from.
• A protocol and auth-flow report documenting the Swing2App session and token chain as captured during the build.
• Runnable source in Python or Node.js for the key calls: session auth, list linked UIDs, pull the ledger by UID and period, reconcile against Bybit's affiliate list and its peers, and pull payout history.
• Automated tests, including a reconciliation fixture that asserts the app ledger totals match the exchange affiliate figures within tolerance.
• Interface documentation with a field dictionary (exchange, uid, gross_fee, rebate_rate, rebate_usdt, status, settle_date).
• Data-retention and consent-handling notes written against PIPA, so the stored fields and their lifetime are defensible.

Reading the rebate ledger — a worked sketch

Illustrative only; the exact paths and field names are confirmed during the build against a consenting account. The shape, though, follows the two-surface approach above — read the app, then settle against the exchange.

# 1) session captured from the Swing2App app shell (JWT / cookie)
session = tm_login(token)

# 2) the trader's linked exchange UIDs
links = session.get("/api/v3/cashback/links").json()
# -> [{"exchange":"BYBIT","uid":"1850xxxx","joined":"2025-11-02"}, ...]

# 3) the rebate ledger for one linked UID, one month
ledger = session.get(
    "/api/v3/cashback/ledger",
    params={"exchange":"BYBIT","from":"2026-05-01","to":"2026-05-31"},
).json()
# -> {"gross_fee_usdt":612.40,"rebate_rate":0.55,
#     "rebate_usdt":336.82,"status":"SETTLED"}

# 4) settle that line against the exchange's own affiliate feed
import requests
aff = requests.get(
    "https://api.bybit.com/v5/affiliate/aff-user-list",
    headers=sign(api_key, secret),          # affiliate-permission key only
).json()

gap = abs(aff["result"]["totalFee"] - ledger["gross_fee_usdt"])
if gap > TOL:
    flag("fee basis mismatch", uid="1850xxxx", gap=gap)   # net-vs-gross or lag

Keeping rebate numbers in step

Rebates accrue continuously but settle on each exchange's own cycle. WOO X, per its integration note with tetherMax, pays on net trading fees and distributes within fourteen working days, and it states that rates can change at its discretion. That has a direct consequence for any sync: freshness is bounded by the slowest-settling venue a trader uses. We poll the app ledger and the affiliate totals on each venue's cadence and stamp every line with its settlement state, so a downstream consumer can tell "not yet paid" from "never arrived" without guessing.

Consent, PIPA, and handling the data

The operator is Korean-origin and built on Swing2App, so the working privacy regime is South Korea's Personal Information Protection Act, which leans on explicit opt-in consent and consent records rather than implied permission. For any EU account holder, GDPR handling applies in parallel. In practice that means we read only the rebate, UID and payout fields a project needs, keep an access log of what was read and when, and work under an NDA where the engagement calls for one. The app's own permission notes list location, storage, camera and files as optional and used for in-app features, not for the cashback flow — so an integration of the ledger does not touch them, and we keep it that way. Consent for any one trader's data is scoped to that trader and revocable; we design around revocation rather than assuming a standing grant.

Engineering realities we plan around

Two things about this app shape the build, and we account for both rather than treating them as someone else's problem.

• One number, many fee bases. A blended 55% cashback figure is really many per-venue rates stacked together, each on a different basis — WOO X pays on net fees, Bybit caps a broker rebate near 45%, and others differ again. We model the per-exchange rate rules so the single displayed balance decomposes back to the correct contribution from each venue, instead of being trusted as one flat rate.
• A re-skinnable front end. Because the shell is Swing2App, a cosmetic update to the app can move the session or token handshake without changing the underlying data. We capture that handshake as a discrete, re-runnable step and fold a re-validation pass into maintenance, so a front-end change is a quick re-capture rather than a rebuild.
• Settlement windows, not real time. Each venue settles on its own clock, so we design the sync around those windows and mark unsettled accruals as such, keeping an in-flight rebate from looking like a lost one.

Access to a consenting account or a sponsor environment is arranged with you during onboarding; it is part of how the project runs, not something to clear before we begin.

Screens from the app

The published store screenshots, for reference while reading the surfaces above. Select one to enlarge.

Other rebate services in the same orbit

These sit in the same crypto fee-cashback niche. A unified integration treats them as variations on one shape: a per-UID rebate ledger reconciled against exchange affiliate data. Named here for context, not ranking.

• tetherCash — advertises up to 80% trading-fee cashback through exchange partnerships, holding the same kind of per-UID accrual ledger.
• TetherBack — positions itself, in an MEXC feature, as turning exchange commission into lower effective trading costs, tracking referred-UID fees.
• Rebatefee — pays USDT rebates back to the exchange account daily off the public UID, keeping per-account accruals.
• PaybackFX — a rebate comparison and cashback service spanning multiple crypto venues, tracking per-account fee returns.
• HighFxRebates — compares and routes crypto exchange cashback, holding referred-account fee and rebate records.
• RebateKing — offers perpetual-contract fee rebates tied to exchange UIDs.
• CoinRebates — runs cashback across many partner venues, keyed to user accounts.

How this mapping was checked

This was put together on 15 June 2026 from the app's own store listing and description, the WOO X integration note describing exactly which fields tetherMax reads from a partner exchange (nicknames, UIDs, trade amounts, rankings) and how rebates settle, Bybit's published v5 affiliate documentation for the source-of-truth endpoint, and the IQ.wiki entry for background on the service. Where a number could not be independently confirmed it is attributed to the source that states it.

• WOO X — integration note with tetherMax (data fields and settlement)
• Bybit v5 API — Get Affiliate User List
• tetherMax — Google Play listing
• IQ.wiki — tetherMax overview

Compiled by the OpenBanking Studio integration desk · 2026-06-15.

Questions integrators ask about tetherMax

Does reading my tetherMax data need exchange API keys, or just the UID?

The cashback model itself runs on the public exchange UID, with no withdrawal permission attached. We read the rebate and payout views from the app's authenticated session the way its own client does, and reconcile them against the exchange's affiliate totals. A trading-permission or fund-move key is never part of that.

Which exchanges' rebates can you actually reconcile against source data?

tetherMax lists roughly twenty affiliated venues as of its December 2025 listing, including Binance, Bybit, Bitget, OKX, HTX, BingX, MEXC, Gate, KuCoin and BitMEX. How deep the reconciliation goes depends on each venue's affiliate feed; Bybit, for instance, exposes a per-referred-user list we can total against the ledger.

How do you tell a genuinely missing rebate from a settlement lag?

We total the app's ledger against each exchange's per-UID affiliate figures on that venue's own cycle. WOO X, as one example, distributes within fourteen working days and pays on net rather than gross fees, so an accrual that is merely unsettled reads differently from one that never arrived.

Under which data rules do you handle a Korean-origin rebate app's records?

The operator is Korean-origin, built on Swing2App, so the working regime is South Korea's PIPA with its opt-in consent and consent-record requirements, plus GDPR handling for any EU account holder. We minimize to the rebate fields a project needs and keep an access log.

If you have a tetherMax integration in mind, give us the app name and what you want out of its data; access and any compliance paperwork are arranged with you as part of the work. The delivery itself is runnable source code with its spec, tests and interface docs — from $300, paid only after delivery once you are satisfied. If you would rather not host anything, the same data is available as a hosted API you call and pay for per call, with nothing upfront. Either path runs in one to two weeks. Tell us about the integration and we will scope it.