Conclude the onboarding process by transitioning a fully verified customer to Active status. This milestone interaction transforms a pending registration into a qualified banking participant, unlocking the ability to open accounts, execute trades, and perform fund transfers.

Designed as a final safeguard, the activation endpoint ensures that all institutional prerequisites—including KYC verification—are satisfied before a customer becomes an approved member of your financial environment.

Onboarding Flow Context

This API is the final step in the customer onboarding journey:

1. Create Customer: POST /v1/clients (State: Pending)
2. Add Documents/Identifiers: Provide required identification records.
3. Verify Customer: POST /v1/clients/{clientId}?command=verify (State: transitions to Verified)
4. Activate Customer: POST /v1/clients/{clientId}?command=activate (State: transitions to Active)

Expected Outcomes & State Transitions

• Success (200 OK): The customer is successfully activated and their status transitions to Active. They can now open accounts and perform transactions.
• Validation Error (400 Bad Request): The activation date is missing or in an invalid format.
• Domain Violation (403 Forbidden): The customer is already active, has not been verified, or the user lacks the required ACTIVATE_CLIENT permission.

Integration Guidance

• Ensure the customer has been verified before calling this API. Unverified customers cannot be activated.
• The activationDate must be provided in the format specified by the dateFormat parameter.
• If you need to bypass the standard verification flow, use the isActivatedByManualReview flag with appropriate manualReviewActivationComments.