Requests from your existing systems
Submit transaction instructions through API, retain your own business references and follow the request through quotation, execution and settlement.
Momentum OTC · Dubai, UAE
OTC execution.
Integrated with
your systems.
Momentum combines client requests, trading, treasury and transaction records in a working platform. We are developing APIs that connect this workflow directly to clients’ finance, ERP and accounting systems.
Working platform. Client integration and regulatory preparation in progress.
RequestsTradingTreasuryReporting
Connect. Exchange. Settle.
01 /Working software
Requests, treasury and reporting.
Already in the platform.
Client work, treasury controls and team oversight share the same operational records. Explore three views of the working system below, or open the full walkthrough for the details. These are actual application screens with demonstration data.
Operational core availableClient & manager
The request.
Its conversation.
Its record.
Instructions, quotations and transaction updates stay together. The client and manager work from the same request context.
- Conversations linked to requests
- Rates and settlement instructions
- Beneficiaries reviewed by treasury
Actual application screensDemonstration data
02 /Client integration programme
Connect transactions
to your accounting.
The API programme will let businesses submit and track OTC requests from their own systems, then retrieve statements and reports as structured JSON. Excel, PDF and CSV outputs will support the same reporting workflow.
Records your finance team can use
Retrieve transaction records, statements and reports in JSON for automated processing. Use Excel, PDF or CSV when a file-based workflow is required.
Less re-entry and manual reconciliation
Map client references to transaction and payment records. Feed the resulting data into your finance systems to reduce spreadsheet preparation, repeated data entry and manual accounting work.
Client systems ↔ MomentumIN DEVELOPMENT
ERP / finance / accountingAPI
Request + your business reference
Quotation, checks and settlement
Transaction record + statement
{
"client_reference": "ERP-20261019-001",
"side": "sell",
"send_amount": "100000.000000",
"send_currency": "USDT",
"receive_currency": "AED",
"beneficiary_id": "BANK-TEST-A3-01",
"settlement_method": "bank_transfer"
}100,000 USDT × 3.6740Gross: 367,400.00 AEDFee 0.3%: 1,102.20 AEDNet settlement: 366,297.80 AED
Fee shown as 0.3% of the gross AED amount, deducted before payout. Illustrative data structure. The external API contract is under development.
Planned reporting outputs
JSON / APIExcelPDFCSV
03 /Screening and customer due diligence
Deeper checks.
Less manual handling.
We are building automated wallet screening and risk-based customer review into the transaction workflow. The aim is to shorten routine processing while examining wallet exposure, ownership and transaction context in greater depth.
VARA compliance frameworkWorkflow under development
Collect data → screen → review exceptions → approve → monitor.
Automation will handle collection and screening steps. Flagged cases will be routed to accountable reviewers, with findings and decisions retained in the transaction record.
Automated wallet screening
In progressThe planned blockchain-analytics integration will examine wallet history, transaction links, direct and indirect exposure to high-risk counterparties, sanctions indicators and suspicious fund-flow patterns. Results will inform transaction review and ongoing monitoring.
KYC / KYB policies
In progressPolicies are being developed to meet applicable VARA AML/CFT requirements: identity and beneficial-owner verification, corporate ownership, the purpose of the relationship, source-of-funds review and enhanced due diligence where required.
Faster routine processing
Development focusCollect documents and transaction data once, route checks within the same workflow and reuse valid records where policy permits. This reduces repeated requests, hand-offs and manual preparation without bypassing review requirements.
Evidence linked to the transaction
Operational coreClient records, approval decisions, payment references and execution events remain connected. Screening results will extend this record and support structured reporting through the client integration layer.
04 /Transaction controls
A defined process
from request to settlement.
Client-facing work, liquidity decisions and payment execution use the same transaction context. Each stage has an owner and a recorded outcome.
Request and instructions
The client submits the direction, amount and settlement requirements. The request and its conversation remain linked to the client record.
Checks and quotation
Client and beneficiary checks precede execution. The quotation records the rate, final amounts and settlement terms for confirmation.
Liquidity and receipt
Trading controls cover available own liquidity and partner execution. Treasury confirms incoming funds; client funds are accounted for separately from the own trading book.
Settlement and records
Execution is confirmed against payment evidence. Transaction records support reconciliation and reporting, with external API access being developed for clients’ finance systems.
05 /Development and licensing
Development and
licensing timeline.
The operational platform is available for testing. Client integration, screening implementation and regulatory preparation are the current workstreams.
Platform development
Client and staff workspaces, request and quotation handling, trading controls, treasury execution and reporting. Ongoing testing and refinement of the operational workflow.
In progressIntegration and screening
Client APIs for requests and JSON reporting, Excel/PDF/CSV export coverage, banking and liquidity connections, automated wallet screening and KYC/KYB procedures.
In progressIDQ submission
& receiving ATI
Submit the Initial Disclosure Questionnaire (IDQ) through DET or the relevant Free Zone, with the business plan, ownership and management information. Progress the review and supporting documentation toward Approval to Incorporate (ATI).
Starting 19 Oct 2026Full licence
& operational launch
Following ATI, complete incorporation and operational setup, submit the full VASP licence application and address review requirements. Begin live services after the licence and operational conditions are satisfied.
Subject to authorisationATI supports incorporation and operational setup; it does not authorise virtual-asset services. The current portal is a controlled development environment with test transactions. Live services are subject to licensing and applicable operational conditions. VARA licensing process
Momentum OTC
Review the platform
and integration scope.
The working portal demonstrates the operational core. The project overview sets out the API, screening and licensing programme.