Card-data minimisation
The target card architecture keeps raw card credentials within the approved provider-hosted environment rather than storing them in Nexus or connected casino applications.
SECURITY
Reduce payment-data exposure and keep financial actions auditable.
Nexus is designed around provider-hosted payment experiences, environment-held secrets, signed integrations, idempotent financial posting and restricted operational actions.
Environment-only secrets
Provider credentials and signing secrets are configured outside source control and can be separated by environment.
Signed provider events
Provider-specific webhook verification and allow-list controls can be enforced before external events affect financial state.
Exactly-once ledger posting
Retries and duplicate provider notifications must not create duplicate financial movements.
Operational separation
Reconciliation, manual review and settlement approval remain distinct operational states rather than direct balance mutations.