Skip to main content

Release 2.5.0

1. Trading & Requests: fewer mistakes, clearer flows

WIFOX-531 – “Replace only close” for ticket type “Change Stop Loss only”
In Trading Area tickets, the “Change Stop Loss only” ticket type now uses a dedicated “Replace only close” action that updates only the stop‑loss level of an order, without unintentionally changing take‑profit or other parameters.
Business impact:

  • Reduces the risk of traders or support staff accidentally changing the wrong parts of an order.

  • Makes partial order modifications (only SL) safer and more predictable.

WIFOX-583 – Requests/Tickets: show correct creator and last message author
The Requests/Tickets lists and headers now correctly show:

  • who created the ticket, and

  • who wrote the last message, regardless of whether it was done in CRM or Trading Area.
    Business impact:

  • Support, sales, and compliance teams see the real conversation owner and last responder at a glance.

  • Easier prioritisation and follow‑up—no more guessing which side “has the ball”.

WIFOX-598 – Filter by “Waiting for client” status in Requests
In the Requests module, tickets that are in “Waiting for client” (from Trading) can now be filtered and surfaced explicitly.
Business impact:

  • Support managers can quickly find all cases where the next move is on the client.

  • Better control of aging 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 be 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 duplicate callbacks.

  • Less manual reconciliation and fewer finance corrections.

WIFOX-559 – Card transactions: display masked card and Bank Name in UI
The Transactions table now shows:

  • Masked card number (first4********last4) for card payments.

  • Bank name for card/acquirer.
    All values are non‑sensitive and follow PCI‑style masking rules.
    Business impact:

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

  • Easier to spot patterns (e.g. specific banks/cards failing) and escalate correctly.

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:

  • Finance and compliance teams can run more complex searches reliably.

  • Less waiting and fewer “please try again later” errors during investigations.

3. Requests/Tickets messaging: richer, consistent conversations

WIFOX-607 – Requests/Tickets: show which side wrote each message (client vs manager)
Messages in Requests/Tickets now clearly indicate whether they were written by a client (in Trading Area) or a manager/employee (in CRM), with aligned styling across both systems.
Business impact:

  • Everyone can follow the conversation context more easily.

  • Reduces misunderstandings in multi‑party communication.

WIFOX-570 – Requests/Tickets: fix lost messages due to race conditions
A race condition that could cause some messages to not appear or appear out of order across CRM and Trading Area has been fixed.
Business impact:

  • Conversations remain complete and synchronised in both interfaces.

  • Reduces support overhead from “I sent it but you don’t see it” cases.

WIFOX-586 – Unified message timestamps with timezone awareness
Message timestamps in Requests/Tickets now use a consistent format with clear timezone/relative time, harmonised between CRM and Trading Area.
Business impact:

  • Easier for global teams to understand when exactly a message was sent.

  • Supports accurate SLA monitoring and audit.

WIFOX-514 – Preserve and sync read/unread state for messages
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 system now blocks sending messages that contain only spaces/new lines with no actual text.
Business impact:

  • Keeps threads clean and readable.

  • Reduces noise and accidental “blank” replies.

4. Requests/Tickets: better ownership and workflow tools

WIFOX-512 – “Assigned to me” quick filter in Requests
A one‑click “Assigned to me” filter has been added in the Requests module.
Business impact:

  • Each agent can quickly jump to their personal queue.

  • Helps manage daily workload and responsibility.

WIFOX-583 – (Already above) correct creator and last author
This also boosts ownership clarity—list views now clearly show who opened the ticket 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 their project configuration.
Business impact:

  • Avoids cross‑brand confusion and wrong environments.

  • Critical for multi‑brand setups sharing infrastructure.

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.

6. Security and access management

WIFOX-589 – (Already above) secure, idempotent provider callbacks
Besides double‑deposit prevention, this hardening also improves resilience against unexpected or repeated provider calls.

WIFOX-598 – (Already above) explicit access 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 special rule or edge case), I can refine the corresponding bullet to match your internal wording exactly.

1 Source
Back to top