# Pre-production Setup

Similar credential exchanges are required for the pre-production environment setup. If lost, misplaced or compromised, the framework allows new credentials to be generated with a grouping schema. A security profile group consists of a collection of credentials. A group ID is assigned to each group and will be sent along with all calls to the APIs. Only two (2) group IDs can be active per time and the security admin can enable new security groups or disable an older group as required.

Once the simulated tests have been passed in sandbox, a "move to pre-production" link is activated to transition the AP into pre-production. It is expected that the AP has also migrated API and internal services into their production environment at this time. Similar callback URL and certification account details are required to commence the self-service certification program.

![Figure: Pre-production Progress Tracker](/files/NyUZpNyuo1MmpxXvVFjZ)

This program performs good-path, exception and performance tests of the production APIs that helps confirm the features have been migrated correctly and are working as expected in production. In addition, and most importantly, the performance tests would reveal if any APIs are functioning below capacity given the simulated load. These metrics would be red flagged for the AP to tune and rerun the certification. If all metrics pass, the certification program is deemed complete.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.openbanking.ng/standard/integration-and-certification/account-provider-certification/pre-production-setup.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
