Changelog

Stay up to date with the latest updates and improvements to Lumx

​

November 23, 2025

v2.1.0

SEPA and SWIFT are live 🚀

New feature:

1. SEPA support now available

You can now create bank accounts and execute transactions using SEPA (Single Euro Payments Area) for EUR payments across Europe. SEPA provides instant settlement for transactions under $100k and 1 business day settlement for larger amounts.

{
  "rail": "SEPA",
  "sourceCurrency": "EUR",
  "sourceAmount": "10000.00",
  "targetCurrency": "USDC",
  "purpose": "PERSONAL_ACCOUNT"
}

2. SWIFT support now available

You can now create bank accounts and execute transactions using SWIFT for USD international wire transfers. SWIFT enables global payments with 1-5 business day settlement times.

{
  "rail": "SWIFT",
  "sourceCurrency": "USD",
  "sourceAmount": "10000.00",
  "targetCurrency": "USDC",
  "purpose": "PERSONAL_ACCOUNT"
}

For complete coverage details, see Coverage.

Enhancement:

3. Purpose field now returned in transaction responses

The purpose field is now included in transaction responses under the request object, providing full visibility of the original transaction intent.

4. Target amount visibility improved

Transaction responses now consistently return targetAmount in the receipt object when the conversion is complete, ensuring you always have access to the final conversion amounts.

5. Bank account ordering updated

Bank accounts are now ordered by creation date (newest first) instead of by ID, making it easier to find recently added accounts.

​

October 27, 2024

v2.0.0

Bank Accounts are live 🎉

New feature:

1. Supplier payments now available

You can now send off-ramp funds to bank accounts that don’t belong to the registered customer. This enables direct supplier payments.

The new /bank-accounts endpoint allows you to register and manage bank accounts for supplier payments. Refer to the Create a Bank Account for details.

Enhancement:

2. PROCESSING status renamed to TRANSFERRING_STABLECOIN

3. state.blockchain moved to state.receipt

The new receipt object includes transactionHash and blockExplorerUrl fields for better transaction tracking.

4. purpose now required for on-ramp and off-ramp transactions

For compliance reasons, all transaction requests must include a purpose field. Requests without this field will be rejected.

5. On-ramp: payment.rail moved to request level rail

6. Off-ramp: customerId and payment object removed, use bankAccountId only

7. Exchange Rate: rail and customerId parameters now required