Plus500US × Gate · Solution model

Fully disclosed perps and prediction markets

Gate runs the app and the customer relationship. Plus500US is the FCM: it opens one account per customer, credits deposits on Gate’s confirmation, runs risk in T4 and routes orders to Kalshi.

Accounts
One Plus500US account per customer
Integration
Three APIs: Account, Cash, Trading
Funding
Credit on Gate’s confirmation #
Risk
Auto-liquidation by position, in T4
All documents01The model02Account opening03Funding04Trading & risk
01Overview

The model

Every cash activity has two parallel flows. The instruction flow (API calls) drives the customer experience: Plus500 credits the account and updates T4 when the instruction arrives. The money flow (cash between Gate and Plus500’s bank) settles afterwards and is matched in reconciliation.

01

Fully disclosed

One individual Plus500US account per customer. No omnibus or master account.

02

Gate owns the UX

App, onboarding, KYC and the relationship. We run books, risk and reporting by API.

03

Package in, account out

No complete package, no account. The account number keys everything after.

04

Credit on confirmation

Deposits credit on Gate’s confirmation #. Cash settles behind the scenes.

05

Kalshi is the source

Perps settlement and funding come per account, in real time. Market data goes straight to Gate.

Money flow
Settles after the API flow · ops & recon
Gate · customer fundsHeld by Gate for its customers
Gate · transferMoves funds per customer instruction
Issues a confirmation # per transfer, sent on the API call
Plus500 bank accountCash in or out, typically with a delay
Arrives after the credit and is matched to the confirmation # in recon. It never holds up the credit.
Onboard›Fund›Trade›Reports
End customer

Gate · trading UX & customer management

Customer identity · relationship · wallet
Gate App: mobile & web
Onboarding & KYCCollect · verify
Identity mapGate ID ↔ acct #
Order managerFIX orders + acct #
Customer walletFunds activities · moves
Documents & reconStatements · AML
Market data feedKalshi WS / REST

Account API

↓Customer package
↓Lean upgrade (later)
↑Account number
↑Statements (PDF)

Cash Movements API

↓Deposit / withdrawal
↓Acct # + confirmation #
↑Approved or rejected
↑Posted balance

Trading API · FIX

↓Orders, acct # on each
↑Account data · margin
↑Fills & events

Plus500US · FCM, clearing & order routing

Official balances · positions · reporting
Account API
  • Onboarding intake
  • Account openingPerps + predictions, or predictions only
  • Customer statements
Cash Movements API
  • Deposits
  • Withdrawals
  • Funds checkHolds back perps margin
Trading API
  • Real-time account dataFunds, margin, leverage, margin ratio
  • Risk engineKalshi margin API · auto-liq by position
  • Order router
FCM core · individual customer accounts
Every cash activity posts from Cosmos to T4 and QBO in parallel.
Cosmos · adminAccount master · cash transactions
T4 · order routing & riskReal-time trading balance
QBO · back officeStatements · official records
The books act on the API call: the credit posts on Gate’s confirmation #, Kalshi settlement and funding post per account in real time, and incoming cash is matched later in reconciliation.
↓Orders · margin queries
↑Fills & events
↑Settlement & funding, per account

Kalshi · exchange & execution venue

Markets · executions · settlement
Matching engineExecution venue
Margin APIPer order · size-dependent
Settlement & fundingPer account · 2 + 3 runs a day, 7 days
Market data APIPrices · order book
Market data streams from Kalshi straight to Gate, not through Plus500.
Request / response APITrading API / event streamMarket data, Kalshi → Gate directMoney flow, matched in recon
A

Account opening

One individual account per customer · open on receipt, check after

  1. CustomerCompletes onboarding, KYC and the Futures (Lean) questionnaire inside the Gate App. A shorter prediction markets questionnaire may be added later.
  2. GateVerifies the customer and sends the complete package to the Account API; Plus500 confirms receipt.
  3. Plus500Opens the account at once in Cosmos, reflected in T4 and QBO: perps + predictions, or predictions only.
  4. Plus500Returns account-ready status and a unique account number.
  5. GateMaps Gate customer ID ↔ Plus500 account #, the key on every order, cash move and statement.
  6. Plus500After opening: validation, FCM acceptance and the BG New Accounts second-eye review. The customer never waits.
No omnibus or master account. Gate owns the app and the day-to-day relationship.
B

Funding

Credit on confirmation · cash settles behind the scenes

  1. CustomerInstructs Gate to move funds into their Plus500 account: one balance for perps and predictions. Never funds Plus500 directly.
  2. GateMoves the cash and issues a confirmation #, proof the cash is irrevocably on its way.
  3. GateCalls the Cash Movements API with acct #, amount and the confirmation #.
  4. Plus500Credits the account on the confirmation, without waiting for cleared funds.
  5. Plus500Cosmos posts to T4 and QBO in parallel; the T4 balance updates and the customer can trade.
Cash arriving in Plus500’s bank is an ops and reconciliation matter, not a step the customer waits on.
Withdrawals mirror this: Plus500 checks eligibility (withdrawable cash excludes perps margin and open predictions), debits and approves via API, Gate pays the customer, and Plus500 sends the cash to Gate after.
C

Trading

Orders via Plus500 · market data direct from Kalshi

  1. CustomerSees live markets and prices in the Gate App, streamed directly from Kalshi.
  2. GateBuilds the order, stamps the Plus500 acct # and sends it via the Trading API (FIX).
  3. Plus500Runs pre-trade risk: for perps, the Kalshi margin API for this order’s size against the T4 real-time balance. Routes to Kalshi.
  4. KalshiMatches the order; fills and per-account settlement and funding flow back as events.
  5. Plus500Posts settlement, funding and fees as real-time cash; updates positions, margin and margin ratio; relays to Gate.
  6. GateRefreshes orders, positions, P&L and margin in the app.
Auto-liquidation runs position by position in T4 (section 4).
02Account API

Account opening

The customer signs and answers everything in the Gate App. Gate verifies and sends one customer package, with proof for every detail. The package triggers the account. To keep onboarding fast, the account opens on receipt and the checks run after.

Building and submitting the package

Gate collects and verifies. Plus500 opens on receipt and reviews after.

End customer
Gateregulated broker
Plus500USFCM · books & records
Signs the agreements and answers the questionnaire (Futures or prediction markets)1
Provides ID and proof of address2
3Runs the electronic identity check (EIC) and AML screening; keeps each result and reference
4Wraps it into one verified package, every claim with its proof
Account API: submits the package, details + files5
6Confirms receipt and opens the account at once in Cosmos, reflected in T4 and QBO, per questionnaire
Account ready + unique account number7
8Stores Gate ID ↔ Plus500 acct #
9After opening: completeness, FCM acceptance, BG New Accounts second-eye review
No package, no account. The number returned at step 7 keys every order, cash movement and statement after it.

Two questionnaires, two starting points

The first questionnaire decides how Cosmos sets up the T4 account.

Perps first

Futures questionnaire (Lean)

The full futures questionnaire. Cosmos sets up the T4 account for perps and prediction markets in one pass.

PerpsPrediction markets
Predictions first

Prediction markets questionnaire

A shorter flow. The T4 account is set to prediction markets only. To add perps later, the customer answers the lean questions and Gate sends them over the Account API.

Prediction marketsPerps after lean upgrade
Possible first phase: a single flow. Every customer completes the Futures questionnaire, and once the package is received the account opens for both perps and prediction markets, on one balance. The prediction-markets-only flow and the upgrade path would follow in a later phase.

Upgrade: predictions only → perps

Same account, same number. Only the T4 product setup changes. Needed once the predictions-only flow is offered.

End customer
Gate
Plus500USCosmos · T4
Wants to trade perps1
Shows the missing lean questions2
Answers them3
Account API: lean answers for acct #4
5Cosmos updates the T4 setup: perps on
Product status: perps enabled6
7Shows perps to the customer
03Cash Movements API

Funding

Gate moves the cash and issues the confirmation number; there is no third party in the flow. One balance serves perps and predictions. The examples use $100.

Deposit

Gate’s confirmation # lets Plus500 credit the account before the cash arrives.

End customer
Gateregulated broker
Plus500USbooks & risk
“Transfer $100 to my trading account”1
2Moves the cash and issues a confirmation #
Deposit: acct #, $100, confirmation #3
4Credits the account on the confirmation, before any cash arrives
5Cosmos posts to T4 and QBO; the customer can trade
Sends $100 to Plus500’s bank6
7Recon: bank receipt matched to the confirmation #
The customer is funded and trading at step 5. Steps 6–7 settle behind the scenes.

Withdrawal

Plus500 checks each request. The payout and the cash settlement to Gate run in parallel.

End customer
Gateregulated broker
Plus500USbooks & risk
“Withdraw $100”1
Withdrawal request: acct #, $1002
3Risk check: withdrawable cash excludes perps margin and open predictions. If approved, debits and posts to T4 + QBO
Approved: release $1004
Pays $100 in local currency5
Sends $100 to Gate6
7Recon: payout matched to the debit
The customer is paid at step 5, once Plus500 approves. Plus500 settles with Gate after.
Instruction: API call, no money movesMoney: actual cash between Gate and Plus500’s bank
04Trading API

Trading & risk

Perps never close: Kalshi runs 2 settlements and 3 funding runs a day, 7 days a week, and margin depends on position size. So pre-trade checks call Kalshi per order, settlement and funding post per account in real time, fees are a % of notional, and auto-liquidation closes one position at a time.

Order lifecycle

Orders: Gate → Plus500 T4 → Kalshi. Market data: Kalshi → Gate, direct.

Customer
Gate
Plus500UST4 · risk
Kalshi
Prices & order book, straight to Gate1
Places a perps order2
FIX: order + acct #3
4Pre-trade: Kalshi margin API for this size vs real-time balance
Routes the order5
Fills · settlement · funding, per account6
7Posts cash in real time; updates positions, margin, ratio
Events + account values8
Orders, positions, P&L, margin9

Settlement, funding and fees

Kalshi is the single cash source for perps, as with Galactic.

Today in T4

Prices only, nothing per account

  • T4 receives settlement prices, not per-account amounts
  • Cash changes only through the QBO import, so net liq and liquidation decisions go stale
Agreed

Per-account cash from Kalshi, in real time

  • An import from Kalshi posts each account’s settlement and funding to T4 as cash transactions
  • One source for perps cash: Kalshi, not QBO. Admin cash transactions stay as today
  • Fees calculated in T4 as a % of notional, e.g. $99.68 notional → $0.12 fee at about 0.12%

Auto-liquidation, position by position

Built in T4, with PFP’s futures auto-liquidation logic as the reference, adapted for perps.

  1. 1Trigger. On every price tick: health = 1 − required margin ÷ equity, with equity = balance + unrealized P&L. Below 0, auto-liquidation starts.
  2. 2Shortfall. missing margin = required − equity
  3. 3Priority. Eligible perps only. Orders-only instruments first, then smallest required margin first. Select until the shortfall is covered, then stop.
  4. 4Execute. All or nothing per instrument: cancel its orders (abort if a cancel fails), then close 100% with market-with-protection orders, split by max order size, lots matched FIFO.
Gate’s margin ratio (= 1 − health)
0%healthy67%alert resets75%warning100%auto-close
Guardrails: one run per account at a time, at least 3 seconds apart. Prediction positions are fully paid, never auto-liquidated, and don’t count toward perps margin.
Plus500US · Gate fully disclosed · solution model
Plus500US · Gate

Access code required

Enter the access code to view this site.