Payment operations
Search, save, export, schedule, and reconcile payment operations.
Updated July 29, 2026On this page
- At least one checkout, renewal, or other routed payment attempt
A payment operation is the durable record for one logical payment. It keeps the router and published policy version, every MID attempt, gateway outcome, cascade decision, and any required reconciliation together.
Find an operation
Open the operation ledger
Open Payments → Payment operations. Search by operation, order, customer, source, or another exact reference. Use More filters for status, MID, card BIN or last four, product, currency, Funnel, routing-policy version, payment method, and date range. The ledger shows the amount, router, attempt count, and whether review is required.
Save a working view
Apply the filters your team uses repeatedly, then choose Save view. Saved views retain the complete filter set and can be selected or removed from the ledger toolbar. They do not change live payment behavior.
Export or schedule delivery
Choose Exports to queue a CSV from the filters currently applied. Export generation runs in the background; refresh the drawer and download the file when it is complete. Files expire after 30 days. From the same drawer, schedule a daily, weekly, or monthly CSV, choose the local delivery hour, and add one or more comma-separated recipients.
Review the execution path
Open an operation to see its source, transaction type, router, pinned policy version, and completion state. Each immutable attempt identifies the matched rule, pool, MID, provider result, routing reason, and cascade directive.
Reconcile indeterminate outcomes
If a provider request has an unknown outcome, Recurrify stops automatic cascading and marks the operation for reconciliation. Confirm the result with the provider, then append the verified category, provider status, transaction ID, and evidence. Do not retry the logical payment until the original outcome is known.
Important states
| State | Operator meaning |
|---|---|
| Processing | An attempt is reserved, submitted, or awaiting a final provider result |
| Approved | One attempt completed the logical payment |
| Declined | A definitive failure ended the configured route |
| Action required | Customer authentication or another customer action is required |
| Reconciliation required | The provider outcome is indeterminate; manual evidence is required before another attempt |
An export or scheduled report evaluates its saved filters when the background job runs. A saved view is only a reusable filter definition; it does not freeze the current rows.