Skip to main content

Release 2.5.0

1. Trading Area:& smootherRequests: onboardingfewer andmistakes, accountclearer handlingflows

WIFOX-585531 – Trader“Replace Declaration:only close” for ticket type “ClientChange IDStop number”Loss field fixedonly”
The Client ID number field inIn Trading Area →tickets, Accountsthe →“Change TraderStop DeclarationLoss only” ticket type now acceptsuses anda showsdedicated user“Replace inputonly normally,close” keepsaction that updates only the valuestop‑loss inlevel formof statean andorder, submitswithout itunintentionally correctlychanging withtake‑profit theor declaration.other parameters.
Business impact:

  • TraderReduces declarationsthe arerisk noof longertraders blockedor bysupport astaff “dead”accidentally field.changing the wrong parts of an order.

  • ReducesMakes supportpartial involvementorder duringmodifications KYC(only /SL) onboarding.safer and more predictable.

WIFOX-511583 – AccountRequests/Tickets: selector:show smartercorrect IDcreator displayand last message author
The TradingRequests/Tickets Arealists accountand selectorheaders now shows:correctly show:

  • who client.uidcreated when the clientticket, has exactly one trading account;and

  • asset.uidwho when there are multiple accounts (as before), so they remain distinguishable.
    If client.uid is missing,wrote the selectorlast safelymessage, fallsregardless backof towhether asset.uid.it was done in CRM or Trading Area.
    Business impact:

  • FasterSupport, clientsales, identificationand incompliance teams see the commonreal single‑accountconversation case.owner and last responder at a glance.

  • NoEasier loss of clarity when a client has several accounts.

2. Trading Terminal: saved workspaceprioritisation and betterfollow‑up—no charts

more

WIFOX-588guessing –which Tradingside Terminal: remember selected pairs and order across logins
The Trading Terminal now persists“has the list and order of opened trading pair tabs (and the active tab) per user in local storage.

  • On first login, a default set is opened: EUR/USD, USD/ILS, BTC/USD, GOLD, BRENTball”.

  • Any changes (add/close/reorder/switch active) are saved.

  • After logout or token expiration, the same configuration is restored on the next login.
    Business impact:

  • Active traders no longer rebuild their workspace each session.

  • The terminal feels personalised and consistent between sessions.

WIFOX-515598 – NewFilter Order:by volume“Waiting +/-for controlsclient” basedstatus onin lot sizeRequests
In the NewRequests Ordermodule, form,tickets thethat are in Volume“Waiting for client” field(from Trading) can now hasbe “– / +” buttons with a step size derived from the instrument’s lot size (e.g. 0.01, 0.1, 1). Values are rounded correctlyfiltered and neversurfaced go below zero; manual typing still works.explicitly.
Business impact:

  • Faster,Support lessmanagers error‑pronecan volumequickly selection,find especiallyall forcases verywhere smallthe ornext largemove lots.is on the client.

  • FewerBetter rejectedcontrol ordersof dueaging tickets and follow‑up strategy.

2. Safer payments & transactions (Bridge Pay and beyond)

WIFOX-589 – Bridge Pay: prevent double deposits on duplicate callbacks
The Bridge Pay callback handler was hardened to invalidbe idempotent:

  • Repeated callbacks for the same payment no longer create duplicate deposits.

  • Only the first “success” event funds the client; later duplicates are safely ignored/logged.
    Business impact:

  • Eliminates accidental double crediting from provider‑side retries or awkwardduplicate volumecallbacks.

    inputs.

  • Less manual reconciliation and fewer finance corrections.

WIFOX-569559 – DefaultCard charttransactions: zoomdisplay setmasked closercard and Bank Name in UI
The Transactions table now shows:

  • Masked card number (1‑hourfirst4********last4) view)for card payments.

  • Bank name for card/acquirer.
    TradingAll chartsvalues are nownon‑sensitive and follow PCI‑style masking rules.
    zoomedBusiness inimpact:

    by
    • default

  • Operations and risk teams can identify specific cards/banks for investigations without exposing full PAN data.

  • Easier to spot patterns (1‑houre.g. view),specific showingbanks/cards pricefailing) actionand inescalate acorrectly.

    closer,
    • more
relevant
window.

WIFOX-480 – Transaction search stability & performance
Search and filtering over transactions were optimised to handle higher volumes and complex filters without timeouts or partial results.
Business impact:

  • TradersFinance seeand actionable,compliance recentteams pricecan movementrun immediately.more complex searches reliably.

  • Less manualwaiting zoomingand onfewer every“please symbol.try again later” errors during investigations.

3. Requests/Tickets messaging: richer, consistent conversations

WIFOX-568607 – RemoveRequests/Tickets: open‑positionshow pointerwhich fromside chartwrote each message (client vs manager)
TheMessages specialin pointerRequests/Tickets markernow forclearly theindicate openwhether positionthey onwere thewritten chartby has beena removedclient. (in Trading Area) or a manager/employee (in CRM), with aligned styling across both systems.
Business impact:

  • CleanerEveryone chartscan withfollow lessthe visualconversation noise.context more easily.

  • FocusReduces staysmisunderstandings onin pricemulti‑party and user‑defined levels instead of an extra marker that traders didn’t find useful.
    communication.

WIFOX-579 – Simplified UI: removed unnecessary accordion in Trading conditions section
A redundant accordion component in the Trading conditions context has been removed, keeping the interface flatter and more direct.
Business impact:

  • Less clicking and “hidden” content when working with pair info.

  • Cleaner, more straightforward layout for support teams.

3. Requests & Tickets: real‑time, rich conversations

WIFOX-544570 – Requests/Tickets: near‑real‑timefix messagelost updatesmessages (“online”due mode)to race conditions
MessageA pollingrace incondition that could cause some messages to not appear or appear out of order across CRM Requests → Messages and Trading Area Tickets → Messages has been tightened to a near real‑time interval while a conversation is open (around 1–2 seconds), with optimisations to pause/slow polling when the tab or conversation is not active. Sending a message also triggers an immediate refresh.fixed.
Business impact:

  • Conversations feelremain closercomplete toand chatsynchronised in realboth time, not like an email thread.interfaces.

  • Faster back‑and‑forth between clients andReduces support withoutoverhead manualfrom refresh.“I sent it but you don’t see it” cases.

WIFOX-542586 – Requests/Tickets:Unified clickablemessage linkstimestamps with timezone awareness
Message timestamps in messages (CRM + Trading Area)
URLs inside request/ticket messages areRequests/Tickets now automaticallyuse rendereda asconsistent clickableformat linkswith inclear bothtimezone/relative time, harmonised between CRM and Trading Area, opening in a new tab with safe settings.Area.
Business impact:

  • AgentsEasier andfor clientsglobal canteams followto sharedunderstand linkswhen (docs,exactly KYCa pages,message references)was directly from the conversation.sent.

  • LessSupports copy‑pasteaccurate SLA monitoring and fewer mistakes opening referenced resources.audit.

WIFOX-584514 – Tickets/Requests:Preserve removeand “onlysync letters”read/unread validationstate for Name/Subjectmessages
Read/unread state for ticket messages now syncs more reliably between CRM and Trading Area:

  • Messages read on one side are correctly marked on the other.

  • Badge counters (unread counts) reflect reality.
    Business impact:

  • Agents and clients see an accurate unread message count and don’t double‑work already read items.

  • Better experience for both sides in ongoing cases.

WIFOX-483 – Prevent sending empty or whitespace‑only messages
The Name/Subjectsystem fieldnow inblocks Ticketssending (Tradingmessages Area)that andcontain Requestsonly (CRM)spaces/new lines with no longeractual enforces “letters‑only” validation. Any characters are allowed (digits, symbols, mixed text such as “KYC 2.0 – urgent #15”).text.
Business impact:

  • UsersKeeps canthreads describeclean casesand naturally (IDs, ticket numbers, versions, etc.).readable.

  • FewerReduces blocked formsnoise and noaccidental need“blank” to invent artificial subject lines.replies.

4. ClientRequests/Tickets: Areabetter UXownership &and internationalisationworkflow tools

WIFOX-263512 – RTL/LTR“Assigned auditto andme” fixesquick forfilter Clientin AreaRequests
TheA mainone‑click Client“Assigned Areato (Tradersroom)me” viewsfilter havehas been reviewed and adjusted to work correctlyadded in boththe LTRRequests and RTL languages, including dashboards, markets, FAQ, history, tickets, deposits/withdrawals, forms, profile, documents, PWA modal, OAuth pages and key modals/drawers. Alignments, directional icons, paddings, table behavior and animation directions have been fixed for RTL where needed.module.
Business impact:

  • ProperEach experienceagent forcan right‑to‑leftquickly languagesjump (Arabic,to Hebrew,their etc.),personal on par with LTR.queue.

  • ReducesHelps layoutmanage issuesdaily workload and confusion for international clients.responsibility.

WIFOX-190583 – Mobile/tablet(Already formabove) paddingscorrect adjustedcreator and last author
FormThis paddingsalso inboosts ownership clarity—list views now clearly show who opened the Clientticket and who last replied.

5. Multi‑brand and client‑side behaviour

WIFOX-633 – Multi‑trading projects: correct redirect after login
In deployments with multiple trading projects/brands, clients are now redirected to the correct brand’s Trading Area after login, based on mobiletheir andproject tablet were updated to match approved design values (different vertical spacing for ≤768px and ≥769px), including removal of an extra padding block.configuration.
Business impact:

  • FormsAvoids lookcross‑brand confusion and feelwrong more balanced on phones and tablets.environments.

  • LessCritical unnecessaryfor scrolling,multi‑brand clearersetups focussharing oninfrastructure.

    primary
    • actions.

WIFOX-621 – Brand‑specific email templates for Tickets
Ticket‑related emails sent to clients now use brand‑specific templates (logo, colors, legal text, links) according to the project/brand the client belongs to.
Business impact:

  • Consistent communication that matches the brand clients know.

  • Better legal/compliance handling for multi‑entity businesses.

WIFOX-648 – Avoid client‑side caching issues for updated content
Client‑facing pages now include improved cache‑busting/versioning so that updated scripts and content are correctly fetched instead of using stale browser cache.
Business impact:

  • Clients experience new fixes/features immediately after release.

  • Fewer “it still looks broken for me” scenarios due to old cached assets.

5.6. TradingSecurity UXand micro‑improvementsaccess management

WIFOX-569589 – Closer default chart view (1 hour)
(Already listedabove) abovesecure, underidempotent tradingprovider terminal)callbacks
Besides double‑deposit prevention, this hardening also improves resilience against unexpected or repeated provider calls.

WIFOX-598 – charts(Already nowabove) openexplicit inaccess to “Waiting for client” tickets
Helps ensure that client‑pending cases aren’t forgotten and can be managed proactively.

If you share specific descriptions for any of these tickets where you want even more precision (e.g. a closerspecial timeframe,rule makingor recentedge datacase), easierI can refine the corresponding bullet to analyse.match your internal wording exactly.

1 Source
Back to top