Loading…
Open-Policy Exchange
~4 min to deploy
Zapier Refund-Within-Policy Gate
Lets the Zap issue refunds that sit inside policy and holds the rest — with the reason code attached to the record.
For: Support and ecommerce ops automating refunds in Zapier
SOC 2 CC8.1ISO 27001 A.8.34Refund evidence trail
What it enforces
In-policy auto-approval
Allows refunds under the threshold for customers in good standing.
Return-window check
Escalates a refund requested outside the published return window.
Chargeback block
Blocks a refund on an order with an active chargeback.
zapier-refund-within-policy.yaml
# Zapier Refund-Within-Policy Gate
# Fork: set the threshold and return window from your published policy.
apiVersion: decionis.dev/v1
kind: PolicyPack
metadata:
name: zapier-refund-within-policy
surface: zapier
workflow_key: refund_approval
standards: [SOC2-CC8.1, ISO27001-A.8.34]
defaults:
mode: shadow
emit_dossier: true
rules:
- name: in_policy_auto_approval
when: "action == 'refund.issue'"
decision: |
ALLOW IF refund_amount < 1000 AND customer.standing == 'good'
ESCALATE OTHERWISE
reason_code: refund_over_threshold
- name: return_window_check
when: "action == 'refund.issue'"
decision: |
ESCALATE IF order.days_since_delivery > 30
ALLOW OTHERWISE
reason_code: outside_return_window
- name: chargeback_block
when: "action == 'refund.issue'"
decision: |
BLOCK IF chargeback == true
ALLOW OTHERWISE
reason_code: refund_on_active_chargeback
Fork it, change the thresholds to match your environment, and deploy in shadow mode first — it defaults to listen-only so nothing in your live pipeline changes.
How to install it
Follow the install path for this surface, then paste the forked YAML as your policy config.
What to do next
This recipe is one step in a path. The same five steps apply to every recipe in the exchange.
- Simulate this recipe
Run the policy against a realistic action in the browser. Push it past what the rules allow and watch the verdict come back. No account.
- View the signed Decision Dossier
See exactly what was decided and why: the rule that fired, the evidence it read, the policy version in force, and an Ed25519 signature you can verify yourself.
- Deploy in shadow mode
Measure what the policy would have caught on your own traffic without touching the live path. Every recipe defaults to shadow, so the first deployment carries no execution risk.
- Connect a real workflow
Point the same policy at the system where the action actually originates — a checkout, an ERP posting, a Zap, an agent's tool call.
- Share the verified result
Publish the proof: a public verification link, an embeddable badge, a PR comment, or an anonymized shadow-mode finding. This is how the next person discovers Decionis.