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

# SlipPay

Stellar-native commerce stack for Brazilian merchants billing globally. Pix in, USDC out (PYUSD coming), no chargebacks.

> **Status**: **live on Stellar mainnet** since 2026-05-16. Subscription contract `CBJMQ6ZYQJ2OMM46FGXPEIKKZDRHHERBXUVE54ZN64FDPKN5DJKSEVQN` on [stellar.expert/explorer/public](https://stellar.expert/explorer/public/contract/CBJMQ6ZYQJ2OMM46FGXPEIKKZDRHHERBXUVE54ZN64FDPKN5DJKSEVQN). API at [api.slippay.cc](https://api.slippay.cc/api/health).

> **Ask Slippay** — the support agent on the bottom-right of every page is **Concierge**, governed by the [**Bluewave Soul Specification Language v7**](https://galmanus.github.io/ssl-spec/). The full open spec is at `galmanus.github.io/ssl-spec`. See [concierge-ssl](/slippay-docs/integrations/concierge-ssl.md) for how the soul file constrains the agent — doc-grounded answers, inline citations, "I don't have that information" honesty, full audit chain on every reply.

## Get started

|                                                                     |                                                   |
| ------------------------------------------------------------------- | ------------------------------------------------- |
| [**Quickstart**](/slippay-docs/quickstart.md)                       | Create your first order in five minutes.          |
| [**Architecture**](/slippay-docs/concepts/architecture.md)          | The three-tier picture: api, listener, contracts. |
| [**Authentication**](/slippay-docs/api-reference/authentication.md) | API keys, JWT sessions, webhook HMAC.             |

## API reference

| resource                                                      | description                                       |
| ------------------------------------------------------------- | ------------------------------------------------- |
| [Merchants](/slippay-docs/api-reference/merchants.md)         | Sign up, manage settings, rotate API key.         |
| [Orders](/slippay-docs/api-reference/orders.md)               | One-shot payments. Buyer pays, you get a webhook. |
| [Subscriptions](/slippay-docs/api-reference/subscriptions.md) | Recurring billing. Idempotent on time.            |
| [Webhooks](/slippay-docs/api-reference/webhooks.md)           | Event types, retry semantics, HMAC verification.  |
| [Errors](/slippay-docs/api-reference/errors.md)               | Status codes and error shapes.                    |

## Guides

|                                                                    |                                                   |
| ------------------------------------------------------------------ | ------------------------------------------------- |
| [BR-export merchants](/slippay-docs/guides/br-export-merchants.md) | Stop the 6% leak: invoice in USD, settle in USDC. |
| [Drop-in checkout SDK](/slippay-docs/guides/drop-in-sdk.md)        | Two lines of JavaScript on your site.             |
| [Recurring billing](/slippay-docs/guides/recurring-billing.md)     | Subscriptions end-to-end.                         |
| [WooCommerce plugin](/slippay-docs/guides/woocommerce.md)          | Install + configure on any WC store.              |
| [Handle webhooks](/slippay-docs/guides/webhooks-handler.md)        | Verify HMAC, idempotency, retry windows.          |

## Concepts

|                                                                                |                                                          |
| ------------------------------------------------------------------------------ | -------------------------------------------------------- |
| [Architecture](/slippay-docs/concepts/architecture.md)                         | How the three runtime processes fit.                     |
| [Non-custodial settlement](/slippay-docs/concepts/non-custodial-settlement.md) | What "non-custodial" actually means here.                |
| [Regulatory framing](/slippay-docs/concepts/regulatory.md)                     | BCB Res 519/520/521 and the partnership-with-VASP model. |

## Integrations

|                                                                     |                                                                                                                                                           |
| ------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [x402 protocol](/slippay-docs/integrations/x402.md)                 | Pay-per-call resources gated by Stellar USDC. Shipped 2026-05-16.                                                                                         |
| [Ask Slippay · SSL v7](/slippay-docs/integrations/concierge-ssl.md) | The Concierge agent is built on the open [Bluewave Soul Specification Language v7](https://galmanus.github.io/ssl-spec/). Doc-grounded, cited, auditable. |

## Where to next

* See live: [api.slippay.cc/preview](https://api.slippay.cc/preview) — buyer-flow simulation
* SDK demo: [api.slippay.cc/demo](https://api.slippay.cc/demo) — drop-in checkout in action
* Sign up: [api.slippay.cc/signup](https://api.slippay.cc/signup) — get a testnet API key
* Issues / questions: [github.com/Galmanus/slippay/issues](https://github.com/Galmanus/slippay/issues)

## Stay close to the runtime

Every claim in this documentation should be verifiable against the code. If you find a doc that says something the code doesn't do, file an issue — that's a bug, not an aspiration. The honest disclosures section in the top-level README is the canonical place for known gaps between marketing and runtime.


---

# 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://slippay.gitbook.io/slippay-docs/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.