Prepare or complete consumer umbrella payment collection in chat.
Use this only after the consumer umbrella follow-up reports payment_needed. Authenticate with Authorization: Bearer <intake_access_token> from the latest consumer-prefill follow-up response. First call this endpoint with payment_collection_requested: true to request a secure Stripe SetupIntent session; this native step comes before handing the shopper to payment_url. If your runtime can render the registered secure payment UI, display it and wait for completion; do not collect card details through conversational text. Then call this same endpoint again with setup_intent_id and payment_method_id so Coverage Cat can place the reusable payment method on file. If the secure UI is unavailable or setup fails in chat, use the returned payment_url browser fallback and preserve the specific fallback reason. When payment_needed appears, the current checkout price shown came directly from the insurer while Coverage Cat is down to final declarations verification before charging the card. Never describe successful payment-method setup as premium collected or active insurance.
Request
- Base URL: https://api.coveragecat.com
- URL: https://api.coveragecat.com/api/intake/{uid}/payment
- Auth: HTTP bearer
Path parameters
Coverage Cat intake uid returned by the consumer-prefill or intake creation step.
Headers
Optional explicit Coverage Cat API version selector. Omit the header to use the current stable version.
Optional idempotency key for consumer or operator write requests. Coverage Cat replays the cached successful response for the same subject, path, and key for 24 hours, and rejects a changed payload under the same key.
Request body
Response
Payment collection is ready or the payment method is now on file.
Changes
No recorded changes to this operation across all 1 revision of this API.