Clear answers before you connect the work.

Palyra is an independent payment-route control plane for cross-border businesses using two or more providers. It connects payment operations, settlement truth, reconciliation, route intelligence, and governed execution across merchant-owned provider relationships.

An authenticated workspace accepts controlled operational data and turns normalized evidence into payment, route, provider, market, settlement, and reconciliation views. Teams can export a finance close pack, simulate bounded route rules in shadow mode, and ask Palyra Intelligence questions grounded in the active evidence. Persistent Route Passports, recurring Drift Monitor runs, and durable decision records are being connected in stages.

The current workspace does not initiate payments or change live routing. Palyra’s controlled-execution layer is being built to act through merchant-owned provider accounts only after explicit policy approval, traffic limits, circuit breakers, and rollback controls. Palyra does not hold customer funds.

Palyra begins above the existing stack and works with the providers a merchant already chose. Over time it can become the routing and execution layer, while the merchant keeps its provider accounts, evidence, policies, and operating history.

CSV is one controlled ingestion method. An authenticated workspace accepts size-limited, sanitized files, validates their schema, and stores normalized evidence under the relevant workspace and source. Raw files are not attached to contact or feedback submissions.

Card numbers, CVV or CVC, expiry dates, customer names, emails, phone numbers, addresses, passwords, API keys, access tokens, and other secrets.

Recurring, least-privilege provider connections are on the roadmap. Each connection must pass provider-specific mapping, security, permission, and runtime checks before it is presented as available.

Palyra does not currently claim SOC 2, ISO 27001, or PCI certification. The product is designed to avoid cardholder data and to introduce production access only with the controls required by the data and workflow.

Palyra is provider-neutral. Controlled exports can be mapped when their fields and semantics are verifiable. Production provider coverage will be published only after each mapping has been tested against an authorized customer workflow.

The current engine uses explainable reference, currency, amount, timing, state, settlement, duplicate, and fee checks. It shows the rule and source evidence instead of silently forcing records to agree.

Yes. Export windows, time zones, provider semantics, retries, and reference mappings can all change the result. Palyra keeps uncertainty visible and asks an operator to verify material findings against source systems.

It investigates payment operations, explains the selected evidence, cites what it used, states confidence and uncertainty, and prepares the next reviewable action. It cannot invent payment truth or change a route outside the customer's approval controls.

Growing cross-border businesses already operating at least two providers, with a team responsible for payment performance, reconciliation, settlement, expansion, or route decisions.

Create an account for the self-service workspace, or contact Palyra when you need a guided walkthrough, provider-specific mapping, security review, or implementation support.

No card is requested when creating a workspace. Team deployments are scoped around provider coverage, markets, evidence volume, refresh cadence, users, and implementation needs before paid work begins.

Yes. A work email is useful when available, but a personal address is accepted. Your account still receives the same email verification and workspace protections.