lynqx
Products

Payments, data, and the tools that keep them in sync.

Every product speaks one normalized, ISO 20022 compliant schema — and every payment reports its lifecycle back to you, event by event.

SAPORACLEKYRIBAHDFCDBSOCBClynqxPAIN.001 OUT · STATUS EVENTS BACK · ISO 20022
Single payments

One instruction, executed on local rails.

One instruction from your ERP, TMS, or API call — routed to the right bank and executed on the local rail (NEFT, RTGS, IMPS, FAST, GIRO). ISO 20022 pain.001 in, status events back at every step.

Bulk payments

Multiple payments, one file, one click.

Vendor runs, payroll, and disbursals as one batch — fanned out across banks and rails, with per-item status. A failed item never blocks the run; it reports back and can be retried alone.

Statements

Every statement, every bank — one schema.

MT940, ISO 20022 camt.053, and bank-proprietary formats land as one normalized, ISO 20022 compliant schema — intraday or end-of-day, pushed or pulled, ready for reconciliation.

Accounts & balances

Live account info across every bank.

Account details and live balances across every connected bank — normalized, currency-converted, and grouped by entity. Group cash the moment it moves, not at tomorrow's statement.

Virtual accounts

A dedicated account number for every counterparty.

Issue virtual accounts per client, entity, or use case on top of your physical bank accounts. Incoming funds identify themselves — collections reconcile on arrival, and client money stays segregated.

Tools & services · Data sync

Your ERP, TMS, and banks — never out of step.

Data sync keeps both sides current automatically: payment status written back to SAP, Oracle, or Kyriba the moment it changes, statements and balances pushed forward on schedule. No batch files, no manual exports.

Standards & notifications

ISO 20022 native. Notified at every step.

pain.001

Payment initiation — sent to any connected bank, any market.

pacs.002

Status report — accepted, executed, or rejected, back in real time.

camt.053

End-of-day and intraday statements, normalized on arrival.

Lifecycle webhooks

Initiated → accepted → executed → settled — delivered to your ERP, TMS, or endpoint.

Payments and statements are ISO 20022 compliant end to end — one schema regardless of bank.

PAIN.001 · PACS.002 · CAMT.053 · ISO 20022

Pick a product. Ship it in days.