Skip to main content
WaltzPay
Sign in
Controlled implementation · pilot preparation

Financial infrastructure built for emerging-markets commerce

WaltzPay is building a financial operating system that helps businesses connect providers, coordinate financial operations and maintain clearer control—starting with Collections.

One platform vision. Collections first. Capabilities released progressively.

See how it worksTalk to us

The problem

Fragmented finance is hard to see, and harder to trust

Businesses operating across more than one payment provider, or more than one market, run their financial operations in pieces. Collections, and eventually settlements, payouts and reconciliation, each live in a different provider dashboard, with no single, dependable record connecting what happened across any of them. That fragmentation is a financial-operations problem, not just a payments one — and it is the problem WaltzPay exists to work on, starting with the part of it that touches revenue first.

The vision

A financial operating system, not a single tool

WaltzPay is building a financial operating system that helps businesses connect providers, coordinate financial operations and maintain clearer control—starting with Collections.

Where the platform starts

Why start with Collections?

Collections is where revenue, provider performance, customer experience and financial records first meet. By making that flow more visible and controllable, WaltzPay establishes the foundation for broader financial operations.

Collections orchestration and routing for emerging-markets commerce.

Collections today

One control point instead of several dashboards

WaltzPay gives a business one clearer way to initiate, monitor, control and reconcile its collections, whichever licensed provider actually processes the payment. One record per collection, however many providers are involved behind it — so the question “what actually happened to this payment” has a single, checkable answer.

The licensed providers still process and settle the money. WaltzPay does not touch it — it is the record and the control layer that sits above them.

How it works

Three things happen behind every collection

  • Choosing the right provider automatically

    orchestration and routing

    Every collection is checked against a configured rulebook and sent to the provider set up to handle it — a person decides the rules, not an algorithm that learns or guesses.

  • A payment that hasn’t fully resolved yet

    an unresolved or ambiguous outcome

    Sometimes a provider hasn’t said yet whether a payment went through. Rather than guess, WaltzPay marks it openly as not-yet-final so nobody is told a payment succeeded before it actually did.

  • The paper trail that proves what happened

    reconciliation evidence

    The records a payment provider gives back once money has moved, kept in one place so what was collected can be checked against what the provider reports — later, not just at the moment of payment.

Evidence, today

What that looks like right now

One capability is in controlled implementation today, for a named set of merchants. It is shown here with exactly who it is available for — a capability is never presented as available generally.

Card collection through a provider-hosted checkout

A merchant's own backend requests a collection; WaltzPay selects the configured provider, records the charge canonically, and tracks the attempt through to a final outcome — or holds it explicitly when the provider has not made the outcome final.

Available for

Provider
Stripe (connector under certification)
Method
Card, via provider-hosted checkout
Currency
Two-decimal currencies only
Market
Pilot markets agreed per product
Merchant cohort
Named merchants, by invitation

The platform

What WaltzPay is building

Collections is the first piece. The platform it is part of is meant to grow into five connected areas — described here in plain terms, not as a finished feature list.

  • Financial Connectivity

    Connect payment providers, banks and financial systems through a more consistent integration layer.

  • Financial Operations

    Coordinate collections and, progressively, settlements, payouts, subscriptions and treasury workflows.

  • Financial Record

    Maintain a dependable, auditable record of financial events and their supporting evidence.

  • Financial Intelligence

    Turn financial activity into clearer reporting, forecasting and operational decisions.

  • Financial Controls

    Apply identity, approval, risk, security and governance controls consistently across financial operations.

Public status, by layer

Collections foundations
Available first / controlled introduction
Broader financial operations and reconciliation
In development
Treasury workflows and financial intelligence
Future capability
Regulated financial products
Subject to regulatory authorisation and market readiness

WaltzPay does not currently operate every workflow named above. Only Collections foundations are available today, and only to a named set of merchants — see the scope shown earlier on this page.

Control & trust

What WaltzPay is responsible for — and what it deliberately is not

WaltzPay chooses which configured provider handles a collection, keeps one canonical record of it, and retains the evidence to reconcile it. It does not hold, safeguard or settle money at any point.

See the full list of responsibilities, boundaries and the regulatory position

Five responsibilities, and no more

  • Provider selection

    Chooses which configured payment provider a given collection is submitted to, using deterministic, explicitly configured rules. Selection is governed and reviewable — it is not learned, inferred or self-tuning.

  • Canonical transaction records

    Keeps one normalised record per collection across providers, so a payment has a single identity regardless of which provider handled it.

  • Controls

    Applies idempotency, duplicate-charge protection and explicit handling of outcomes that a provider has not yet made final.

  • Reconciliation evidence

    Collects and retains the provider evidence needed to reconcile what was collected against what a provider reports.

  • Reporting

    Makes the canonical record and its supporting evidence available to the finance, operations and risk functions that own the payment.

What WaltzPay does not do

  • Hold, safeguard, pool or lend customer or merchant funds.
  • Operate wallets, stored value or customer balances.
  • Settle funds. Settlement is performed by the payment provider to the merchant’s own account.
  • Guarantee that a payment will succeed, or that any service will be uninterrupted.
  • Route around a failing provider automatically, or fail over between providers without operator action.
  • Optimise routing by learned or autonomous means.
  • Perform cross-border FX execution or corridor settlement.
  • Net settlement or treasury optimisation.

Who does what, legally

WaltzPay is not a licensed payment processor, acquirer, money transmitter or deposit-taking institution. Payments are processed and settled by licensed payment providers under their own authorisations and their own terms. WaltzPay does not hold, safeguard, pool or lend customer or merchant funds, and does not operate customer balances.

Present availability

Where this actually is

WaltzPay Collections is in controlled implementation and pilot preparation. It is not generally available, and it is not open for self-service sign-up.

Nothing on this site should be read as a statement that a capability is available to you today. Where a capability is described, the provider, method, currency, market and merchant cohort it applies to are stated alongside it.

Next step

If this sounds like your problem

Collections is in controlled implementation for a named set of merchants today. Reach out and we’ll tell you honestly whether, and when, it fits your business.

Talk to us