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

# Commerce Security

## Credential boundaries

The BIFY SDK server package and webhook secret run on the partner backend. The browser component receives only a short-lived session or claim credential.

The following values remain server-side:

* BIFY API keys;
* webhook signing secrets;
* signing and encryption keys;
* database credentials;
* decrypted customer data.

## Payment integrity

BIFY verifies the canonical USDC contract, Base network, payment recipient, exact amount, payment reference, successful transaction status, confirmation depth, and replay state before settlement.

## Data protection

Customer contact and delivery details are encrypted at rest by the backend. Personal data is excluded from on-chain metadata, order-scope hashes, event payloads, and public certificate responses.

## Partner controls

Partners should use stable idempotency keys, reconcile settlement events with their own order records, and fulfil only after server-side settlement confirmation.


---

# 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 dynamically by asking a question.

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

```
GET https://bify.gitbook.io/rwa-docs/bify-commerce/security.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.