Technical Registry
Gateway Scenarios
This registry contains seeded examples of gateway outcomes. It is used to verify handler behavior across invoice creation, policy enforcement, and Fiber settlement paths.
| Method & Route | Scenario Title | Tenant | Outcome | Status | |
|---|---|---|---|---|---|
POST/api/v1/invoices | Invoice creation succeeds A tenant with `invoices:write` creates a Fiber invoice and receives a persisted tenant-owned record back from the gateway. | sandbox-merchant | INVOICE CREATED | 200 | Inspect |
POST/api/v1/payments | Allowed payment settles A payment request for an owned invoice passes policy checks, claims the invoice for processing, and settles through Fiber. | sandbox-merchant | SETTLED | 200 | Inspect |
POST/api/v1/payments | Policy blocks an unapproved payment The gateway refuses to execute a payment when the active policy rejects the recipient or spend amount. | sandbox-merchant | REJECTED | 403 | Inspect |
POST/api/v1/payments | Duplicate in-flight execution is blocked A second payment attempt against an invoice already in `PROCESSING` returns `409` instead of racing a duplicate execution. | sandbox-merchant | BLOCKED | 409 | Inspect |
POST/api/v1/payments | Settled retry returns idempotent success A retry against an already paid invoice returns success with `idempotent: true` instead of charging twice. | sandbox-merchant | IDEMPOTENT | 200 | Inspect |
GET/api/v1/payments/{paymentHash} | Status lookup recovers stale processing state A payment-status read reconciles a stale `PROCESSING` invoice against Fiber and updates the stored invoice when a final status is found. | sandbox-merchant | RECOVERED | 200 | Inspect |
Operator Note: These records are seeded for demonstration and do not reflect live network telemetry. All IDs and payment hashes are illustrative.