Skip to content
casino.limo
P

Praxis Tech

Praxis Tech owns payment orchestration software that sits between an operator cashier and external PSPs, acquirers, banks, wallets, and local payment methods. It standardizes integrations, routing, cascading, tokenization, checkout, and reporting.

Page updated

Visit website
Company details
Named companyPraxis Tech Ltd.
Organization typecompany
Statusactive
Websitepraxis.tech
Research checked
Main categoryiGaming Payment Providers

Praxis Tech Ltd., Cyprus registration number HE 410576, is the website operator, platform company, and customer-facing entity. Current Cyprus corporate status and ownership remain unresolved. Each order must define its payment and data responsibilities.

Buyer decision brief

Use this summary to decide whether the offer belongs on your shortlist and which terms need a written answer.

Fit and use case

Editorial fit

Gaming operators outside the United States that already have, or plan to obtain, multiple PSP and acquirer accounts and need one technical layer to manage them.

Primary offer: Praxis Payment Orchestration

Primary offer delivery

  • iFrame
  • API

Integration boundary: The operator connects Praxis through the hosted cashier, hosted card fields, or direct API.

Critical contract questions

Start with unresolved terms, negotiated terms, and dependencies that need a named owner.

8 of 9

Resolve before shortlist

No usable standard answer is available on the public terms.

Software pricing and provider costsNot disclosed
Praxis Payment Orchestration · Commercial terms
Configuration and token portabilityNot disclosed
Praxis Payment Orchestration · Exit and portability

Fix in the signed order

The answer changes by operator, market, package, or negotiated order.

Payment data and PCI scopeSet in contract
Praxis Payment Orchestration · Operating responsibilities
Chargebacks and disputesSet in contract
Praxis Payment Orchestration · Operations and service

Assign outside supplier scope

The operator or another supplier needs a named owner for this dependency.

Settlement and reconciliationExternal dependency
Praxis Payment Orchestration · Operations and service

Reconfirm before signature

A current boundary is available, but the final order still needs to match it.

3 of 4 shown
Client and market approvalPublished boundary
Praxis Payment Orchestration · Market and approvals
Merchant relationshipsPublished boundary
Praxis Payment Orchestration · Contract and supplier
Software counterparty and rolePublished boundary
Praxis Payment Orchestration · Contract and supplier

Next buyer step

Ask Praxis Tech to resolve “Software pricing and provider costs” and “Configuration and token portability” before moving Praxis Payment Orchestration to a commercial shortlist. Then compare the answer with the complete product record below.

Confirm every selected term in the proposal and signed order. No price, market approval, availability, or contracting entity is implied unless it is stated above.

What this provider offers

1 offering

Praxis Payment Orchestration

Multi ProductFirst PartyAvailability: Standalone

Praxis Tech owns payment orchestration software that sits between an operator cashier and external PSPs, acquirers, banks, wallets, and local payment methods. It standardizes integrations, routing, cascading, tokenization, checkout, and reporting.

Praxis is not the acquirer or payment processor. It does not process or settle transactions or hold client funds. The operator still needs approved PSP contracts and merchant accounts.

Products

Praxis Cashier: Hosted and customizable cashier delivered through an iframe or redirect with connected provider methods.
Praxis Direct: Server integration for operators that keep their own cashier and connect orchestration through the Praxis API.
Hosted Payment Fields: Praxis-hosted card fields embedded in the operator payment page to reduce PCI scope while an external processor handles the payment.
Praxis Safe: Risk and fraud tooling used alongside the orchestration and connected payment providers.

Integration: The operator connects Praxis through the hosted cashier, hosted card fields, or direct API. Approved external PSP, acquirer, wallet, and local-payment accounts require their own credentials and commercial relationships.

Delivery options

iFrame

Delivery model

Hosted cashier embedded in or linked from the operator site, with transactions routed to the operator's external payment providers.

Operator license
Operator
Merchant of record
Unknown
Player data controller
Unknown

Included

  • + Hosted checkout
  • + Provider and method presentation
  • + Routing and cascading
  • + Tokenization and reporting

Not included

  • ! Acquiring
  • ! Payment settlement
  • ! Custody of merchant funds
  • ! Gambling license
  • ! PSP merchant accounts

API

Delivery model

Direct orchestration API for an operator-owned cashier and existing external provider relationships.

Operator license
Operator
Merchant of record
Unknown
Player data controller
Unknown

Included

  • + Unified payment API
  • + External PSP connectors
  • + Smart routing and cascading
  • + Transaction reporting

Not included

  • ! Acquiring
  • ! Payment settlement
  • ! Custody of merchant funds
  • ! PSP underwriting

Procurement record

Current product boundaries and the terms that still have to be fixed in the signed order or service agreement.

Known is usable now. Contract specific changes by order or market. Not disclosed has no usable standard term. Unknown remains unresolved. Outside provider scope is handled by the operator or another supplier.

Contract and supplier

Software counterparty and roleKnown
Praxis Tech Ltd. supplies payment-orchestration software. It does not process or settle transactions and does not hold client funds. External PSPs, acquirers, wallets, and method providers supply the underlying financial services.
Merchant relationshipsKnown
The operator needs its own approved merchant accounts and credentials with each financial provider connected through Praxis. A connector is technical availability, not a merchant account, acquiring agreement, or payment-method approval.

Implementation

Cashier, API, and hosted fieldsKnown
Praxis can provide a hosted cashier, a direct orchestration API for an operator-owned cashier, or hosted card fields. The implementation schedule must name each enabled connector, credential owner, route, fallback, token boundary, environment, and acceptance test.

Operating responsibilities

Payment data and PCI scopeContract specific
Hosted fields and hosted cashier routes place different data in Praxis systems than a direct server integration. The order needs PCI responsibility, controller and processor roles, token ownership, subprocessors, retention, fraud-data exchange, breach duties, and export rights for each route.

Operations and service

Settlement and reconciliationOutside provider scope
Praxis does not settle transactions or hold funds. It supplies transaction reporting and orchestration records; each connected financial provider controls its own settlement account, schedule, deductions, reserves, and bank reconciliation.
Chargebacks and disputesContract specific
Praxis can route payment and fraud data, while the underlying PSP or acquirer owns the financial dispute process. The operating model must assign alerts, evidence collection, representment, player contact, ledger adjustment, connector escalation, and provider fees.

Commercial terms

Software pricing and provider costsNot disclosed
Praxis software fees, implementation charges, connector charges, minimums, support tiers, and termination costs are not published. PSP processing rates, reserves, chargebacks, settlement, and foreign exchange remain separate provider contracts.

Market and approval scope

Client and market approvalKnown
Praxis accepts licensed iGaming clients subject to compliance review and excludes clients located in the United States. The accepted-license list is non-exhaustive; every operator, jurisdiction, activity, and connected PSP still requires approval.

Exit and portability

Configuration and token portabilityNot disclosed
Connector configuration, routing rules, tokens, transaction history, reconciliation exports, vault migration, credential handoff, termination assistance, and continued access after exit are not established outside the customer agreement.
Best for: Gaming operators outside the United States that already have, or plan to obtain, multiple PSP and acquirer accounts and need one technical layer to manage them.

Strengths

  • + The acceptance policy clearly defines Praxis as software and excludes processing, settlement, and fund custody.
  • + Operators can use a hosted cashier or retain their own cashier and integrate the orchestration API directly.

What to verify in procurement

  • ! Connected PSP counts describe available integrations, not active merchant accounts or guaranteed method availability for one operator.
  • ! Acquiring, reserves, settlements, merchant underwriting, accepted gambling licenses, and market approval remain with external financial providers.
  • ! Praxis does not accept clients located in the United States. Gambling applicants must hold an accepted license and pass compliance approval.
Reference documents6

More providers with similar products