Scheduled Fill ExchangeOperational marketplace for cycle-based card fulfillment

Admin area

Admin cockpit

This cockpit is meant to stay calm under pressure: resolve disputes, watch cycle state, track webhook health, and keep operational notifications in view without context switching.

Pricing OpsPayout OpsWebhook OpsOpen Hub Console

Runtime mode

prisma

Actionable disputes

0

Webhook backlog

0

Notifications

0

Admin audits

0

Risk has one desk

Dispute resolution, webhook health, and operational notifications should read like one coherent control surface.

Runtime state stays human

Database posture, worker activity, cycle state, and sanctions need to feel legible under pressure, not merely present.

Backlog needs shape

When the cockpit gets busy, the first view should separate what is actionable now from what is just informative.

Audit without friction

Operators should move from summary to dispute/webhook detail without losing the surrounding operational story.

Risk and dispute pressure

Actionable disputes should be visible and resolvable without leaving the cockpit.

No open disputes are currently waiting for a resolution decision.

No actionable disputes are waiting for a decision.

  • Risk queue is clearNo open disputes currently require admin intervention.

Cycle and runtime summary

Cycle state, sanctions, and worker posture belong together.

Current cyclen/a
Cycle statusn/a
Database connectedYes
Worker statusBootstrap
Buyer sanctions0
Seller sanctions0

No disputes exist yet.

Webhook and outbox posture

Provider flow and platform notifications should be visible in one scan.

No webhook events have been recorded yet.

No notification events have been recorded yet.

  • No outbox events yetEvents will appear here as live flows execute.

Backlog posture

This is the quick operational scan before diving into a single dispute or webhook event.

  • 0 dispute(s) can be resolved nowActionable disputes should surface as explicit work, not as a vague risk signal hidden behind tables.
  • 0 webhook event(s) are in the latest backlog sliceProvider health and replay safety belong inside the same calm cockpit view as disputes and notifications.
  • 0 notification event(s) are visibleOperators should be able to verify that operational side-effects actually happened after dispute or parcel actions.

Admin audit trail

Replay requests and case follow-ups should accumulate as durable operator evidence, not just transient notices.

  • No admin audit entries yetReplay and follow-up actions will appear here.

No admin audit actions have been recorded yet.