Aurora Nexus connects MT5 accounts, onboarding, wallets, payment approvals and introducing-broker workflows in one back office and client portal. Give your team a shared client record and a clear path from registration to ongoing service.
For brokerage operations, sales, onboarding and client-service teams.
01
MT5 operations
Provision accounts from verified client identity. Bring account data, positions, leverage agreements, group settings, history and statements into the same workflow.
02
Payments & wallets
Manage deposits, withdrawals, client balances and transaction history. Review payout requests, attachments and risk flags through a shared approval queue.
03
Onboarding & verification
Support individual and corporate registration, document collection, KYC workflows and payout identity matching, with recorded review steps.
04
Client portal
Give clients access to their account view, funding, internal transfers, support tickets and notifications through one portal.
05
IB & growth tools
Connect referral links, downline views, commission tracking, rewards and IB payouts with campaign tools and sales-performance reporting.
06
Operational controls
Permission-gated administration, signed action links, payment replay protection and audit trails make important actions traceable.
AI features
AI features in Aurora Nexus
AI assistance across the client lifecycle.
Aurora NexusEnterprise
Client Summary
One view of a client before a call or a decision.
When
From Analyze client on any client record.
Reads
Account status, KYC and onboarding progress, deposits and withdrawals, MT5 accounts, open tickets and recent interactions.
Produces
A summary with a suggested next step, each fact linked to its record.
Who
Account managers, onboarding and support teams.
Where
Analyze clientOnboardingWallets & approvals
Never
Approves KYC, withdrawals or account changes.
Aurora NexusEnterprise
Reply Drafts
Follow-ups and support replies drafted from the client’s record, in Arabic or English.
When
From a support ticket, an onboarding step or a client profile.
Reads
The ticket or request, the client’s status and your approved message templates.
Produces
An editable draft in the client’s language.
Who
Support, onboarding and account teams.
Where
Support ticketsOnboardingClient profile
Never
Sends a message. A staff member reviews and sends every reply.
See each feature at work
Nexus / Client SummaryAI
Summarize Omar M. before my call.
Active since March, with 2 MT5 accounts and equity of $48.2K.¹ A 1,500 JOD withdrawal to his CliQ alias is pending approval.²
Last contact: 14 Sep, about leverage on gold. Referred by IB #1027.³
Sources
1Accounts · MT5 equity11:40
2Withdrawal queue10:02
3CRM timeline · IB record14 Sep
Open client recordDraft follow-up
Withdrawal approval stays in the queue with its identity checks.
Sample data
What applies to all four
Enterprise edition
AI features are included in the Enterprise edition. The Standard edition does not include them.
Arabic and English
Every feature works in Arabic and English, for questions, summaries and drafts.
Third-party AI processing
AI processing is provided by a third-party AI service. The provider, data handling and region are set out in your agreement.
Inside your existing views
The features appear in the views your teams already use, such as Analyze client, Deals history and Alerts, not in a separate tool.
Your data. Your permissions. Your decision.
01
Reads governed product data
Through Aurora’s own APIs. No direct access to trading servers or databases.
02
Uses your permissions
It sees only the books and clients the signed-in user can see.
03
Cites every figure
Each number links to the record and timestamp behind it.
04
Calculations stay in the engines
Exposure, P&L and balances come from Sentinel and Nexus, not the model.
05
A person approves actions
Hedges, limits, withdrawals and messages go through the product’s controls and audit trail.
Each step is a separate control, applied to every request.
Regional funding and payout workflows sit alongside cards, bank rails and crypto settlement. A central exchange-rate registry supports consistent conversions. Supported provider settings are configurable; new connectors are assessed separately.
MetaTrader 5
Gate2Pay
PayTabs
HyperPay
Paysafe
UWallet
B2BinPay
eFAWATEERcom
CliQ
Activation depends on supported connectors, provider onboarding and the agreed scope. An integration does not imply a commercial partnership.
Prove the fit. Then put it to work.
01
Assess
Map client, payment, IB and reporting workflows in the CRM Fit Assessment.
02
Configure
Configure roles, MT5 groups, verification steps and supported payment providers.
03
Validate
Test onboarding, payment reconciliation and client journeys before launch.
04
Enable
Train operations and client-facing teams, then measure adoption after launch.
Frequently asked questions
Who owns Aurora Nexus?+−
Aurora Nexus is an Aurora-owned CRM product. Aurora provides the product and its implementation; external trading, payment and verification services retain their own provider roles.
Are all payment integrations available to every brokerage?+−
Availability depends on the supported connector, provider onboarding and your operating requirements. The CRM Fit Assessment confirms the integration scope.
Which edition includes the AI features?+−
The Enterprise edition. AI features are not part of the Standard edition. They work in Arabic and English and are processed by a third-party AI service under your agreement.
Next step
CRM Fit Assessment
Assess product fit, data access, integrations and team workflows. Receive a written implementation recommendation, including which AI features fit your teams.
Every Aurora engagement starts with a short, no-commitment diagnostic and a written deliverable. No price list — we scope your environment, then quote.
