This project is not covered by Drupal’s security advisory policy.
This modules provides a Transaction entity for tracking transactions related to a payment. A payment can have multiple transaction records in the remote payment gateway system i.e. the initial charge transaction and one or more refund transactions.
This module does not provide any functionality by itself. It requires a payment gateway module to implement integration with this module.
Features
- A transaction entity that can be used to track the remote state of individual transactions related to a parent payment.
- Automatic updates of transactions during cron.
Use cases
- Provide a UI within Drupal with details about each individual transaction related to a payment.
- Automatically fetch updates for pending transactions via cron for payment gateways that process transactions in batch.
- Automatically fetch updates for pending transactions via cron as a fallback mechanism in case IPNs/webhooks fail or get lost.
Implementing integration
See the Commerce Sage Payments module as an example. Specifically the SEVD gateway plugin for creating transactions, and the SagePayments payment type and the PaymentUpdater event subscriber for fetching updates from the payment provider.
Supporting organizations:
Sponsored initial development
Project information
- Project categories: E-commerce
- Ecosystem: Commerce Core
- Created by krystalcode on , updated
This project is not covered by the security advisory policy.
Use at your own risk! It may have publicly disclosed vulnerabilities.
