Building
Provider APIs
Incremental sync and backfill through merchant-owned provider accounts, scoped to the least privilege the connection needs.
Developers
One lifecycle across provider-specific payment systems.
Palyra retains the source event and provenance while mapping provider behaviour into canonical payment, settlement, reconciliation, monitoring, and execution contracts.
Integration boundary
Connect evidence first. Add execution only under explicit control.
Palyra supports API, webhook, SFTP, and controlled-file ingestion behind a consistent connector contract. Live routing is a separate, approval-gated capability.
Building
Signed webhooks
Signature verification, deduplication, out-of-order convergence, replay, retry, and dead-letter recovery.
Available
Controlled data bridge
A validated file path for sanitized operational evidence while recurring provider mappings are verified.
Preview
Payments and routing API
One payment instruction and versioned route policy mapped to merchant-owned providers under approval and rollback controls.
Canonical lifecycle
Payment success is not the end of the record.
Each event keeps provider identity, provider version, event time, receive time, provenance, workspace, and a sanitized source reference.
Order
Payment
Attempt
Authorization
Capture
Refund
Dispute
Payout
Settlement
{
"merchant_reference": "order_...",
"amount": { "value": "128.40", "currency": "USD" },
"market": "ZA",
"payment_method": "card",
"policy_version": "route-policy-...",
"execution_mode": "shadow"
}Safety is part of the contract.
Exact-money arithmetic, idempotency, signature verification, tenant scope, immutable policy versions, approval, traffic limits, circuit breakers, and rollback are launch gates—not optional UI.
Bring the provider and lifecycle edge cases your stack must handle.
We will map the required evidence, connector capabilities, security boundary, and execution controls before an integration is activated.