M/03 — Alpenglow module
Run tap, insert, and manually-keyed card payments on physical Stripe Terminal readers — initiated from the Register Payment dialog, reconciled automatically, refundable through credit notes.
01 — Overview
Select an invoice, pick a terminal, collect the card.
Stripe Terminal Integration connects physical Stripe Terminal readers to Odoo invoicing. Register Payment from an invoice, choose a reader, and collect — the transaction is recorded, reconciled, and linked back automatically.
Supports card-present (tap or insert) and MOTO (manual entry for phone orders). Refunds route back to the original card through a credit-note wizard.
A full-screen overlay shows live payment progress during every transaction — amount, terminal name, and status messages — with automatic retry on decline.
No external POS, no separate hardware integration, no duplicate payment records — everything lands on the same invoice the accountant is already looking at.
02 — What’s included
Four capabilities across the full lifecycle.
F/01
Payment processing
Tap, insert, or swipe on any supported reader. MOTO for phone and mail orders. Automatic reconciliation. Card tokenization for repeat customers. Stripe Customer sync with smart deduplication.
F/02
Refund management
Guided wizard from credit notes. Funds return to the original card. Refund count, totals, and linked transactions tracked. Guards prevent refunding more than the original charge. Full chatter audit trail.
F/03
Reader management
Multi-reader support from a central list. Connectivity monitoring before every transaction. Each user can set a preferred terminal in Preferences. Pre-flight checks validate availability.
F/04
User experience
Full-screen overlay shows live status, amount, and terminal name. 20+ error conditions mapped to clear messages. Auto-retry on decline so customers can try again. Cancel in-progress payments with one click.
03 — How it works
Four steps from invoice to reconciled payment.
STEP 01
Register payment
Open an invoice, click Register Payment, select the Stripe journal.
STEP 02
Choose mode & reader
Pick Terminal (card-present) or MOTO (manual entry). Select the reader.
STEP 03
Present the card
The terminal activates. The overlay shows live status as the card is processed.
STEP 04
Done
Payment posts, invoice reconciles, card token saves for future use.
04 — Supported hardware
Every reader that runs server-driven integration.
| Device | Type |
|---|---|
| BBPOS WisePOS E | Countertop smart terminal. |
| Stripe Reader S700 | Countertop smart terminal. |
| Verifone P400 | Countertop terminal. |
| Stripe Reader M2 | Mobile card reader. |
| BBPOS Chipper 2X BT | Mobile Bluetooth reader. |
05 — Configuration
If Stripe is already configured, add readers and mark the journal.
1. Stripe payment acquirer
Under Accounting → Configuration → Payment Providers, configure Stripe with valid API keys. Same credentials as Odoo’s built-in Stripe integration.
2. Register terminal readers
Under Accounting → Configuration → Stripe Terminal Readers, create a record for each physical reader with its Stripe Reader ID (from your Stripe Dashboard), a label, and the device type. Check Status verifies connectivity.
3. Payment journal
On a payment journal under Accounting → Configuration → Journals, enable Is Stripe Journal in the advanced settings. The journal needs an outbound payment method if you plan to process refunds.
4. User preferences (optional)
Each user can set a default reader in Preferences so it’s pre-selected during payment registration.
06 — Compatibility
Odoo 17 – 19. CE & EE.
| Dependency | Purpose |
|---|---|
| account | Invoices, journals, and payment posting. |
| payment | Payment transaction framework and tokens. |
| payment_stripe | Stripe API credentials and base integration. |
07 — Support
A real engineer reads every email.
Email contact@aglow.dev
Stripe Terminal Integration is developed and maintained by Alpenglow Technologies LLC. Provided “as is” without warranty of any kind.
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