Skip to content
In the news TRM Labs × Finray — audit-ready crypto transaction monitoring for banking
Finray

Payment operations for Swiss and cross-border rails.

Payment operations with validation, enrichment, and exception handling. Zahlex runs the rail-side path of payments that Corebanq orchestrates and XZiel has screened. SIX's public SIC service provider list names FinRay Technologies Limited as a banking software provider for SIC RTGS, SIC Instant Payments and SWIFT, see the list on six-group.com.

Works with Corebanq as the ledger; XZiel screens upstream.

Live on SIC

Audax Solutions AG

Finray connected Audax Solutions AG to SIX SIC: RTGS settlement, SIC IP instant payments and QR-bill payments.

Audax Solutions AG passed SIX's acceptance test for SIC Instant Payments in September 2026 and has been a SIC RTGS and SIC IP participant since 2 November 2026.

  • SIC RTGS
  • SIC IP (instant payments)
  • QR-bill payments

One console for SIC operations.

The Home screen lists what needs a decision, shows connection health for RTGS and SIC IP (instant), the clearing-day calendar status, and payments in flight and settled today. The menu names the SIC tools: bank directory, IP participant register, IP debit stop, returns not delivered, and backup via the miniSIC carrier.

Menu groups in the console.

  • Operations: Home, Analytics, Payments, Inbound recalls, Unbookable credits, Reconciliation breaks, Messages waiting, Unmatched messages.
  • SIX Interbank Clearing: Connection, Clearing calendar, Settlement accounts, Clearing day summary, Own bank payments, Bank directory, IP participant register, IP debit stop, Returns not delivered, Backup / miniSIC carrier.
  • Developers: API keys, Webhooks.

Dashboard areas on the Home screen, with illustrative values.

  • Needs a decision: Inbound recalls 3, oldest 2 h ago; Unbookable credits 1, oldest 5 h ago; Not settled at day end 2, oldest created 1 d 3 h ago; Reconciliation breaks 1, oldest 1 d 6 h ago.
  • Connections and health: healthy overall; RTGS and Instant connected; database, broker and cache healthy.
  • Clearing day: RTGS closed today, opens 14.09.2026 00:00; Instant open.
  • In flight now: none for RTGS and Instant.
  • Today: sent settled, sent rejected, sent cancelled, settlement rate and received settled, per rail.
The Zahlex operations console: decisions waiting, SIC connection health, clearing-day status and today's totals. Illustrative data.

From Corebanq to SIC and back to the ledger.

Corebanq originates the payment and holds the funds in the ledger. XZiel screens it upstream. Zahlex validates it, applies its controls and submits it to SIC. The status that comes back settles or voids the ledger hold, and statements are reconciled against the ledger.

  1. Corebanq

    Orchestration · ledger hold

    screening request

  2. XZiel

    Screening · upstream

    screened payment + verdict reference

  3. Zahlex

    Validate · four-eyes and limits · submit

    pacs.008

    pacs.002 (back to Zahlex)

  4. SIX SIC

    SIC RTGS · SIC IP

    status → settle or void

  5. Ledger settle or void

    Posted once on settlement, voided otherwise

    reconciliation

  6. Reconciliation

    camt.054 (RTGS only) / camt.052 matched against the ledger

  1. pacs.008

    Out

    The customer credit transfer. It is the instruction Zahlex submits to SIC.

  2. pacs.002

    Status back

    The status report that answers a submission: settled, rejected, or still pending.

  3. pacs.004

    Return

    A payment return. It sends funds back after a payment has settled.

  4. camt.056 → camt.029

    Recall

    A return request, answered by a rejection (camt.029) or by a pacs.004 return.

  5. camt.054 (RTGS only) / camt.052

    Reconciliation

    Settlement confirmations (camt.054, RTGS only) and recapitulations (camt.052) that Zahlex matches against its own ledger entries.

Two SIC services and the QR-bill standard.

Clearing day

SIC RTGS

Swiss franc real-time gross settlement. Each payment settles individually, irrevocably and with finality in central bank money, once cover is available. Retail payments are handed to RTGS when the sending bank chooses to deliver them.

pacs.008 out · pacs.002 status · camt.054 (RTGS only) / camt.052 reconciliation

24 / 7 / 365

SIC IP

Instant payments in the same system. The amount is reserved, the recipient bank answers, then the payment settles. In principle this takes ten seconds or less; a payment that exceeds the time limit is cancelled.

pacs.008 out · pacs.002 status · camt.052 recapitulations

Standard

QR-bill

The Swiss invoice standard. A QR-IBAN (institution identifier 30000 to 31999) goes with a 27-digit QR reference, which Zahlex validates before submit. The payment itself settles over SIC.

QR-IBAN + QR reference validated · pacs.008 over SIC

SIC RTGS and SIC IP

One payment status model across both services.

SIC is the Swiss franc real-time gross settlement system. The Swiss National Bank commissions and oversees it, and SIX Interbank Clearing Ltd operates it. Payments settle in central bank money, individually and irrevocably, as soon as the debit is made to the settlement account.

Since November 2023 SIC has comprised two services. RTGS works in clearing days. The IP service settles instant payments around the clock: the amount is reserved, the recipient bank answers, and the payment settles. In principle this takes ten seconds or less, and a payment that exceeds the time limit is cancelled.

Zahlex tracks a payment through one status model, whichever service it uses. A payment is held only for a Zahlex control, such as a pending four-eyes approval or a limit breach, before it is submitted.

  1. received

  2. validated

    Before accepted, a Zahlex control can park the payment as held. It resolves to accepted when the control clears.

  3. accepted

  4. submitted

  5. pending

  6. settled

    After settlement, a pacs.004 return can make the payment returned.

Before settlement, a payment can also end as

  • rejected
  • cancelled
  • expired

SIC settlement is final, so the checks come first.

  1. Four-eyes approval

    A payment that needs a second approver is parked in the held state before submit. It resolves to accepted when the control clears.

  2. Limits and velocity

    Payment-level limits and velocity thresholds are checked before submit. A breach holds the payment instead of sending it.

  3. Retry-safe message IDs

    Message and transaction identifiers are derived deterministically from the payment, within the 35-character ISO 20022 limit. A retried submission produces the same message, so the duplicate check on the rail can recognise it.

  4. One reconciliation key

    The UETR and the end-to-end identifier are set when the payment is created and carried through every state. Statements are matched to ledger entries on them.

  5. Append-only ledger

    Ledger entries are append-only; a correction is a new, opposite entry, so the history reads as the audit trail.

Cross-border payments over SWIFT.

Zahlex connects to SWIFT through Alliance Cloud for cross-border payments.

Blink.

Finray is working on the launch of Blink, a pay-by-bank service for Switzerland — account-to-account payments initiated from the payer's bank, and a foundation for agentic payments.

Frequently asked questions.

  1. What is Zahlex?

    Zahlex is Finray's payment operations platform. It works with Corebanq as the ledger; XZiel screens upstream. It handles the rail-side path of a payment as structured steps: validation, enrichment, controls before submit, submission, status handling, exceptions and reconciliation.

  2. What is the difference between SIC RTGS and SIC IP?

    Both are services of the Swiss Interbank Clearing system and both settle in real time on a gross basis, in Swiss francs. SIC RTGS works in clearing days and also settles interbank payments; SIC IP settles retail instant payments around the clock, in principle within ten seconds. The Swiss National Bank commissions SIC and SIX Interbank Clearing Ltd operates it.

  3. Does Zahlex screen payments for sanctions or AML?

    No. Screening runs upstream: Corebanq sends the payment to XZiel before it reaches Zahlex. Zahlex records the upstream compliance decision reference in its audit trail and executes the rail. Zahlex's own controls are four-eyes approval and limit and velocity checks.

  4. What happens when a payment is rejected, returned or recalled?

    A rejection arrives as a pacs.002 status report and the payment moves to rejected. A return after settlement arrives as pacs.004. A recall is sent as camt.056 and answered with camt.029 or a pacs.004 return. A returned or recalled payment becomes a new reversal payment in the append-only ledger rather than an edit.

  5. Which message formats does Zahlex use?

    ISO 20022, in the Swiss interbank implementation: pacs.008, pacs.002, pacs.004, camt.056, camt.029, camt.054 (RTGS only) and camt.052. These are XML messages exchanged with SIC, not a REST interface.

  6. Is Finray a bank?

    No. Finray is a software company, not a bank, payment institution, or e-money institution. Zahlex operates within the licensed institution's regulatory perimeter, and the institution remains responsible for regulated activity.

Bring one payment flow.

We will map it to the rail, the controls and the reconciliation it needs.

Certificate of Registration NQA · UKAS Management Systems
ISO/IEC 27001:2022 Certificate of Registration issued by NQA to Finray Technologies Ltd, certificate number 215646, valid 21 October 2025 to 21 October 2028
Search
Type to search across Finray, products, company, and journal.

    Press Esc to close · ↵ to open the highlighted result.

    Book a briefing Step 1 of 3

    Your details

    Who is requesting the briefing.