public
GET /v1/public/payment-config
The publishable key and enabled gateways, for a browser.
身份验证
此端点是公开的。它不需要任何凭据或组织——这是我们自己的营销网站和 AI 问答引擎所读取的内容。
此端点不需要组织 ID。您的密钥已用于识别其所属的组织，且响应范围也仅限于该组织。
免费试用
将尖括号中的内容替换为您自己的值，并将键占位符替换为您仪表板中的一个键。
curl -X GET https://api.zinndigital.com/v1/public/payment-config已登录？您仪表板中的 API 控制台会自动填入您真实的组织 ID 和您自己的密钥，并针对实时 API 运行请求，以便您查看实际的响应。 在 API 控制台中打开此端点
详细信息
Unauthenticated: the guest checkout funnel has no principal, and everything here is public by construction — a Stripe **publishable** key is designed to be embedded in a page, and "which gateways are switched on" is visible at checkout anyway. This exists so the key is **rotatable from admin**. The dashboard used to read it from `VITE_STRIPE_PUBLISHABLE_KEY`, a build-time constant that was set in no build — so every deployed dashboard shipped an empty key and could only tell customers card payments were unavailable. A build-time value also could not be changed by editing a row, which is what the owner asked for.
响应
| 名称 | 类型 | 必填 | 内容简介 |
|---|---|---|---|
providers | PaymentConfigProvider[] | 是 | — |
stripe_publishable_key | string | 是 | Empty when Stripe is not configured. Served here rather than baked into the SPA bundle so the merchant account can be rotated from admin (§2.35). |
card_capture_available | boolean | 是 | Whether the dashboard can show a card form. Computed here so "can this customer add a card?" has one answer rather than one per client. |
paypal_client_id | string | 是 | PayPal's client id, which goes in the JS SDK's script URL — the browser cannot render Buttons or hosted card fields without it. Public by construction (the catalogue marks it `s… |
paypal_available | boolean | 是 | Whether PayPal can actually be offered. Its own flag rather than something the SPA infers from `providers`: a PayPal row can be enabled with the client id blank, and a client re… |