The rails BTSE settles on and their clocks, a catalogue of the breaks a settlement desk meets, how I would run the daily close across three shifts, and a working desk that ties every account to zero.
Every deal, deposit and withdrawal ends as a line on a bank statement or a wallet. The settlement associate makes the two sides agree to the cent, every day, and explains each difference.
Spot and futures users on SWIFT, SEPA, FPS, SIC and cards; OTC and convert deals with two legs each; crypto on several chains; and B2B clients on BTSE's white-label and payments stack.
A settlement desk: deal confirmations, deposit and withdrawal status, bank and wallet matching, a break queue with maker-checker, and an end-of-day tally that must reach zero.
| Takeaway | Why it matters on the desk |
|---|---|
| "100% tallied" is a number | Book movement minus bank movement equals the sum of listed breaks, per account. Anything left over is the day's real problem. |
| Paid-but-failed is the costliest break | A withdrawal that left the wallet while the system says FAILED invites a retry, and a retry pays twice. It goes first, and nobody retries until it is reconciled. |
| Deals settle in two legs | Releasing our leg before the client's arrives is credit risk. The desk checks the price, the confirmation and both legs, in that order. |
| Each rail has its own clock and fee | SWIFT takes 1 to 5 business days and loses intermediary charges on the way; SEPA and SIC are free; cards cost 3.3%. Each rail produces different breaks. |
| Three shifts mean one ledger | Every open item crosses a handover with its owner, its next action and its deadline, so the night shift closes what the day shift found. |
BTSE runs three businesses: an exchange, payments and white-label infrastructure. Each one sends money through settlement differently.
| Business line | What BTSE's pages say | What it means for settlement |
|---|---|---|
| Exchange (spot, futures, convert) | Fiat in USD, EUR, GBP, JPY, HKD, CAD, CHF, AUD. Deposits by SWIFT, SEPA, FPS, SIC, card, Google Pay and Apple Pay. Multi-asset futures collateral and settlement. | Daily volume of user deposits and withdrawals across many rails, each with its own cut-off, fee and failure modes. |
| OTC desk | Any pair including fiat to crypto. Fixed, time-limited quote. Support pages give USD 0.10 to 3.5M per trade; larger tickets go to the manual desk. | Two-leg deals: confirmation to client and to the internal ledger, price check, then both legs matched against bank and wallet. |
| Payments | Fiat and crypto pay-ins and payouts; OTC "for over 50 major currencies". | FX legs and many more currency accounts to tie each day. The JD's "FX or Money Operation" sits here. |
| White-label infrastructure | Exchange, custody, wallet and payment stacks run for corporate clients (BTSE Enterprise Solutions). | Settlement reports aligned with each client's deals, and confirmations to external parties on their schedule. |
| Regional entities | Bhutan licence for an exchange and custody (Sep 2026); an Indonesia joint venture with IDR pairs (Jul 2026); Liechtenstein registration (2023). | More legal entities means more bank accounts, each reconciled on its own and reported on its own. |
Sources: BTSE support centre fiat and OTC articles, btse.com/en/otc, btsesolutions.com, BTSE and press releases. Links in §09.
BTSE competes in two markets at once: exchanges with their own retail users, and providers that run exchanges for other firms. Settlement quality is visible to both sets of customers.
| Peer | Model | Where settlement is the difference |
|---|---|---|
| Bybit, OKX, Bitget | Large offshore exchanges with Mandarin-speaking operations teams in the region. | Scale lets them absorb slow fiat. BTSE competes on service: a fast, correct answer on a missing SWIFT deposit keeps a trader. |
| MEXC, Binance | Fiat mostly through P2P and third-party channels in many markets. | BTSE offers direct bank rails (SEPA, SIC, SWIFT), which are cleaner to reconcile and easier to evidence for audit. |
| ChainUP, AlphaPoint, Shift Markets | White-label exchange technology for brokers, banks and fintechs. | BTSE also runs the payments and OTC liquidity behind the platform. Settlement reports that tie to each client's deals become part of what BTSE sells. |
| Licensed local exchanges | Onshore exchanges on local rails in a single market. | A regional joint venture (as in Indonesia) needs local-currency settlement held to the same daily tie-out as the global book. |
From BTSE's own support centre. The last column is what I would watch for on each rail.
| Rail | Deposit time | Withdrawal time | Deposit fee | Breaks to expect |
|---|---|---|---|---|
| SWIFT | 1 to 5 business days | 1 to 5 business days | From USD 10 | Credits short by intermediary charges; missing or truncated reference; returns days later (closed account, name mismatch). |
| SEPA | 1 to 2 business days | 1 to 3 business days | Free | Payer name differs from the account holder; R-transactions (returns) after the user was credited. |
| FPS | 1 to 2 business days | 1 to 3 business days | 0.1% | Reference dropped by the payer's app; timing breaks when internal batching meets an instant rail. |
| SIC (CHF) | 1 to 2 business days | Not stated | Free | Swiss holidays and cut-offs moving value dates. |
| Card, Google Pay, Apple Pay | Instant to 30 minutes | n/a | 3.3% | Net settlement from the processor (gross minus fees, refunds and chargebacks) matched to many small credits. |
| Crypto | Network confirmations | Network confirmations | Network fee | Wrong network, wrong token contract, amount differences, a hash that exists but failed. |
BTSE support articles on fiat deposit methods, times, fees and withdrawal times, read 4 Nov 2026. Out-of-hours requests roll to the next business day.
Users quote the support centre back to the settlement team, so it needs to match what the desk does. I read the fiat, OTC, fee and jurisdiction articles. These are the items I would check with the team first.
| Item | Detail | Suggested fix |
|---|---|---|
| Fiat withdrawal fees | "Fees and Transaction Limits" says it covers "everything from fiat deposit fees to futures trading fees", but links only spot and futures fees. The public deposit and withdrawal fee page lists crypto only. | One fiat fee table per rail, so a short payout has a page to point to. |
| FPS timing | FPS deposits take 1 to 2 business days and withdrawals 1 to 3, on a rail that settles in seconds. The pages do not say whether this is UK or Hong Kong FPS. | Name the scheme and currency, and state the review step that sets the timing. |
| EU fiat access | The MiCAR FAQ says users with an EU address are not eligible for fiat on and off ramps. The SEPA EUR deposit guide and the EU bank verification step are still live. | Add a line to the SEPA guide on who it applies to. |
| OTC limits | Support: USD 0.10 to 3.5M per trade, one-click fixed quote. OTC page: volume tiers above USD 10M a month and a manual desk for the final quote. | Say which channel handles which size. |
| Jurisdiction lists | The Terms and the support article give different country lists: the support article has 21 prohibited countries plus a separate restricted group, and only the support article names Malaysia. | One list, linked from both. |
BTSE support centre and btse.com, read 4 Nov 2026. Article links in §09. Each item is a page-to-page comparison; internal practice may already differ.
Each line of the JD, how I would do it, and where the demo shows it.
| JD duty | How I would do it | In the demo |
|---|---|---|
| Handle fiat and crypto payments accurately and promptly | Verify before release: right amount, right beneficiary, right network and token contract. For crypto, success status and confirmations before marking a leg settled. | On-chain check |
| Record all deals with no errors, 100% tallied with transaction history | Every deal and order booked as expected movements; every statement line matched or explained; unexplained difference must be 0 before sign-off. | EOD tally |
| Monitor trade confirmations and settlement reports against customers' deals | Check the deal price against the market at trade time, the confirmation amount against the deal, and both legs against bank and wallet. | Deals & confirmations |
| Track and process deposit and withdrawal status | Age every open order against its rail's SLA. Stuck items go to the processor owner; paid-but-failed items are fixed by hand, never retried. | Deposits & withdrawals |
| Daily reconciliation with Treasury against bank details | Statement integrity first (opening plus lines equals closing), then matching, then the break list Treasury needs: unknown debits, duplicates, recalls. | Bank & wallet lines |
| Dispatch confirmations to internal and external parties | Confirmation within 30 minutes of trade to the client and to the ledger mailbox, logged with time and channel. Corrections go out marked AMENDED. | Confirmation drafts |
| Liaise to solve confirmation and settlement issues | One message per break with the deal or order ID, the reference, the amount and one clear ask, in English or Chinese. | Break queue drafts (EN, 简体, 繁體) |
| Resolve FX and money operation problems | Value dates and cut-offs per currency; charges on SWIFT credits booked to the right account; short or over settlement handled before our leg goes out. | Bank charge, short settled |
| Regular reports for internal control and external audit | Daily tally, break log with maker and checker, and an audit trail of every manual status change. | CSV exports, printed EOD report |
The order I would work the day in. The demo follows the same steps.
Opening balance plus every line equals the stated closing balance, per bank account and per wallet. A gap here means a missing statement page and stops the close.
Two legs per deal once value time has passed; every deposit and withdrawal with its system status.
Deal ID, order ID or tx hash first. Lines without a reference match on exact amount and account only, and a person confirms the remitter before linking.
Money at risk first: paid but failed, duplicate payments, unknown debits, our leg out with the client's missing. Then stuck items past SLA, then tidy-ups.
Book minus bank equals the listed breaks, unexplained 0. Every sev 1 item has a maker and a different checker. Preparer and reviewer sign the day.
| Across shifts | What the handover carries |
|---|---|
| Each open break | Owner, next action, deadline, and the message already sent with its time. |
| Each held leg | Why it is held and what releases it (shortfall paid, price confirmed, recall answered). |
| Cut-offs ahead | Which currencies close in the next shift, and what must be paid before they do. |
All five appear in the demo's break queue on any seeded day.
| Case | What I check, in order | Root cause | Fix and escalation |
|---|---|---|---|
| USDT withdrawal shows FAILED, user says it arrived | Hash on chain; status success; token contract; amount and address against the order. | The payout went through; the status update did not. | No retry. Manual status change to COMPLETED with the hash, approved by a checker; ticket to Engineering on the status bug. |
| OTC client says the USD has been sent, our BTC already delivered | Bank statement by deal ID, then by amount; MT103 from the client. | Client paid late or to the wrong account. | Chase with deal ID and SSI; Treasury and the RM informed; no new deals for the client until received. |
| SWIFT credit 25 USD short | Narrative for charge lines; deal terms (SHA or OUR). | Intermediary bank deducted its fee. | Book to bank fees under SHA; claim from the client under OUR. |
| EUR payout returned three days later | Return reason code; original order; whether the user was re-credited. | Beneficiary account closed (AC04). | Reverse and re-credit; CS asks the user for new bank details. |
| Deal price 3.5% away from the market | BTSE candle for that minute; quote record; who booked it. | Fat finger or a stale quote. | Hold our leg; trading desk and compliance decide cancel or rebook with client consent. |
What internal control and an external auditor ask for: what moved, what did not tie, and who approved each fix.
| Cadence | Content | Control it evidences |
|---|---|---|
| Daily | Per-account tally (opening, in, out, closing, book vs bank, unexplained), break list, sign-off names. | Completeness and accuracy of the day's movements; four-eyes on the close. |
| Daily | Manual status changes and resolutions with maker, checker and evidence (hash, bank case number). | No unapproved ledger edits. |
| Weekly | Break ageing by type and owner; counts of paid-but-failed, duplicates and returns. | Root causes reach Engineering and Treasury with numbers. |
| Monthly | Suspense balance and ageing; bank charges booked; confirmations sent late. | Suspense is cleared under policy; late confirmations are tracked. |
Role: Settlement Associate (Mandarin speaking, shifting required), BTSE (public job posting, 2026).
BTSE support centre articles on fiat methods, times, fees, withdrawals, OTC and jurisdictions; btse.com OTC and fee pages; BTSE public API documentation. Read 4 Nov 2026.
The demo is my own build for this application. Deal prices are checked against BTSE's public 5-minute candles (api.btse.com, through the demo's own proxy because the API accepts browser calls from btse.com only). The on-chain tab reads real Ethereum and Tron transfers. Clients, deals, orders and statement lines are synthetic, with breaks injected on purpose; thresholds and SLAs are my assumptions.
Demo: btse-settlement.pages.dev · Fiat deposit methods · Fiat deposit times · Fiat deposit fees · Fiat withdrawal times · How to withdraw fiat · Fees and transaction limits · Deposit and withdrawal fees · OTC trading · OTC page · MiCAR FAQ · SEPA EUR deposit · Restricted jurisdictions · Terms · Spot API docs · BTSE Enterprise Solutions · Bhutan licence (Blockhead) · Indonesia JV release
Independent homework for the BTSE Settlement Associate role · 2026 · edwardtay.com