> For the complete documentation index, see [llms.txt](https://docs.paystation.ng/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.paystation.ng/resources/security.md).

# Security

## Protect credentials

* Keep secret keys in a server-side secret manager or protected environment variable.
* Never commit `.env` files or keys to source control.
* Never expose secret keys in browser or mobile application code.
* Reset keys immediately when exposure is suspected.
* Use separate credentials for each environment.

## Transport security

Use HTTPS for every production request. Reject invalid TLS certificates and do not disable certificate verification.

## Customer information

Send only information required for the payment operation. Restrict access to customer identifiers, account numbers, KYC documents, and transaction records.

## Logging

Log request references and HTTP status codes, but redact:

* `Authorization` headers;
* secret and public keys;
* full account numbers;
* BVN and NIN values; and
* raw identity documents.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.paystation.ng/resources/security.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.