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

# Product Overview

Secant Pay is a payment operating system for merchants who work across Base and Solana.

The product combines checkout, invoices, customer payment requests, point-of-sale payments, portfolio visibility, and swap routing into one self-custodial workflow. A merchant connects an EVM wallet and a Solana wallet, creates payment requests, shares a payment link or QR code, optionally sends the request to a customer's Dialect inbox, and tracks settlement — without giving Secant custody over funds.

## Core Jobs

### Accept Payments

Merchants request USDC on Base or Solana. Customers scan a QR code, open a payment link, receive a Dialect in-app request, or pay from a Solana Action / Blink. On Solana, customers can pay with SOL or any supported SPL token — Jupiter routes the swap so the merchant always receives USDC.

### Track Settlement

Secant tracks payment state through on-chain data, Solana reference keys, Helius webhook events, and Zerion activity feeds. The backend validates every settlement against the expected chain, recipient, asset, amount, and reference before marking an invoice as paid. See [Security and Settlement](/secant-docs/security-and-settlement.md) for the full validation model.

### Manage Invoices

Invoices become shareable payment links. On Solana, invoice links also expose Action endpoints so they unfurl as payable cards in clients that support Blinks. Merchants can add a customer Solana wallet to send a Dialect request automatically; the request points back to the same Secant pay link and invoice settlement record. Each invoice carries a 30-minute expiry, unique reference, and full settlement data for the target chain. Plans set a monthly invoice allowance (Starter includes 10 active invoices/month; Growth and Enterprise are unlimited), and unpaid invoices that expire refund their slot automatically.

### Swap and Bridge

Solana-to-Solana swaps route through Jupiter with price impact and minimum received shown before signing. EVM swaps and cross-chain bridge routes use Zerion-powered routing with slippage controls.

### Portfolio Visibility

Aggregated balance and asset views across all connected wallets. Network distribution, position metadata, and transaction history from portfolio providers — all in one dashboard without switching between block explorers.

## How It Works

```mermaid
flowchart LR
  A["Merchant creates\npayment request"] --> B["Customer scans QR\nor opens payment link"]
  A --> N["Optional Dialect request\nsent to customer wallet"]
  N --> B
  B --> C["Customer signs tx\nfrom their wallet"]
  C --> D["Funds settle directly\nto merchant wallet"]
  D --> E["Secant detects settlement\nvia webhook + chain data"]
  E --> F["Invoice marked SETTLED\nmerchant dashboard updates"]
```

At no point does Secant hold, escrow, or route funds through its own wallets. The customer's wallet sends directly to the merchant's wallet. Secant's role is coordination: building the payment request, encoding the transaction parameters, and verifying that the on-chain result matches what was expected.

## Current Audience

| Segment                  | Use Case                                                                         |
| ------------------------ | -------------------------------------------------------------------------------- |
| Freelancers and agencies | Generate payment links, send customer wallet requests, receive USDC settlement   |
| Global merchants         | Request stablecoin payments, track on-chain settlement, manage across networks   |
| Solana-native teams      | Blinks, Solana Pay, Jupiter checkout — accept diverse SPL tokens, settle in USDC |
| EVM users                | Portfolio visibility, Base USDC payments, swap and bridge routing                |

## Product Principles

**Self-custodial.** Wallets sign directly. Funds settle to merchant-owned addresses. Secant never holds keys or balances.

**Two-chain first.** Base and Solana are treated as first-class rails with native tooling, not abstracted behind a generic multi-chain wrapper.

**USDC-centered.** Checkout and settlement are optimized around stablecoin payments. Token flexibility at the customer layer, stablecoin certainty at the merchant layer.

**Composable.** Routing, balances, settlement detection, name resolution, Blinks, and wallet-native notification inboxes use ecosystem-standard providers (Jupiter, Zerion, Helius, SNS, Solana Pay, Dialect). Secant composes existing infrastructure rather than rebuilding it.

**Open.** The SDK, checkout components, and Action endpoints are designed for external developers to build on — not just for Secant's own frontend.


---

# 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://secant.gitbook.io/secant-docs/product-overview.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.