7e860b65c5
The plan flags this as the highest-risk module since the payment provider API is strict and version-sensitive. Before writing any code, read Odoo 19's own payment_custom module (its wire-transfer provider) end to end as a reference, since it's the closest first-party analog to a manual/ offline payment flow - this avoided the trial-and-error that hit the other modules and got the core logic right on the first install attempt. payment.provider gains code='interac' (via selection_add, same pattern payment_custom uses for 'custom') plus interac_recipient_email (required_if_provider='interac' - Odoo only enforces this when the provider's state is enabled/test, so the module ships a disabled, unconfigured provider record and the deployment layer configures + enables it, keeping client specifics out of product code) and a configurable interac_deadline_hours. Flow: selecting Interac at checkout calls _apply_updates, which sets the transaction 'pending' and emails instructions (recipient address, amount, reference, deadline) via a mail.template - no dynamic per-transaction data needs to live in the static provider-level pending_msg field, since the reference/amount are already shown on Odoo's generic payment status page. A "Pending Interac Payments" admin list (Interac Payment Verifier group) has a one-click "Payment Received" button calling action_confirm_interac_ payment (-> _set_done, which triggers Odoo's normal order/invoice reconciliation - no need to reimplement that). An hourly cron cancels unconfirmed pending transactions past the deadline and emails a cancellation notice. Verified against a live Odoo 19 + Postgres 16 container: 4/4 automated tests pass, plus a full manual live run of both cycles the plan's gate asks for - drove a transaction through the actual /payment/interac/process controller to pending (confirmed the instructions email), used the treasurer action to confirm it to 'done', and separately backdated a second transaction's last_state_change and triggered the auto-cancel cron via ir.cron's method_direct_trigger, confirming both the state change to 'cancel' and the cancellation email. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
44 lines
1.4 KiB
Python
44 lines
1.4 KiB
Python
{
|
|
'name': 'Community OS - Interac e-Transfer Payments',
|
|
'version': '19.0.1.0.0',
|
|
'category': 'Accounting/Payment Providers',
|
|
'summary': 'Semi-automated Interac e-Transfer payment provider for Canadian organizations',
|
|
'description': """
|
|
Community OS - Interac e-Transfer Payments
|
|
=============================================
|
|
|
|
A generic Interac e-Transfer payment provider for the Odoo 19 payment
|
|
framework:
|
|
|
|
* Configurable recipient e-transfer address, org name, and deadline
|
|
(provider config, never hardcoded)
|
|
* Automated instructions email with a unique reference code
|
|
* Treasurer "Pending Interac" view with one-click "Payment received"
|
|
* Configurable auto-cancel window for unconfirmed transfers
|
|
|
|
Sellable to any Canadian organization accepting Interac e-Transfer.
|
|
""",
|
|
'author': 'Metatroncube Software Solutions LLP',
|
|
'website': 'https://www.metatroncube.com',
|
|
'license': 'LGPL-3',
|
|
'price': 0.00,
|
|
'currency': 'USD',
|
|
'depends': [
|
|
'payment',
|
|
'account',
|
|
],
|
|
'data': [
|
|
'security/interac_security.xml',
|
|
'views/payment_interac_templates.xml',
|
|
'views/payment_transaction_views.xml',
|
|
'data/payment_method_data.xml',
|
|
'data/payment_provider_data.xml',
|
|
'data/mail_templates.xml',
|
|
'data/ir_cron.xml',
|
|
],
|
|
'demo': [],
|
|
'images': ['static/description/banner.png'],
|
|
'application': False,
|
|
'installable': True,
|
|
}
|