Tradaxi Review: Pricing, Control & Due-Diligence Passport
Tradaxi publishes unusually detailed self-service pricing and operating claims. PFV retains it as market research, but it remains on verification hold and is excluded from active matching and introductions until a reliable official commercial route is re-verified.
Published pricing
| Plan | Monthly | Setup | Published capacity |
|---|---|---|---|
| Starter | $700 | $0 | Up to 500 active traders |
| Growth | $1,200 | $0 | Up to 1,000 active traders |
| Pro | $2,000 | $1,000 | Up to 2,000 active traders |
| Enterprise | From $4,000 | Tailored | Unlimited |
Tradaxi states 0% revenue share, month-to-month plans and a 14-day trial. These are current provider-published terms and should be reconfirmed in a governing agreement before purchase.
Buyer Dependency Layer
| Dependency layer | Current evidence state | What the buyer still needs to establish |
|---|---|---|
| Exit & portability | partial | CSV import and migration support are public, but outbound exit-export rights, schema, timing, retention and deletion terms are not sufficiently evidenced. |
| Control & authority | partial | Buyer-controlled payment account ownership is provider-stated; exact breach override, risk-rule and payout approval authority remains unknown. |
| Integration dependency | partial | Webhook API/custom integrations are tier-stated; read/write/event scope, credential ownership and termination portability require contract review. |
| Operational continuity | partial | Tiered SLA and migration support are provider-stated; remedies, rollback and post-termination support require the governing contract. |
See the Buyer Dependency Model methodology →
PFV Due-Diligence Passport
| Area | Evidence state | Buyer implication |
|---|---|---|
| Public pricing | High transparency | Entry, limits, setup and support tiers are published. |
| Trader payment control | Provider-stated: buyer-controlled | Provider says trader payments go directly to the firm's own NowPayments account and Tradaxi does not touch funds. |
| Tenant isolation | Provider-stated | Provider states every database row is tenant-scoped. Treat architecture claims as provider evidence unless independently tested. |
| Data ownership / exit export | Unknown / partial | CSV migration imports are documented, but a complete outbound exit-export schema and contractual retrieval window are not publicly established. |
| API / webhooks | Partial | Webhook API appears on Pro and custom APIs on Enterprise; exact scope and portability should be tested. |
| SLA | Provider-stated, tiered | Pro lists an SLA contract; Enterprise lists 99.9% uptime SLA. Measurement, exclusions and remedies need contract review. |
| Migration | Provider-stated | CSV import is published for traders, challenges and payment history; hands-on migration is listed on Enterprise. |
| Dependency concentration | Medium | Core operating stack is concentrated, but the buyer is stated to control its payment account. |
| Risk / payout authority | Unknown | Exact breach override and payout approval authority should be written into the agreement. |
Why the hold remains
PFV's prior outreach route did not deliver reliably. Until an official working business route and contracting identity are re-verified, Tradaxi remains research-only regardless of how transparent the website appears.
What buyers should ask
- Full contracting entity, registration and governing jurisdiction.
- Exact SLA measurement, exclusions, service credits and escalation.
- Complete trader/account/trade/payout/KYC/affiliate export rights.
- Post-termination access and deletion timetable.
- Who controls breach overrides and payout approvals.
- Which payment, KYC, market-data and bridge dependencies are direct versus vendor-mediated.
Use the PFV due-diligence model, data ownership guide and vendor lock-in guide to compare these fields consistently.