QUMI Docs
API

Payments & Billing API

Representative contracts:

GET   /api/v1/payments
POST  /api/v1/payments
PATCH /api/v1/payments/:id/status
GET   /api/v1/payments/payable-summary
GET   /api/v1/billing/summary
GET   /api/v1/billing/plan-limits
GET   /api/v1/billing/check-feature/:feature
POST  /api/v1/billing/upgrade-request
GET/POST/DELETE /api/v1/billing/payment-config
GET   /api/v1/public/payments/booking/:bookingId

Payment creation supports idempotency keys. Partner access should initially expose status/reference data rather than provider secrets or platform subscription administration.