| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 977 |
| Technical Name |
aglow_stripe_payment_element |
| License | OPL-1 |
| Website | https://www.odoo.com |
| Versions | 15.0 16.0 17.0 18.0 19.0 |
M/02 — Alpenglow module
Charge a credit card from the Odoo backend invoice form, in a Stripe-hosted modal — no POS app, no portal redirect, no external page. Payment is posted and reconciled the moment the charge succeeds.
01 — Overview
One click on the invoice. One charge on the card.
Stripe Backend Payments adds a Pay with Stripe button directly to the backend invoice form. Accounting and sales can collect payment without switching to the POS, opening a portal link, or leaving the record.
Clicking the button opens an in-app modal with amount, card input, and confirmation. Card details are collected by Stripe — nothing touches your server.
On success, the module creates and posts an account.payment, links it to the invoice, and clears the outstanding balance. Every payment is tracked through a payment.transaction with the Stripe PaymentIntent and PaymentMethod IDs.
Accounting and sales stay on the invoice they’re already looking at — one record, one reconciled payment, no separate journal entry to chase.
02 — What’s included
Four capabilities, one button.
F/01
Backend payment flow
Branded modal with amount display, card input, action buttons. Real-time validation. 3D Secure handled automatically. Success screen with transaction ID. Cancel anytime.
F/02
Accounting integration
Posts account.payment on success, reconciles invoice balance, creates payment.transaction with PaymentIntent and PaymentMethod IDs. Multi-currency, uses the invoice’s currency.
F/03
Customer management
Creates a Stripe Customer for the partner when none exists. Deduplicates against the partner record and existing tokens. Stripe Customer ID persists on the partner for future charges.
F/04
Error handling
30+ Stripe error codes mapped to plain-language messages. Errors show inline in the modal so the user can correct and retry. Full backend logging for troubleshooting.
03 — How it works
Four steps, no redirects.
STEP 01
Pay with Stripe
Open a posted customer invoice. Click the Pay with Stripe button in the header.
STEP 02
Enter card details
The payment modal opens with the amount due and Stripe’s card input form.
STEP 03
Process payment
Click Process Payment. 3D Secure triggers automatically when the issuer requires it.
STEP 04
Done
Payment is posted, the invoice balance is reconciled, you’re back on the invoice.
04 — Smart visibility
The button hides when it doesn’t apply.
Pay with Stripe only appears when all three conditions are met.
COND/01
Posted invoice
The invoice must be Posted. Draft and cancelled invoices don’t show the button.
COND/02
Customer invoice
Only out_invoice — vendor bills are excluded.
COND/03
Outstanding balance
Fully paid invoices hide the button automatically.
05 — Configuration
If Stripe is already configured, there’s nothing else to do.
1. Stripe payment acquirer
Go to Accounting → Configuration → Payment Providers. Configure Stripe with your Publishable Key and Secret Key. This module uses the same credentials as Odoo’s built-in Stripe integration.
2. Assign a journal
Make sure your Stripe acquirer has a payment journal assigned — that’s where successful payments will post.
3. You’re ready
Open any posted customer invoice with an outstanding balance. The Pay with Stripe button is in the header.
06 — Compatibility
Odoo 17 – 19. CE & EE.
| Dependency | Purpose |
|---|---|
| account | Invoices, journals, and payment posting. |
| payment | Payment transaction framework. |
| payment_stripe | Stripe API credentials and base integration. |
07 — Support
A real engineer reads every email.
Email contact@aglow.dev
Stripe Backend Payments 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