billing

POST /v1/payment-methods

Begin adding a payment method (on-session).

Dhammaan billing bixiyayaasha

Xaqiijinta aqoonsiga

U dir furaha API ah calaamad dusha ah (bearer token). Furaha waa inuu wataa ruqadda billing.payment.manage; furaha aan wadan waxaa loo diidayaa 403, ee ma aha 404.

Meesha aqoonsiga ururkaagu galayo

Boggan waxaa uu qaataa org_id oo ah goob ku jirta JSON body.

Aqoonsiga ururkaagu wuxuu ku yaallaa shaashada furayaasha API ee dashboard-kaaga, oo ku xiga furaha laftiisa. Waa isku aqoonsi wicitaan kasta oo aad sameyso.

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 POST https://api.zinndigital.com/v1/payment-methods \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{  }'

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

Faahfaahin

Opens a gateway SetupIntent and returns its short-lived `client_secret` for the browser SDK to confirm, completing 3-D Secure there. **No payment method is created by this call** — a mandate is consent, and the row is written only when the gateway confirms it on its webhook (ADR 0011 §3). Requires `billing.payment.manage` in the target organization.

Codsiga jidhkiisa

MagacaNoocLoo baahan yahayMaxay tahay
org_idstringMayaOrganization to attach the mandate to. The caller must hold `billing.payment.manage` in **that** organization.

Jawaab

MagacaNoocLoo baahan yahayMaxay tahay
setup_intent_idstringHaa
client_secretstringHaa

Cilladaha ay bartaani soo celin karto

401 · 403 · 422 · 429