FAQ

Need deeper technical detail? See Performance & Technology, Pilots, and Technical Docs.

General

What is PraxisNet?

PraxisNet is a settlement platform that helps teams process payments quickly while keeping records consistent and easy to audit.

How is PraxisNet different from a blockchain?

PraxisNet is focused on business settlement outcomes first: faster processing, fewer mismatches, and clearer records for finance and audit teams.

What does “deterministic settlement” mean?

It means the same payment input gives the same result every time, so teams are not arguing over which report is right.

Why does determinism eliminate reconciliation?

Because fewer mismatches are created in the first place, teams spend less time doing manual reconciliation and exception cleanup.

Performance

What are your current TPS benchmarks?

Current strict benchmark profiles show approximately ~17.8k–18.1k committed TPS (20k tx/block profile) and ~73k–84k committed TPS (100k tx/block profile), with validator-path runs around ~340k–380k. See Technology and Benchmark Methodology.

How does lane-based scaling work?

Work is spread across controlled parallel paths so the system can handle more volume without losing consistency.

What is committed TPS vs ingest TPS?

Ingest TPS is how much arrives at the front door. Committed TPS is how much is actually accepted and written as final state.

Do you publish raw artifacts?

Yes. PraxisNet publishes test and benchmark artifacts to support independent review during technical evaluation.

PSP & Payments

How does PraxisNet integrate with Stripe?

PraxisNet takes Stripe API and webhook events, then processes them in a way that prevents duplicates and keeps settlement records consistent.

Can this run in the cloud with PSP-style requirements?

Yes. PraxisNet is designed to run in cloud deployments while preserving key PSP controls: fast charge/refund handling, duplicate-event protection, out-of-order protection, and replayable audit trails.

What tests have you passed?

The platform has passed card lifecycle, replay, and event-ordering suites, including high-volume ingress profiles.

How do you handle duplicate webhooks?

Duplicate events are detected and ignored so they do not apply twice.

How do you handle out-of-order events?

Older events are marked stale and ignored when a newer valid state is already committed.

How do you handle refund-before-charge?

The engine treats edge ordering safely so settlement state does not drift from valid history.

How do you ensure deterministic replay?

When events are reprocessed, the platform checks that outcomes match prior results so duplicate charges/refunds are not introduced.

Can PraxisNet replace a PSP ledger?

It can serve as a deterministic settlement layer that reduces reconciliation burden. Final architecture depends on your controls, regulatory scope, and rollout plan.

Compliance & Governance

Is PraxisNet governed?

Yes. Governance and operational controls are part of the platform design for enterprise use.

How do you ensure auditability?

PraxisNet keeps traceable records that show what happened, in what order, and why the final balance is correct.

What is a state root?

Think of it as a tamper-evident summary hash of the ledger at a point in time.

How does deterministic replay support audits?

Auditors can re-run the same input history and confirm they get the same final result.

Architecture

What is the execution model?

PraxisNet uses deterministic validation and commit rules so accepted transactions produce stable, repeatable outcomes.

How do lanes work?

Lanes are parallel execution paths with deterministic controls that improve throughput while preserving correctness.

How do validators reach agreement?

Validators follow the same deterministic ruleset and converge on the same committed state from the same valid inputs.

How do you guarantee deterministic ordering?

Ordering controls reject stale events and enforce consistent commit behavior under replay and high load.

Pilots

Who is PraxisNet for?

PSPs, payment operations teams, gaming and digital commerce platforms, and enterprise settlement organizations.

What does a pilot include?

Pilots typically include integration setup, test scenarios, deterministic replay checks, and measurable success criteria.

What data do you need?

Usually event schemas, transaction workflows, and representative traffic patterns. Scope is minimized to what is needed for validation.

How long does integration take?

Timelines vary by complexity, but many teams can start with a phased integration quickly through API and webhook pathways.

Reliability

What happens if a node fails?

The network is designed for resilience so processing can continue and state integrity can be verified during recovery.

How do you handle network partitions?

The system favors consistent state progression and safe recovery over unsafe writes during partition conditions.

How do you recover from stale events?

Stale events are identified by ordering rules and ignored when they would regress already-committed state.

How do you guarantee no double-refunds?

Replay-safe event handling and deterministic deduplication prevent duplicate refund effects from being committed.

Roadmap

What’s next for throughput?

Next steps focus on broader lane scaling validation and continued publication of measured performance artifacts.

What’s next for multi-rail support?

PraxisNet is expanding toward deeper multi-rail orchestration patterns across payment and settlement workflows.

What’s next for compliance tooling?

Upcoming work includes stronger audit tooling, reporting support, and operational controls for regulated environments.