Shaype platform release, focusing on:`Account Opening Access Controls`

Account Opening for a Customer

In this release, we have delivered an update to Account Opening that may require clients to make a change to how they open customer accounts via the Shaype API. We are introducing new customer status validation for opening an account. Shaype will mandate that any clients who utilise our on-platform KYC capabilities can only open accounts where the customer's status is ACTIVE.

An example response has been added to the 422 section of our API swagger to demonstrate the type of response you will receive when this feature is activated in production.

{
  "message": "PERMISSION_DENIED: Account cannot be created for customer with id eed1e718-b1ca-4b94-a508-3d2d41c2e96b as their status is currently BLOCKED",
  "details": "Please refer to the API documentation or contact Shaype for more info with the traceId.",
  "status": "422",
  "traceId": "b24daeb7-4242-4ff1-ba50-9825d5deedd8"
}

Account Opening for a Group

To ensure parity for all account opening APIs, we have also introduced the same validation on group account opening. If all customers associated with the groupHayId provided in the request do not have a customer status of ACTIVE, then the request will be rejected.

We have provided the example response in the 422 section of the API swagger.

{
  "message": "PERMISSION_DENIED: Account cannot be created for group with id f64f41eb-41f4-4619-9fc4-68d292aeb0f9, all members of the group should have an ACTIVE status",
  "details": "Please refer to the API documentation or contact Shaype for more info with the traceId.",
  "status": "422",
  "traceId": "b24daeb7-4242-4ff1-ba50-9825d5deedd8"
}

📘
Feature Activation
We are not enforcing this feature for all clients in this release. Your CSM should be contacting you to discuss the timelines for you adopting this change and - once agreed - Shaype will update your production configuration to enforce this new protection on account opening.

Changelog