Upvest: investment APIs, operating models and custody responsibilities

Upvest supplies investment infrastructure to financial businesses building their own customer proposition. Its Investment API connects trading, settlement, custody and back-office processing, while the client controls the distribution experience. Banks, brokers, wealth managers and fintechs are the intended institutional customers.[1]

The product range includes stocks, ETFs, mutual funds, money-market funds, ELTIFs, bonds and securitised derivatives. Published workflows include fractional investments, savings plans, portfolio investing and market, limit and stop orders. Cash can be handled through prefunding or post-trade settlement, with securities transfers and corporate actions forming part of the operational scope. Availability needs to be matched to the instrument, country and chosen setup.[2]

The operating model changes the legal chain as well as the account structure. In the own-licence model, the client is the intermediary custodian for its end users and contracts with Upvest for custody. The choice should therefore precede the detailed integration design.[9]

In the UK, the marketed account range includes general investment accounts, ISAs, Junior ISAs and SIPPs. Upvest can act as ISA manager or support a client that retains that role. These are country-specific configurations; a UK wrapper should not be treated as a standard account available throughout the European offering.[10]

The September 2026 SIPP description covers contributions, pension transfers, tax-relief investment, accumulation and decumulation pots, reporting and payroll. It also describes human handling of sensitive cases and operational visibility through Upfront. This identifies components for an institution’s pension proposition; the particular assets and withdrawal journeys remain part of that institution’s agreed product design.[11]

The architecture uses asynchronous REST APIs: accepting a request and completing its financial operation are separate events. OAuth 2.0 and signed HTTP messages protect API access, while webhooks communicate state changes. Upvest describes a cloud architecture on Google Cloud and Kubernetes. Its public technology material also says changes are intended to remain additive and backward-compatible.[4]

The operations service can cover selected processes or a broader back-office remit. Published functions include order and mistrade handling, settlement, cash and position reconciliation, account changes, corporate actions and reporting. Upfront gives client operations teams a user interface for inspecting transactions, settlement and information generated through the API.[5]

Upvest says pricing is tailored to the client’s product scope. Its public FAQ does not set out a complete numeric tariff, minimum commitment or implementation charge. The commercial proposal needs to specify the selected services and operating model.[3]

The UK page advertises trading below £1 per trade. That headline is not a complete tariff: the page does not establish that every instrument, account, custody service, migration and support arrangement is included at that price.[10]

The documented fee engine concerns charges the client levies on end users. Upvest can calculate and collect agreed asset-based fees, or collect an amount calculated by the client; collection can involve selling investments to cover a fee. Transaction fees can be absolute, relative or tiered. These capabilities should not be confused with the business-to-business price of Upvest’s infrastructure.[18]

Fee reporting has a separate control boundary. Supplying an ex-ante fee estimate does not collect that fee, and the client must keep estimates consistent with actual charges. Upvest includes fees it processes in ex-post reporting; fees collected outside its system must be supplied for the annual reporting process.[19]

The sandbox simulates dependencies that are real in production. It supports integration development, but a successful simulated transaction does not establish live settlement or customer-funds handling. Upvest says implementation time depends on the scope and offers integration and migration assistance.[3]

Virtual-cash management is limited to the single-account, post-trade-settlement setup. Its backlog lets eligible cash-reducing operations wait for funding instead of immediately failing for insufficient money.[16]

The virtual-cash guide requires the relevant administration scope and lifecycle subscriptions. An increase becomes available for trading only after confirmation; a decrease can remain queued until funds arrive. The settlement and treasury procedure handles payment for the relevant orders. The application must therefore distinguish request receipt, usable balance and settled cash rather than treating them as one event.[15]

Securities transfers currently require whole units and generally retain the same beneficial owner; the guide excludes fractional transfers and ownership-changing events such as gifts or inheritance. Incoming transfers require the client to check instrument availability and account readiness. For outgoing requests, the client validates the instruction and signature. German acquisition and tax data use Taxbox in the described workflow, with the CPB integration applying to the single-account models. These transfer assumptions need to be reflected in migration plans.[17]

The published October 2025 execution principles, framed under German law, describe a restricted venue and instrument set with automated venue selection and fallback. Execution quality is assessed using total consideration, including relevant third-party costs. Specific customer instructions can constrain that process, and off-venue trades can be reversed under a counterparty’s mistrade conditions. The document distinguishes commission execution from fixed-price dealings and identifies separate arrangements for fractional transactions. Its scope should be matched to the contracting entity and transaction type.[20]

Upvest describes dedicated partner support and specialist handling of complex operational issues. Upfront provides an additional self-service route for client teams. The inspected public operations page does not establish a universal response-time or recovery-time commitment; these belong in the service agreement for the chosen operational scope.[5]

The complaints policy asks for identifying information and details of the issue. It says a response is usually provided within 15 days, with an interim explanation when more time is required. This complaint-handling process is separate from a contracted incident-support response target.[22]

Upvest describes its German permissions as covering brokerage, execution, custody, proprietary dealing and relevant currency conversion, and identifies Upvest Securities Ltd as FCA-authorised for dealing and asset safeguarding/administration. These activity descriptions are the company’s statements. Full live BaFin and FCA permission schedules were not retrievable for this profile, so the descriptions should not be read as an independently verified list of every permission or restriction.[24]

The company also specifies permissions the distributing client must bring: an EU order-reception/transmission or applicable national framework, or an appropriate tied-agent arrangement; in the UK, arranging permissions or an appointed-representative arrangement through its partner network. Taking Upvest’s licence model does not remove that client-side requirement.[24]

Upvest dates its foundation to 2017 and identifies Berlin as its headquarters, with additional hubs in London and Tallinn.[3]

Upvest’s March 2026 financing announcement distinguishes $90 million of equity funding from a $35 million debt facility that was still being finalised. It should not be treated as confirmation that the entire headline $125 million had closed on that date. The announcement describes continued independent management by the founders.[27]

Operator

Upvest GmbH; investment services through Upvest Securities GmbH and Upvest Securities Ltd

Service scope

Institutional investment APIs, trading, settlement, custody and operational services.

Customer types

Banks; Brokers; Wealth managers; Fintechs

Delivery

API; Hosted; Managed service

Pricing publication

Quote only

Pricing scope

Scope-dependent commercial proposal; UK trading headline is not a full tariff.

Implementation

Operating-model selection, credential setup, sandbox integration and scoped migration.

Support

Partner support, Upfront operations interface and public service-status reporting.

Permissions and regulatory scope

Company-described German and UK permissions; accessible CNMV and HMRC records have narrower scopes.

Provider metadata checked 21 Oct 2026Source 1Source 21Source 2Source 4Source 5Source 3Source 10Source 12Source 24Source 25Source 26

The current FAQ still marks crypto as forthcoming and says retail investors cannot open accounts directly with Upvest. Its discussion of Kafka event streams also labels them as forthcoming. Product planning should therefore distinguish the available institutional service and webhook interface from these announced extensions.[3]

On 15 October 2026, Upvest announced a partnership with Quirin Privatbank and quirion. The described sequence begins with an Altersvorsorgedepot launch in early 2027, then migrates quirion users, followed by Quirin’s private-banking investment business. The announcement establishes a planned programme, not a completed migration as of the profile’s inspection date.[28]