Skip to Content

POS Tabby (QR Payment Terminal)

by
Odoo

$ 119.00

v 18.0 Third Party
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies • Point of Sale (point_of_sale)
• Discuss (mail)
• Inventory (stock)
• Invoicing (account)
Lines of code 1281
Technical Name bb_pos_tabby
LicenseLGPL-3
Websitehttps://bbtech.ae
You bought this module and need support? Click here!
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies • Point of Sale (point_of_sale)
• Discuss (mail)
• Inventory (stock)
• Invoicing (account)
Lines of code 1281
Technical Name bb_pos_tabby
LicenseLGPL-3
Websitehttps://bbtech.ae

POS Tabby Payment Gateway

Accept Tabby Buy Now Pay Later (BNPL) payments directly in Odoo 18 Point of Sale. The cashier selects Tabby (QR) from the POS payment screen; the customer completes payment using Tabby checkout (scan QR or open link). The system confirms payment and completes the POS order—no manual steps, no POS crashes.

POS Tabby Payment Gateway

Tabby BNPL in Odoo 18 Point of Sale

The POS Tabby Payment Gateway module brings Tabby's Buy Now Pay Later flow into Odoo 18 Point of Sale. It is designed for retailers in UAE, KSA, and other markets where Tabby is available. Cashiers use a dedicated Tabby (QR) payment method; customers pay via QR code or checkout link; the system polls payment status and completes the order when Tabby confirms payment.

Tabby POS Payment Flow

A) Tabby Terminal Configuration

Configure one or more Tabby terminals per company with secure API settings:

  • Merchant Code & Secret Key: Tabby API credentials; secret key is never sent to the POS frontend
  • Environment: Test or Production (live) mode selection
  • Base URL: Optional override for Tabby API base URL
  • Poll Interval & Timeout: How often to check payment status and when to cancel (e.g. 5s poll, 300s timeout)
  • Auto-Capture: Option to capture payment automatically when Tabby status is AUTHORIZED
  • Per-Company / POS: Terminals can be enabled per company and linked to specific POS payment methods

B) POS Payment Method Integration

Seamless integration with Odoo 18 POS payment screen:

  • Tabby (QR) Payment Method: Dedicated payment method type that appears alongside Cash and Card
  • Payment Screen: Cashier sees Tabby (QR) button; clicking it creates a payment line and opens the Tabby popup
  • Core Flow Preserved: Payment line is created via core addNewPaymentLine so the line is fully initialized and linked to the order
  • No Regressions: Cash and Card payment methods work normally; no POS crash when switching between methods

C) Customer Checkout Flow (BNPL)

End-to-end Tabby checkout from POS:

  • Cashier Initiates: Selects Tabby (QR), popup opens with QR code or checkout link
  • Customer Pays: Scans QR or opens link on phone; completes Tabby checkout (installments, etc.)
  • Status Updates: Pending → Authorized / Paid → payment line marked done; or Failed / Cancelled with friendly message
  • Auto-Complete: On success, payment line is marked done and Tabby payment/session IDs are stored for reconciliation

D) Payment Status Handling & Safety

Reliable status handling and error recovery:

  • Polling & Retry: Backend polls Tabby payment status at configured interval until CLOSED, AUTHORIZED, REJECTED, or EXPIRED
  • Cancel Removes Line: If customer or cashier cancels, the payment line is removed so the cashier can choose another method
  • Error Handling: No POS crash on API errors; friendly error message shown; optional logging for debugging
  • Timeout: Session times out after configured seconds; payment line is removed and user can retry or use another method

E) Accounting & Reconciliation

Integration with POS accounting and reporting:

  • POS Session Closing: Tabby payments are included in session totals and closing
  • Journal & Payment Method: Tabby payment method is mapped to your chosen journal; payments post to accounting as configured
  • Transaction References: Tabby payment ID and session ID stored on pos.payment for reconciliation with Tabby dashboard
  • Reports: Standard POS reports show Tabby payments; backend Payments tab displays Tabby references

F) Security & Permissions

Secure configuration and access control:

  • Terminal Keys: Secret API key stored only on server; never sent to browser or POS UI
  • Access Groups: POS Manager can configure terminals and payment methods; POS User can use Tabby at checkout
  • Company Scoping: Terminals and payment methods respect multi-company settings

G) FAQ

See Frequently Asked Questions below for test vs live keys, QR display, troubleshooting, and more.

Frequently Asked Questions

Q: What is the difference between Tabby test and live keys?
A: Use test keys in the Tabby terminal configuration when your Tabby environment is set to Test. Test mode allows you to simulate payments without real charges. For production, switch to Production environment and use your live merchant code and secret key from the Tabby dashboard.
Q: Why is the QR code not showing in the Tabby popup?
A: Ensure you have upgraded the module and cleared browser assets (hard refresh Ctrl+Shift+R or clear cache). The module generates a QR image from the Tabby checkout URL via Odoo's barcode route. If the popup opens but the image is missing, check that the create_session route returns a valid qr_code_url and that your Odoo server can serve /report/barcode/QR/...
Q: Are there network or firewall requirements for Tabby?
A: The Odoo server must be able to reach the Tabby API (api.tabby.ai) over HTTPS. All Tabby API calls are made server-side from Odoo; the POS frontend only calls your Odoo JSON routes (e.g. /bb_pos_tabby/create_session, /bb_pos_tabby/payment_status). Ensure outbound HTTPS is allowed from your Odoo host.
Q: How do I validate that a Tabby payment was successful?
A: When the customer completes payment, Tabby returns status CLOSED (with captures) or AUTHORIZED. The module marks the POS payment line as done and stores the Tabby payment_id and session_id on the payment record. You can cross-check these IDs in the Tabby merchant dashboard and in Odoo (POS order → Payments tab).
Q: How do I troubleshoot Tabby payment failures?
A: Check the browser console for [bb_pos_tabby] messages. On the server, review Odoo logs for bb_pos_tabby create_session, payment_status, or cancel_session errors. Verify terminal credentials, merchant code, and that the Tabby API is reachable. For "assert_editable" or POS crash issues, ensure you are on the latest module version and have cleared assets after upgrade.
Q: Does the module support refunds?
A: The module supports Tabby capture (when using authorize-then-capture) and can be extended for refunds via the Tabby API. Refund capabilities depend on your Tabby contract and the payment status (CLOSED with captures). Check the module documentation or contact support for refund configuration.

Screenshots

Explore the POS Tabby Payment Gateway in action:

Terminal Configuration

Tabby terminal form with merchant code, secret key, environment, poll interval, and timeout

Payment Method Setup

POS payment method with Tabby (QR) terminal selected

POS Payment Screen

POS payment screen with Tabby (QR) button alongside Cash and Card

Tabby Popup with QR

Tabby payment popup showing QR code and waiting for payment

Pending status – customer scanning QR or completing checkout

Success status – payment confirmed, line marked done

Failed or cancelled status – payment line removed, cashier can choose another method

POS Order & Receipt

POS order receipt showing Tabby payment

POS order backend – Payments tab with Tabby payment and references

Session Closing

POS session closing with Tabby payment totals

Professional Support & Services

Binary Bridge Technology Services

Binary Bridge Technology Services provides comprehensive support for the POS Tabby Payment Gateway module. Our team of Odoo experts ensures smooth installation, configuration, and ongoing maintenance of your Tabby POS integration.

Installation & Implementation Support

We offer professional installation services to get Tabby payments running in your POS quickly:

  • Install and configure the module for Odoo 18
  • Set up Tabby terminal(s) with test or live credentials
  • Configure POS payment methods and journal mapping
  • Verify QR display, polling, and session closing
  • Train your staff on the Tabby checkout flow

Customization Services

Need adjustments or extra features? Our development team can customize the module to match your processes:

  • Custom fields or workflows for Tabby payments
  • Integration with other payment terminals or reporting
  • Refund workflows and reconciliation reports
  • Multi-company or multi-currency enhancements

Ongoing Support & Maintenance

Our support team is available to assist with:

  • Technical issues and bug fixes
  • Odoo version upgrades and module updates
  • Tabby API changes and compatibility
  • Best practices for reconciliation and security
Request Support Chat on WhatsApp
Binary Bridge Technology Services Professional Odoo Solutions | POS & Payment Integration | Expert Support
info@bbtech.ae | +971 56 128 6321 | www.bbtech.ae

Please log in to comment on this module

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.