Skip to main content
Operate Pix Lerian as a stateful application with Midaz postings and asynchronous provider outcomes. In v1.0.0, exercise this model with the supplied mock provider only.

​
Observe the operation, not only the HTTP response

A create response can acknowledge accepted work before the mock provider reports a terminal outcome. Store the resource identifier, request correlation data, and idempotency value. Then read the resource until its state is terminal.
  • Use SPI transfer reads and refund reads for payment flows.
  • Use the DICT and COB resource reads returned by the generated reference for their respective flows.
  • Match the final plugin state to the expected Midaz debit, credit, hold, release, or reversal in your test evidence.
Do not infer settlement from a successful submit alone.

​
Preserve safe retry behavior

Keep X-Idempotency with the original request payload and response. Reuse it only to retry that request. The plugin rejects a divergent reuse, except on the two collection-create routes: they return the existing immediate or due-date collection. A dependency failure is not a signal to invent a terminal state. Restore the dependency, preserve the same retry identity when the contract allows it, and read the resource before sending a new business request.

​
Handle reconciliation and MED 2.0

DICT can temporarily gate selected key and claim mutations while VSync reconciles a scope. A 503 from that gate means reconciliation is active. Inspect its state and retry only after the scope is available. Cancellation remains distinct from mutations that can introduce drift. MED 2.0 holds and refunds have their own state transitions. Use the SPI guide and DICT guide to determine whether a hold should be settled, compensated, released, or reviewed. Do not turn operational overrides into ordinary client flows.

​
Respect the connectivity boundary

The plugin and Midaz are the components under test. The supplied mock provider simulates the provider outcome and invokes internal callbacks. A client must not invoke callback, override, or recovery routes directly. Native SPI messaging integration is not available for use in this release. These pages do not establish production connectivity or a provider selection model.

​
Test-operating checklist

  1. Verify the authenticated account scope before a write.
  2. Save the request, X-Idempotency value, and returned resource identifier.
  3. Wait for and observe the mocked asynchronous outcome through a public read.
  4. Verify the expected Midaz posting or compensating posting.
  5. For a non-terminal result, read state first. Only then follow the documented retry or recovery action.
See Integration for client boundaries and request conventions.