Refund approval example
A synthetic refund shows how Relay reviews a money-moving action before it happens
Review outcome
- Amount
- $420
- Decision
- Owner review
- Next step
- Owner review
- Blocked
- Refund and message
Review flow
The proposed refund becomes a review decision before anything changes
- 01
Refund proposed
Agent proposes a refund for order CO-1007and a customer notification
- 02
Policy checked
Relay checks the refund againstthe merchant approval threshold
- 03
Owner review required
Relay pauses this refunduntil owner review is complete
- 04
Execution blocked
No payment is sentand no customer message leaves the system
Review checkpoint
Relay pauses this refund until the owner reviews it.
Blocked until owner approval
Payment stays blocked
Message stays blocked
Decision record
The decision stays inspectable without exposing private data
- Scenario
- Over-threshold refund
- Proposed action
- Refund order
- Target
- Order CO-1007
- Amount at risk
- $420
- Decision
- Owner review
- Runtime instruction
- Pause for owner review
- Allowed next step
- Prepare owner review
- Blocked actions
- Refund payment; customer confirmation
- Record
- Review record 001
- Trace
- Refund review trace
Run locally
Test the refund review with synthetic data
git clone https://github.com/neurarelay/relay-action-card.git
cd relay-action-card
npm ci
npm run verify:commerceops-fire-drillWhat this example shows
Neura Relay reviews the proposed refund, returns a clear decision, and keeps execution inside the runtime
It does not claim production integration, provider approval, certification, real merchant adoption, or downstream execution by Neura
What Relay controls
Relay reviews the refund and returns the decision. Execution stays with the runtime.
- Synthetic data only
- No real Shopify store touched
- No real payment touched
- No customer message sent
- No provider approval or certification claimed
- Relay does not execute downstream actions