Security & transparency
GLIX Sweep is built around one rule: the interface must never imply that money moved when it did not. Here is how that promise is enforced under the hood.
We never see your full card number or CVV
Card entry happens through provider-hosted, tokenized fields in live mode. GLIX Sweep servers only ever receive an opaque provider token, masked card details, and expiry metadata.
Funds are never marked available before they're confirmed
GLIX Sweep uses a double-entry ledger with immutable, append-only entries. A balance only becomes spendable after the corresponding provider funding is confirmed — never before.
Every action is idempotent
Sweeps, card issuance, and webhook processing all use idempotency keys and database-level deduplication, so retries, duplicate submissions, or duplicate webhook deliveries can never move money twice.
Partial failures are handled safely
If one of several cards fails to authorize, GLIX Sweep never silently proceeds. You review the partial result and explicitly choose to continue with the confirmed subset or reverse everything.
Real money stays off until every safeguard is in place
Live payment processing is controlled by server-only feature flags that fail closed: if a required secret, provider, or approval is missing, GLIX Sweep refuses to start in a half-live state.
Access is invitation-controlled during the pilot
New accounts require a server-validated, single-use or limited-use access code. Identity verification runs before any funding can be swept.