Deltatech Payment

Deltatech Paymentr

This module extends Odoo’s payment layer with two independent behaviours used in Terrabit deployments: confirming a sales order on a partial payment, and controlling which payment providers are offered on payment links.

Features:

• ✓Confirm a sales order as soon as a (partial) payment is received, without waiting for the full amount.
• ✓Optionally keep payment transactions out of the “done” state while still confirming the related order, driven by a system parameter.
• ✓A per-provider switch that decides whether a payment provider is offered when the customer pays through a payment link, while leaving the regular e-commerce checkout and express-checkout flows untouched.

Sales order confirmation on partial payment:

When a payment transaction is set to done, the related quotations in state “draft” or “sent” are confirmed (with the confirmation email sent), as long as the paid amount is greater than zero.

The behaviour is refined by the system parameter payment.do_not_set_transaction_done:

• When it evaluates to a false value (the default), the standard Odoo behaviour applies: the transaction moves to “done” and the order is confirmed.
• When it evaluates to a true value, the transaction is not moved to “done”, but the related sales order is still confirmed on a positive payment. This is useful when the actual settlement of the transaction is handled by a separate process while the order must already be confirmed.

Restricting payment providers on payment links:

Each payment provider gains an “Allowed on Payment Links” option (found in the provider’s Availability section). It defaults to enabled, so existing providers keep working until configured otherwise.

When a payment link is generated for a sales order, that order is flagged as restricted. From then on, paying that order online only offers the providers whose “Allowed on Payment Links” option is enabled; providers with the option disabled are hidden.

The restriction is enforced from trusted server-side state on the sales order, read through the access-token-validated order identity — not from a URL parameter — so a buyer cannot lift it by editing the payment link. Website e-commerce checkout is unaffected, because its cart orders are never flagged.

Configuration:

• Sales order confirmation: set the payment.do_not_set_transaction_done system parameter (Settings > Technical > System Parameters) to a truthy value to keep transactions out of “done” while still confirming the order; leave it absent or false for the standard behaviour.
• Payment links: open Accounting/Website > Configuration > Payment Providers, edit a provider and toggle “Allowed on Payment Links” in the Availability section.

Usage:

Generate a payment link for a sales order as usual. The order is flagged automatically, and from then on only the providers with “Allowed on Payment Links” enabled are offered when that order is paid online.

Scope and limitations:

• ✓The restriction is keyed on the sales order, so it applies wherever that order is paid online (the payment link and the customer portal “Pay Now”). Website e-commerce checkout uses separate cart orders and is not affected.
• ✓Invoice payment links rely on the portal page flow and are not covered by this option.
• ✓A payment method disappears only when all of its compatible providers are filtered out; a method backed by several providers stays available until every backing provider is disabled.