POS User Restrict Strype Bypass User
This module allows you to use stripe in POS with the group user assigned POS only.
auto_awesome What this module does
AI-generated from the code · Odoo 17.0Lets cashiers who are limited to their assigned points of sale still pay with Stripe in the Point of Sale, without being blocked by the point-of-sale user restriction.
This module makes the Stripe payment terminal work for users who are restricted to only their assigned points of sale.
Normally, the point-of-sale user restriction feature limits which points of sale a cashier can use. That restriction could also block the Stripe payment steps. This module removes that block for those users.
- When a restricted user starts a Stripe connection, creates a Stripe payment, or captures a Stripe payment, the system automatically bypasses the point-of-sale user restriction for that action.
- The change applies to the payment method configuration used by the Point of Sale (
pos.payment.method), specifically its Stripe connection, payment intent and capture operations. - No new menus, screens or buttons are added; the behaviour is automatic and invisible to the cashier.
- Users who are not in the assigned points of sale group are not affected and keep the normal restriction.
In short, it is a compatibility fix between the Stripe payment terminal and the point-of-sale user restriction, so restricted cashiers can complete card payments without extra steps.
Depends on
Models and fields (1)
- pos.payment.method · extends an existing model
Text generated by AI (DeepSeek) from reading the Odoo 17.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 17.0
Confirmed on 2026-11-03 in branch 17.0 of OCA/pos.
terminal Installation and usage
No verified informationInstallation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.