Security by boundary

Keep public attribution, tenant authority and money control separate.

This page describes architectural controls visible in the AffiliateRails implementation. It does not claim a certification or audit that has not been completed.

01

Credential separation

Publishable keys are limited to public attribution operations. Secret keys belong in trusted server code. Human operator sessions and background workers use separate authorization paths.

Test and live credentials are environment-bound so sandbox activity cannot silently become production activity.

02

Tenant and identity isolation

Authorization resolves the tenant, application environment, role and resource ownership on the server. Browser-supplied identifiers do not grant authority by themselves.

Affiliate portal sessions remain self-scoped and re-resolve current affiliate state for protected operations.

03

Money controls

Idempotency, version checks and operation controllers fence concurrent money work. Journals record balanced movements, and reversals preserve the decision they negate.

Sensitive payout and configuration actions require explicit roles and, where configured, recent step-up authentication.