GET /v1/orders/{orderId}/payment-options

Xaqiijinta aqoonsiga

U dir fure API ahaan calaamad muujisa (bearer token). Barta dhammaadka ee kani ma caysino luqad ahaan oggolaansho gaar ah oo ku dhex jirta qeexidda, markaa sii furahaaga inta ugu yar ee uu u baahan yahay oo fiiri jawaabta halka aad wax ka qaadan lahayd.

Boggan ma qaato aqoonsiga ururka. Furahaagu wuxuu horay u aqoonsanayaa ururka uu ka tirsan yahay, jawaabtuna waxay ku kooban tahay halkaas.

Isku day

Ku beddel wax kasta oo ku dhex jira qeebaha xaglaha ah qiimayaashaada, sidoo kalena haystaaha furaha ku beddel fure ka dhex muuqda dashboordigaaga.

curl -X GET https://api.zinndigital.com/v1/orders/{orderId}/payment-options \
  -H "Authorization: Bearer zdk_live_…"

Ma sign-garaysay? Qalabka API ee ku jira dashboard-kaagu wuxuu buuxiyaa aqoonsigaaga ururka ee dhabta ah iyo furahaaga gaarka ah, wuxuuna ku shaqeysiiyaa codsiga API-ga nool si aad u aragto jawaabta dhabta ah. Kani ka fur barta kontoroolka ee API

Details

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.

Cabiraha

Jawaab

Cilladaha ay bartaani soo celin karto

401 · 403 · 404 · 429