| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) • Inventory (stock) |
| Lines of code | 1742 |
| Technical Name |
us_sales_order_credit_card_authorization_captu |
| License | OPL-1 |
| Website | https://pokutsoft.com |
| Versions | 18.0 19.0 |
US Sales Order
Sales Order Credit-Card Authorization & Capture (BYOK): authorize on the order, capture on shipment, tokens only — no card data on us
Sales Order Credit-Card Authorization & Capture (BYOK): authorize on the order, capture on shipment, tokens only — no card data on us
Key Features
tokenized at your gateway, and this module stores
tokenized at your gateway, and this module stores only the token and the last four digits — never the full card number, never a CVV. Every request goes from your Odoo straight to your own processor account and nowhere else, so the sensitive
Authorize on order, capture on ship
Authorize on order, capture on ship — a hold is placed at confirmation and the money is only captured when the delivery is validated, never before.
BYOK tokenization, PCI SAQ-A
BYOK tokenization, PCI SAQ-A — cards are tokenized at your own gateway; we keep only the token reference and last four digits, no PAN and no CVV.
Three processors, one flow
Three processors, one flow — Authorize.Net, Stripe and Braintree share one normalized authorize / capture / void / refund interface.
Partial & split capture
Partial & split capture — capture only what shipped; the remaining authorized balance stays open for the next delivery or is released.
Automatic void on cancel
Automatic void on cancel — cancelling an unshipped order releases the hold so the customer's available credit is freed immediately.
Refund after capture
Refund after capture — issue a full or partial refund against a captured charge straight from the order without leaving Odoo.
AVS & CVV result capture
AVS & CVV result capture — the address- and card-verification results the gateway returns are stored on every authorization for fraud review.
Authorization expiry guard
Authorization expiry guard — a scheduled job flags holds that pass your processor's validity window so you never try to capture an expired auth.
Vaulted customer cards
Vaulted customer cards — tokenize a card once and reuse it across future orders for the same customer without re-entering any card data.
One-click connection test
One-click connection test — verify each gateway key with a live handshake and see exactly which merchant account you reached.
Screenshots
Why Choose This Module
Confirm an order and it places an authorization hold for the order total against the saved token. Validate the shipment and it captures exactly the amount you shipped — full or partial — against that same authorization. Cancel before shipping and it voids the hold so the customer is never charged. Ship short or process a return and it refunds the difference. Authorizations that age out past your processor's hold window are flagged automatically so nothing is captured after it has expired.
Specifications
- Compatible: Odoo 18.0 / 19.0
- License: OPL-1
- Languages: English
- Author: Pokutsoft
- Dependencies: sale_stock, mail
- Support: support@pokutsoft.com
Update date: 2026-07-05
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) • Inventory (stock) |
| Lines of code | 1742 |
| Technical Name |
us_sales_order_credit_card_authorization_captu |
| License | OPL-1 |
| Website | https://pokutsoft.com |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module