Backend runtime

Backend ledger / partner runtime gate

Move from UI evidence to backend-controlled finance.

Records idempotent backend packets, checks partner readiness, and blocks payout execution unless licensed runtime is configured.

0

Ledger

0

Payouts

0

Blocked

Current status

Backend runtime not loaded yet.

1. Source posting packet

Use controlled posting evidence only.

2. Licensed partner readiness

Upaisa/SBP rail stays blocked until configured.

Upaisa / SBP licensed partner rail

Runtime config not loaded.

Runtime flag

off

Credentials

0/3

Provider API

blocked

Mode

loading

3. Maker-checker

Backend packet needs human names and note.

4. Backend queues

Server-side preview truth.

No backend finance runtime packets yet.

Runtime locks

Backend packet is still not public wallet truth.

Preview backend uses server JSON for demo truth; production must use PostgreSQL transactions, audit logs, and signed ledger batches.

Licensed partner payout remains blocked unless partner runtime flag and credential custody are configured and approved.

No provider API call, bank transfer, wallet mutation, public balance, refund, penalty, GRN, invoice, or inventory movement is executed from this page.

Masked callback evidence still needs signature verification, reconciliation, exception handling, and ledger posting approval.

Posting gatePayment opsUpaisa sandboxChain spine