Skip to main content
Every on-ramp and off-ramp request takes a purpose code declaring why funds are moving. Lumx uses the purpose for AML monitoring, regulatory reporting, and to match the transaction against the correct destination holder relationship.

​
Accepted values

PERSONAL_ACCOUNT only works with SELF-relationship destinations. Using it with any other relationship returns a validation error.

​
Choosing the right code

Pick based on the economic substance of the transaction, not the rail or destination type. Two heuristics:
  • If the customer and destination holder are the same legal entity, use PERSONAL_ACCOUNT.
  • Otherwise, pick the code that best describes the underlying commercial activity. When more than one applies, go with the more specific one: TAX over BILLS, EXPENSES_REIMBURSEMENT over PROFESSIONAL_SERVICES.
Misclassifying purpose can trigger RFI or transaction holds during compliance review.

Transactions

Full transaction lifecycle and request schemas.

Destinations

Holder relationships that pair with each purpose code.

Treasury management

Worked example of purpose codes across an inter-company flow.

Request for Information

What happens when purpose doesn’t match the underlying activity.