Skip to main content

Pay

Lexabit Pay — "Every payment verified, every transfer compliant."

Planned · Layer: Data

What it does​

Pay is compliant payment initiation with verification built in — including PSD2 account-ownership verification that requires a receiver to prove they own the destination account before funds move. Where most payment platforms optimize for speed, Pay optimizes for verified, compliant transfers — critical for law firms handling client funds and bankruptcy estates.

Key capabilities​

  • Multi-provider payment initiation — banking APIs, direct transfers, and third-party providers; single, bulk, and scheduled payments.
  • Receiver verification — before sending, the receiver proves their identity (BankID/MitID/eID) and/or that they own the destination account (PSD2).
  • Pre-payment compliance checks — sanctions screening on the receiver plus amount/country policy checks before execution.
  • Approval workflows — configurable chains (auto-approve small, sign-off for large, compliance review for high-risk).
  • Source-of-funds documentation — link payments to source-of-funds evidence.
  • Full payment audit trail — who initiated, who approved, which checks ran, and the result.

How it fits​

Pay draws on Account Connect for account data, Comply for screening, Monitor for policy checks, and Trace for source-of-funds context, plus the shared Identification capability.

In the API today​

Pay is Planned and not yet available via the API. This page describes the intended direction — see the Products overview for how to read roadmap status.