TNCSC_Odoo/addons/community_interac/views/payment_transaction_views.xml
metatroncubeswdev 7e860b65c5 feat(community_interac): Interac e-Transfer payment provider (Phase 5)
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>
2026-08-17 21:59:15 -04:00

33 lines
1.6 KiB
XML

<?xml version="1.0" encoding="utf-8"?>
<odoo>
<record id="view_payment_transaction_list_interac" model="ir.ui.view">
<field name="name">payment.transaction.list.interac.pending</field>
<field name="model">payment.transaction</field>
<field name="arch" type="xml">
<list string="Pending Interac Payments">
<field name="reference"/>
<field name="partner_id"/>
<field name="amount" widget="monetary"/>
<field name="currency_id" column_invisible="1"/>
<field name="create_date"/>
<field name="last_state_change"/>
<button name="action_confirm_interac_payment" type="object"
string="Payment Received" class="btn-primary"/>
</list>
</field>
</record>
<record id="action_payment_transaction_interac_pending" model="ir.actions.act_window">
<field name="name">Pending Interac Payments</field>
<field name="res_model">payment.transaction</field>
<field name="view_mode">list,form</field>
<field name="view_id" ref="view_payment_transaction_list_interac"/>
<field name="domain">[('provider_code', '=', 'interac'), ('state', '=', 'pending')]</field>
</record>
<menuitem id="menu_interac_root" name="Interac Payments" sequence="29"
groups="community_interac.group_interac_verifier"/>
<menuitem id="menu_interac_pending" name="Pending Payments"
parent="menu_interac_root" action="action_payment_transaction_interac_pending" sequence="10"/>
</odoo>