Skip to main content
For a shareable summary of the connection model, controls, and partner setup, download the Already partner integration and security overview (PDF, November 2026). Already’s development integration uses different credentials for different trust boundaries: Admin access is separate from partner membership. The API verifies protected requests in deployed environments and does not accept development identity headers there. Sensitive operator actions are recorded with an actor, timestamp, subject, and reason or reference. Demo reset and development simulations are unavailable in production mode.

Integrator responsibilities

Keep API keys and webhook signing secrets server-side. Verify webhook signatures before processing, deduplicate event IDs, and use an Idempotency-Key when submitting obligations. Limit who can read credentials and rotate them when access changes. Use HTTPS for hosted callbacks and send test events after configuration changes.

Development status

The platform is still in pilot development. Do not treat these controls as a certification or as approval for live investor funds. Bank numbers are currently stored in the API database without application-level encryption; provider tokenization or encryption, production operations, and independent review remain launch work. See data handling.