Skip to main content
Create refund_review before running these examples. Connect the SDK to your Engine with an API key and report as the contract’s processor role.
These examples record outcomes; they do not execute a real refund. To prevent an operation before it happens, obtain a permission grant and execute only after it succeeds.

Versions

Pass refund_review:2 to choose a specific version. Omitting the version selects the latest when the thread is created; publishing a later version does not rewrite an existing thread’s contract. Later requests use only the same thread key to resume; omit contract to load the stored binding and pinned version. Supplying a different contract or version is rejected. See the cross-language resume examples.

Interpret results

  • A normal recording acknowledgement is not a completed validation decision.
  • { waitFor: true } waits for that particular reported event’s validation.
  • A failed operation can satisfy its contract; operation outcome and rule compliance are separate facts.
  • A successfully validated terminal step completes the thread.
Subscribe to notifications or inspect validation results to investigate violations. Recording telemetry does not automatically stop the caller’s code.