commerce
GET /v1/orders/{orderId}/payment-options
The payment gateways this order may be settled on.
身份验证
请将 API 密钥作为 bearer 令牌发送。此端点在规范中未指明具体的权限，因此请为您的密钥赋予所需的最小权限，并通过检查响应来确认，而不是盲目假设。
此端点不需要组织 ID。您的密钥已用于识别其所属的组织，且响应范围也仅限于该组织。
免费试用
将尖括号中的内容替换为您自己的值，并将键占位符替换为您仪表板中的一个键。
curl -X GET https://api.zinndigital.com/v1/orders/{orderId}/payment-options \
-H "Authorization: Bearer zdk_live_…"已登录？您仪表板中的 API 控制台会自动填入您真实的组织 ID 和您自己的密钥，并针对实时 API 运行请求，以便您查看实际的响应。 在 API 控制台中打开此端点
详细信息
What the pay screen offers the customer, so an overdue bill can be settled through whichever enabled gateway they pick rather than only the one the subscription was created with. The answer is **per order, not per platform**. A reseller's client always receives exactly one entry — their reseller's connected gateway — whatever the platform has enabled, because that is the only merchant account their money may land in. `payOrder` refuses any `gateway` that is not in this list. Answers for a settled order too, with the same list: the question "what could pay this?" is meaningful for a receipt, and refusing would make the screen depend on a race with the webhook that settled it.
参数
| 名称 | 类型 | 必填 | 内容简介 |
|---|---|---|---|
orderId (path) | Uuid | 是 | The order's id. |
响应
| 名称 | 类型 | 必填 | 内容简介 |
|---|---|---|---|
gateways | string[] | 是 | Provider codes (`stripe`, `paypal`, `nowpayments`). Never empty — `stripe` is always present, because an unreadable provider registry must not be reported as "nothing is enabled". |
此端点可能返回的错误
401 · 403 · 404 · 429