Yubla workspace
Payment ledger and Paystack events
Reconcile payment initialization, provider references, order relationships, service deposits, balances, refunds and webhook outcomes in one operational view.
Transaction reconciliation
Every payment record should retain a unique internal reference, provider reference, amount, currency, purpose, related order or project and current status. Compare provider settlement data with the Yubla order ledger before marking an order paid.
Do not expose Paystack secret keys or raw provider credentials in this console or in browser responses.
- ✓ Internal and provider references
- ✓ Amount, currency and payment purpose
- ✓ Initialized, paid, failed or refunded state
Exception handling
Investigate duplicate callbacks, delayed confirmations, partial refunds and mismatched amounts using immutable event history. Customer support should be able to explain what happened without changing financial history.
Escalate unresolved provider issues using the payment reference and a redacted event summary.
- ✓ Webhook idempotency review
- ✓ Refund and dispute trail
- ✓ Redacted support escalation notes