Signed Nonce & HMAC Security

Every link embeds nonce, timestamp, and HMAC signatures so model names and record IDs cannot be tampered with in transit.

Company-Aware Token Access

Filters Authorize.net tokens and acquirers to the active company, keeping multi-company deployments compliant by design.

Smart Default Tokening

Automatically preselects the customer’s preferred token and writes it back to sales orders and invoices for consistent billing.

Configurable Billing Validation

Require the billing fields that matter to your fraud program. Missing values are logged to chatter for follow-up.

Instant Back-to-Record Navigation

One-click return URLs drop users back on the originating customer, order, or invoice with the new token already stored.

Rich Audit Logging

Structured logging records validation failures, token promotion, and security checks without exposing cardholder data.

AI Financial Snapshot

Ships with an AI job that analyzes receivables, payables, and token creation trends over the last 90 days.

Portal Experience Enhancements

Dynamic payment method summaries, contextual badges, and responsive design guide staff through the add-card flow.

Token Lifecycle Automation

Tokens created via add-card are flagged until a transaction succeeds, then automatically marked production-ready.

Authorize Tokens Analytics

Built-in graph and pivot views help you monitor token creation trends, age mix, and acquirers. Filter by company and customer for precise insights.

Installation & Setup

1. Install the module: Go to Apps -> Search for "oe_payment_authorize_gateway" -> Click Install
2. Configure permissions: Navigate to Settings -> Users & Companies -> Grant accounting managers access to payment tokens
3. Initial configuration: Review your Authorize.net acquirer and ensure the flow is set to Server-to-Server

Basic Usage

1. Creating links: Open a customer, sales order, or invoice and click Add Card
2. Managing data: Ensure billing details meet your required fields before launching the portal
3. Using key features: Complete the Authorize.net form; the resulting token is linked to the originating record automatically
4. Generating reports: Use payment token views to filter Authorize.net cards by company and customer

Tips & Best Practices

• Pre-fill billing fields using partner templates to avoid portal rejections
• Use the default token field on customers to streamline repeat billing
• Monitor chatter logs for validation failures and resolve them immediately
• Pair with oe_ai_job_base to analyze invoice payment velocity automatically

Important Notes

Authorize.net only supports refunds after settlements clear (typically the next day). Ensure your accounting cycle accounts for this delay when scheduling automated charges.

Q: Which Odoo versions and dependencies are required?

A: Authorize Gateway supports Odoo 12 Community and depends on sale, account, payment, payment_authorize, website, and oe_ai_job_base.

Q: Do customers need portal accounts to add cards?

A: Yes. The add-card route uses Odoo's portal authentication so only invited customers with valid logins can submit payment data.

Q: Can we customize the required billing fields per company?

A: Absolutely. Use system parameters to define global defaults or company-specific lists. Missing fields block the flow and create chatter notes for follow-up.

Why Choose Odoo Engineering