Overview
Use refund policies, refund requests, approval records, refund records, payment references, and canonical refund events.
Problem
Refunds need consistent policy, reason, approval, and transaction history.
Solution
Keep refund initiation, approval, execution state, and audit evidence inside PayStream.
How it works
Create a refund request against the relevant payment, evaluate the configured refund policy, record approval workflow where required, create the refund record, and publish the resulting finance event.
Who is this for
Finance Operations
Payments Approver
Expected outcomes
- Consistent refund approval trail
- Refund records connected to original payment state
Key metrics
Security impact
- Refund policies, refund requests, approvals, refunds, payment references, reasons, amounts, and audit/event state · PII: yes where billing, customer, payment, bank, invoice, or external reference data identifies a person or organization
Compliance
- Workspace permissions, trusted execution, resource authorization, Core secrets, finance audit, and app-scoped grants.
Availability & next steps
Team
Business
Enterprise