Explainability
Clear explanations for automated decisions — without access to internal data.
Subscription renewal: Limit exceeded
This outcome often maps to limit exceeded in Finance Decline. Signals from Wire payout processing suggest policy, risk, or configuration checks are needed.
Why this happens
This reason typically appears when the system detects patterns associated with policy/risk triggers or inconsistent signals for this workflow. It’s often resolved by verifying identity, billing consistency, and device/network stability.
This reason often appears with medium confidence unless combined with an additional concrete signal (e.g., error code, mismatch, velocity).
How it appears:
"Subscription renewal: Limit exceeded" can appear as a top-ranked explanation with confidence and clear next steps.
Use this as a starting point, then rerun analysis after adding one more relevant signal.
Suggested next steps
- Verify identity and billing data are consistent across all submitted fields.
- Retry with a previously successful method and stable network/device context.
- Contact support with timestamp and reference data to request manual review.