smartTrade Technologies: institutional FX, payments and post-trade infrastructure

smartTrade supplies electronic-trading and payments technology to financial institutions. The offering connects several stages that are often purchased separately: liquidity access, price construction, distribution, execution workflows and post-trade processing. Its platforms are software infrastructure for the institution’s business; they do not themselves establish the institution’s legal authority to deal, lend or provide payments.[1][2]

The documented bank implementation at Banco de Credito del Peru illustrates a distribution use case: centralise liquidity and provide different channels through which customers and sales teams interact with FX services. That is more specific than a generic claim of faster trading. It shows the type of workflow the software can support, but does not establish a performance result for another bank’s deployment.[10]

AlgoBox makes the boundary between vendor functionality and institution-authored logic explicit. The framework can interact with market information and execution workflows, while the institution defines its own algorithmic behaviour. From an operational perspective, a version change in that custom logic is a separate event from a vendor-platform upgrade. Both need a controlled release process; hosting a strategy inside the platform does not validate the strategy’s risk or profitability.[3]

A dated March 2023 announcement describes smartTrade’s commercial approach as a flat-fee model rather than volume-based charging. That is useful historical context, not a current binding price list. The public pages reviewed do not disclose a universal cash subscription price for LiquidityFX, Flow, AlgoBox or the payments platform. The scope, interfaces, operating model and support commitments still need to be established in the customer’s offer.[9]

A deployment can touch both the market-facing and customer-facing sides of a bank. Liquidity connections, price rules and order processing must coexist with customer identity, credit and payment records. For the Commercial Banking and Payments platform, the published functionality includes approval workflows and different payment instructions. The implication is that implementation includes authority and reconciliation rules, not only a graphical interface.[2]

The SMBC Nikko case documents a fully hosted and managed service. It establishes that this delivery route exists; it does not turn a named customer’s project into a universal migration promise. A transition also needs to distinguish open trading exposure from records being transferred between software systems. The reviewed announcements do not provide a standard enterprise exit timetable or a universally applicable recovery-time commitment.[11]

The contact page separates regional sales and technical-support numbers and also distinguishes support for the kACE business. That separation matters during integration: a group acquisition does not automatically mean that every legacy support entitlement, incident queue or contractual service level has already been consolidated. A staffed response commitment should be taken from the customer’s service agreement, not inferred from the existence of a telephone number.[5][8]

The reviewed material supports a technology and workflow-provider role. It does not establish that smartTrade is the customer’s FX counterparty, custodian or payment institution. In the dbHedge example, the bank supplies the financial execution service through an integrated technology route. The same distinction applies to regulatory reporting features: software can prepare and transmit records without transferring the institution’s responsibility for their completeness or legal accuracy.[4][1]

The provider is smartTrade Technologies SAS, with its headquarters in Aix-en-Provence, France. Its December 2025 kACE announcement was initially an acquisition announcement; the February 2026 corporate update subsequently states that the transaction completed at the end of 2025. This profile therefore treats the acquisition as completed, while keeping the separate question of product integration open.[5][7][8]

The April 2025 TA announcement is an investment agreement involving management and an intended exit by Hg. It is not used here as independent proof of every later ownership percentage or closing condition. The relevant product developments are evidenced separately, so the service description does not depend on reconstructing an undisclosed current share register.[6]

Operator

smartTrade Technologies SAS

Service scope

smartTrade supplies institutional trading and payment workflows, including LiquidityFX, AlgoBox and the new Flow post-trade platform. The profile examines integration boundaries, commercial evidence, regional support and the completed kACE acquisition.

Customer types

Banks; Institutional brokers; Financial institutions

Delivery

SaaS; Hosted; API; Managed service

Pricing publication

Quote only

Platforms

LiquidityFX; AlgoBox; Commercial Banking and Payments; Flow; FXD

Implementation

Institutional projects combine liquidity, distribution, bank-system interfaces and operating responsibilities. Hosted and managed customer deployments are documented.

Support

Regional technical-support and sales routes are published; contractual response and recovery commitments were not publicly established.

Permissions and regulatory scope

The documented role is technology supply. Integrated banks and customers retain their own execution, payment and regulatory responsibilities.

Provider metadata checked 20 Oct 2026Source 1Source 5Source 11Source 4

Flow’s September 2026 release adds a standalone post-trade option. That is distinct from replacing the front end; migration still requires project-specific record mapping and testing.[1]

The strongest comparison with another provider is therefore by workflow ownership: who connects liquidity, sets prices, approves customer actions, runs custom logic and holds the authoritative post-trade record. A single feature count would conceal these differences. This is an analytical reading of the published product boundaries, not a test of smartTrade against a competitor.[3][2][10]