Transactions

A transaction moves value on the platform — converting between fiat and stablecoin, or transferring stablecoin between wallets. Each one has:

• A type defining the direction of the conversion.
• Source and target currencies with amounts.
• A lifecycle status tracking progress.
• Payment details and receipts on completion.

Transactions require an approved customer and support every payment rail available for the currency pair. See Coverage for the full matrix.

​

Transaction types

On-ramps run on demand or automatically: an autoconversion rule converts every fiat deposit that lands in an account to stablecoin, with no per-transaction call.

​

Transaction lifecycle

Each transaction type has its own status progression:

​

Transaction purpose

Every on-ramp and off-ramp carries a purpose field — the end-use category of the funds. Banking partners and correspondent banks on the rail use it for AML screening, cross-border reporting, and how the receiving institution classifies the deposit. Pick the value that matches what the funds are actually being used for; mismatches can hold up the transaction or trigger an RFI.

​

Payment expiration

On-ramp transactions have a payment window. If the customer doesn’t complete the fiat payment in time, the transaction expires.

​

Late deposits

If a fiat deposit lands after the transaction has expired, Lumx doesn’t process the on-ramp. The funds are refunded to the original sender on the same rail used for the deposit. Start a new on-ramp if the customer still wants to convert.

​

Related resources