Skip to main content

❓ Open Questions

The list of questions COOCO needs RideNDine to answer before the integration design can be finalized. Each question is numbered for easy reference in meetings.

caution

All 8 questions are PENDING — awaiting responses from RideNDine.

📋 Question List​

#TopicQuestionStatusRideNDine Response
1EndpointsDo the paths in Expected API match RideNDine's API?⏳ PENDING(to be filled)
2PaymentDoes RideNDine return client_secret (Stripe Elements) or checkout_url (redirect)?⏳ PENDING(to be filled)
3QuoteWhat is the quote expiration TTL?⏳ PENDING(to be filled)
4IdempotencyWhich endpoints require the Idempotency-Key header?⏳ PENDING(to be filled)
5WebhooksIs webhook URL registration done via dashboard, API or email?⏳ PENDING(to be filled)
6MerchantIs re-sync required when store address or bank info changes?⏳ PENDING(to be filled)
7ComplianceBeyond the /merchants/sync payload, is any additional compliance data required?⏳ PENDING(to be filled)
8ContactWho is RideNDine's technical point of contact for integration support?⏳ PENDING(to be filled)

📝 Question Details​

Q1 — Confirm API Endpoints​

Do the paths in Expected API match RideNDine's API?

COOCO has proposed paths such as /merchants/sync, /checkout/quote, /orders/create... If the paths differ, RideNDine needs to provide the correct endpoints.

Impact: If paths are wrong → the entire Directus Extension needs to be updated before Phase 1.

Q2 — Payment Model​

client_secret (Stripe Elements embedded directly) or checkout_url (redirect to RideNDine's page)?

  • client_secret: COOCO embeds Stripe UI Elements into cookin-web — smoother UX.
  • checkout_url: COOCO redirects to RideNDine's hosted page — simpler to implement.

Impact: This decision directly affects the frontend implementation of Phase 4.

Q3 — Quote TTL​

How long does a quote from /checkout/quote remain valid?

COOCO needs to know in order to:

  • Display a countdown timer to the customer
  • Automatically invalidate and request a re-quote if expired
  • Handle QUOTE_EXPIRED errors correctly

Q4 — Idempotency-Key​

Which endpoints require the Idempotency-Key header to be sent?

COOCO has prepared:

  • merchant_sync_{store_id} for /merchants/sync
  • cooco_order_{orders.id} for /orders/create

Needs confirmation on whether /payment/process and other endpoints also require it.

Q5 — Webhook Registration​

What is the process for registering webhook URLs?

Options:

  • Self-register via the RideNDine dashboard
  • Call a dedicated API endpoint
  • Send the list by email for the RideNDine team to register manually

COOCO needs to know in order to prepare according to the correct process.

Q6 — Merchant Re-sync​

When a chef updates the store address or bank information, does COOCO need to call POST /merchants/sync again?

If yes: COOCO will create a Directus Flow trigger when stores.bank_info or store_details.deliveryRegion changes.

Q7 — Compliance Requirements​

Beyond the default /merchants/sync payload, does RideNDine require any additional compliance documents?

e.g. national ID scan, business license, food handler certificate...

Q8 — Technical Contact​

Who is RideNDine's technical point of contact for integration support?

COOCO needs:

  • Name + email
  • Communication channel (Slack / Telegram / email)
  • Working hours / timezone