Nilos

• Name: Nilos

• Status: alias of nilos

• Why this note is not separate: Nilos is better kept as an entity note because the useful question is who controls customer admission, compliance workflow, partner composition, corridor exposure, and the API-and-support shell around cross-border collection, FX, and payout operations — not whether there is a standalone protocol surface independent of the named operator.

• Canonical note: nilos

• Last reviewed: 2026-08-12 UTC