> For the complete documentation index, see [llms.txt](https://bify.gitbook.io/bify-commerce-sdk/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/bify-commerce-sdk/getting-started/readme.md).

# Introduction

BIFY Commerce is the stablecoin checkout and verifiable purchase layer for partner-owned storefronts. Partners keep full ownership of their catalogue, prices, inventory, customer relationship, fulfilment, and commercial policies. BIFY provides the payment authorization, on-chain settlement, purchase record, product certificate, reward, access, voting, and webhook surfaces around each order.

This documentation covers Commerce only — the SDK, browser widget, API, Developer Portal, and Commerce contracts. It is a separate space from the RWA documentation.

## What you can build

| Capability          | What BIFY provides                                                              |
| ------------------- | ------------------------------------------------------------------------------- |
| **Checkout**        | Wallet-authorized USDC payment through the Commerce router                      |
| **Settlement**      | Canonical USDC transfer, purchase recording, and replay protection              |
| **Certificates**    | Non-transferable product certificates with Commerce-owned metadata and image    |
| **Rewards**         | Eligibility, holding periods, claim windows, and signed claim vouchers          |
| **Access & voting** | Optional access passes and one-vote-per-wallet polls                            |
| **Integration**     | `@bify/sdk`, `@bify/commerce-widget`, signed webhooks, and the Developer Portal |

## Start here

| Goal                  | Read                                                                                                                                        |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
| Understand the model  | [Commerce overview](/bify-commerce-sdk/getting-started/commerce.md) · [Architecture](/bify-commerce-sdk/core-concepts/architecture.md)      |
| Ship a checkout       | [Quickstart](/bify-commerce-sdk/getting-started/quickstart.md) · [End-to-end integration](/bify-commerce-sdk/getting-started/end-to-end.md) |
| Integrate payments    | [Hosted USDC payments](/bify-commerce-sdk/sdk/payments.md)                                                                                  |
| Look up a method      | [SDK reference](/bify-commerce-sdk/sdk/reference.md)                                                                                        |
| Call the API directly | [API overview](/bify-commerce-sdk/api-reference/api.md) · [Authentication](/bify-commerce-sdk/api-reference/authentication.md)              |
| Receive events        | [Webhooks](/bify-commerce-sdk/api-reference/webhooks.md)                                                                                    |
| Get credentials       | [Developer Portal](/bify-commerce-sdk/operations/portal.md) → [developer.bify.io](https://developer.bify.io)                                |

## How a purchase works

1. The partner backend creates a checkout session from its trusted order.
2. The buyer connects a wallet in the browser widget.
3. BIFY signs a payment authorization bound to that wallet and order.
4. The buyer approves USDC and calls `payHostedOrder` through the widget.
5. The router pulls USDC and the checkout records one settled purchase.
6. The partner fulfils after the signed `purchase.settled` webhook.
7. The buyer mints a non-transferable product certificate from the same wallet.

Certificates use Commerce-owned JSON metadata and a Commerce-owned image endpoint. They do not resolve through an RWA application or certificate URL.

## Conventions

|              |                                                                    |
| ------------ | ------------------------------------------------------------------ |
| Base URL     | `https://api.bify.io`                                              |
| Environments | Sandbox (Base Sepolia) · Production (Base mainnet)                 |
| Payment      | USDC (6 decimals), amounts as integer strings in base units        |
| Auth         | Bearer API key on server routes; short-lived tokens in the browser |

BIFY Commerce has no BIFY catalogue, custody wallet, card processor, marketplace, yield product, or RWA certificate dependency.


---

# 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://bify.gitbook.io/bify-commerce-sdk/getting-started/readme.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.