Capture

This page explains the implementation of auto-capture.

1. The Charger_Payment_History table is filled during remoteStartCharging. This is to identify whether the charging session is via PayMongo or Wallet.
2. On charger status updates, the insertTransactionData handler is triggered.
3. There, we send a message to the CapturePaymentQueue if the following conditions are met:
   • The charger was stopped.
   • The capture type of the payment associated with the charging session is manual.
4. The handler associated with the CapturePaymentQueue will then attempt to capture the payment. If it fails, the message will be sent to the dead-letter queue.