A payment provider can show a successful purchase while the application still denies access. It can also show cancellation while stale application records continue to grant paid work.
Reconciliation compares trusted billing facts with the application's entitlement policy. It should identify the affected resource and safe repair, not simply set every account with any payment to paid.
Define the mapping and expected state
Record which provider customer, purchase, or subscription maps to which internal user, organisation, or resource. Keep identifiers stable and scope them to the provider environment and account.
Write the rule that derives entitlement from those facts. Include effective dates, refunds, cancellations, pending states, manual grants, and the product's retention or read-access policy. Without that rule, a mismatch report cannot distinguish an error from an intentional exception.
Reconcile a fictional paid-study purchase
Suppose a founder buys access to one additional study. The provider record is complete, but a temporary application failure prevented the entitlement update. A reconciliation job locates the purchase, validates the mapping, and identifies one missing study grant.
Test the reverse mismatch: the application grants access, but the provider record does not support it. Determine whether the grant is a documented support exception, a sandbox record, a pending event, or an actual defect before removing access.
Add duplicate mappings, an unknown customer reference, a partial refund, and a deleted study. These cases should enter a defined review state rather than being repaired through a broad guess. Preserve the original discrepancy and resulting action for later explanation.
Make repair safe and accountable
Separate detection from mutation when the consequence deserves review. An automated repair may be appropriate for a clearly missing grant, while ambiguous ownership needs a person. Record actor, reason, previous state, new state, and provider evidence references.
The official Stripe subscription-event guide describes its event lifecycle, but reconciliation must follow your actual provider and product mapping. Event receipt alone is not proof that the application finished processing it.
The tradeoff is automatic consistency versus incorrect repair. Frequent reconciliation can reduce mismatch duration while increasing provider calls and operational work. A slower review process may fit a small pilot, provided customers have a visible support path and the risk is accepted.
The StackFlight product account describes paid study access. This mismatch exercise is fictional and does not claim a production incident or describe its internal reconciliation implementation.
Questions about entitlement reconciliation
Should every successful payment grant access to the whole account?
No. Apply the entitlement to the resource and scope that were purchased. Account-wide access is only correct when the product explicitly sells it.
Can manual grants be reconciled safely?
Yes, if they are explicit records with scope, reason, owner, and expiry where appropriate. Hidden exceptions are difficult to distinguish from defects.
What should be tested first?
Create one missing grant and one unsupported grant in a sandbox, then inspect detection and repair. Bring ambiguous mappings to a billing-data review.