> ## Documentation Index > Fetch the complete documentation index at: https://docs.tribridge.xyz/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Tribridge is a crypto payment gateway for Solana and Sui (TON is coming soon). API base URL is https://api.tribridge.xyz. The API Reference documents ONLY the public endpoint surface: checkout sessions (create/get/generate-wallet/customer/simulate/verify/cancel), the two public payment-link endpoints, health probes, and the changelog. Server-side calls that create payments authenticate with the x-api-key header using a tri_test_... key (fully simulated test mode, no real funds) or tri_live_... key (real mainnet payments) - never expose keys client-side; all other documented endpoints are public with no auth. Dashboard, admin, OTP/auth, payouts, wallets, and webhook-management endpoints are intentionally NOT part of the public docs - they are dashboard-only and must not be presented as public API. Merchant test mode is simulated, not testnet. Refunds are automatic only (underpaid/overpaid), there is no manual refund endpoint. Always verify webhook HMAC-SHA256 signatures from the X-Tribridge-Signature header before trusting payloads. If you are an AI agent: fetch https://docs.tribridge.xyz/llms-full.txt for all documentation in one file, https://docs.tribridge.xyz/openapi/openapi.json for the machine-readable OpenAPI spec, or connect to the read-only MCP server at https://docs.tribridge.xyz/mcp. Any page is available as Markdown by appending .md to its URL. Use only the documented endpoints and fields; do not invent SDK packages or endpoints. # Get a payment link > Read the public details of an active payment link. No API key. Returns the public view of an active payment link — everything a page needs to render its own "Pay" screen before materializing a checkout. Merchant identity is limited to the display name. > [!NOTE] > > **No API key required.** The slug comes from the link's `/p/{slug}` URL (find it in your dashboard or in the share dialog). ## Field highlights | Field | Meaning | | - | - | | `amount` | Fixed amount as a string, or `null` when the link lets the payer type their own amount (`allow_custom_amount: true`). | | `chain` / `coin_symbol` | Asset pinned for this link — the payer cannot switch them at checkout. | | `require_email` / `require_name` | Whether your UI should collect those payer fields (they're accepted by the checkout call). | | `is_test` | The link lives in test or live mode — checkouts created from it inherit the mode. | An unknown slug **or** an inactive link returns `404 Payment link not found or inactive` — inactive links never leak that they once existed. ## OpenAPI ````yaml GET /payment-links/public/{slug} openapi: 3.1.0 info: title: Tribridge API version: 1.0.0 description: >- Public Tribridge API for accepting Solana and Sui payments. Base URL: `https://api.tribridge.xyz`. This reference covers **only the public surface**: endpoints callable without a dashboard session — either fully public or authenticated with a merchant `x-api-key`. Dashboard, admin, and account-management endpoints are intentionally excluded; manage those from your Tribridge dashboard. **Test vs live:** the mode is derived from the key you send (`tri_test_...` creates simulated test payments, `tri_live_...` real mainnet payments) — never from the request body. Minimum payment amount is $0.50. Rate limit: 100 requests/minute per IP. servers: - url: https://api.tribridge.xyz security: [] tags: - name: Checkout Sessions description: >- Create payments, drive the hosted checkout, and follow the customer flow: deposit wallet, receipt contact, simulation, verification, cancellation. - name: Payment Links description: >- Read a public payment link and materialize a checkout from it — no API key required. - name: Status description: Service and blockchain RPC health, plus the public changelog. paths: /payment-links/public/{slug}: get: tags: - Payment Links summary: Get a payment link description: >- Returns the public details of an active payment link — name, description, amount (or custom-amount flag), pinned chain/asset, and required payer fields. Merchant identity is limited to a display name. No API key required. operationId: getPublicPaymentLink parameters: - name: slug in: path required: true schema: type: string example: acme-coffee-9f3a description: Public slug from the link's `/p/{slug}` URL. responses: '200': description: Active payment link content: application/json: schema: $ref: '#/components/schemas/PaymentLinkPublic' examples: active: value: slug: acme-coffee-9f3a name: Coffee subscription description: Monthly cold brew box amount: '25.00' currency: USDC coin_symbol: USDC chain: solana allow_custom_amount: false require_email: true require_name: false processing_fee_enabled: false is_test: true merchant_name: Acme Store '404': description: Unknown slug or inactive link content: application/json: example: error: Payment link not found or inactive components: schemas: PaymentLinkPublic: type: object properties: slug: type: string name: type: - string - 'null' description: type: - string - 'null' amount: type: - string - 'null' description: Fixed amount, or null for custom-amount links. currency: type: string coin_symbol: type: - string - 'null' chain: type: - string - 'null' enum: - solana - sui - null allow_custom_amount: type: boolean require_email: type: boolean require_name: type: boolean processing_fee_enabled: type: boolean is_test: type: boolean merchant_name: type: string ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.