Stage 1: Batch Commit
When entering refunds, Port first commits the selected Planning Center batch.- While commit is pending, the screen stays in a waiting state.
- After commit completes, refund handling begins.
Stage 2: Refund Processing Paths
Auto-Processable Refunds
If refunds are marked auto-processable, Port calls Planning Center refund endpoints and shows progress.Manual Refunds
If refunds cannot be auto-processed, Port provides a CSV download (refunds-<batch-id>.csv) for manual action in Planning Center.
How Refunds Are Detected
Detection is provider/parser driven. Common patterns:- Negative amounts
- Provider-specific status fields
Important Provider Behavior
- Subsplash requires the
statuscolumn and uses it for refund detection (failed,refunded,disputed). - Some providers mark refunds as manual-only.
Completing the Import
- If no manual refunds remain, the flow can complete automatically.
- If manual refunds exist, confirm you processed them before continuing.