Add payment reconciliation logic #41
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds the initial reconciliation wiring for the payments flow. It prepares the payment module to receive and persist provider responses, and introduces a consumer used to process async reconciliation jobs. The primary goal is to enable reliable reconciliation between our internal payment attempts and external provider outcomes (InterSwitch, VTPass).
What changed
PaymentModule
InterSwitchModuleandVTPassModuleso provider-specific integrations are available to the payment flow.PaymentConsumertoproviders— this consumer will process reconciliation jobs (e.g., poll provider status, handle callbacks, or process queue messages that reconcile attempts).PaymentRepository
updatePaymentAttemptnow accepts and storesresponsePayload(instead ofrequestPayload) so raw provider responses are persisted. This is required to: