POS integrations panel
Connect your point of sale from the dashboard — no code required — so every sale credits points or stamps to your customers automatically.
The point-of-sale Integrations panel lets you connect your POS straight from the dashboard, without writing code. Once connected, every sale your POS registers reaches Xtarly and credits points or stamps to the customer automatically.
You'll find it under Settings → Integrations in your organization.
Have a development team and prefer an API integration? Use the POS REST API. The panel and the API are complementary.
External POS connectors are available from the Shared plan. On the Wallet plan the catalog cards show a "From Shared plan" badge and clicking one takes you to the plans page.
How to connect your POS
- Open Settings → Integrations and search the catalog for your POS by name.
- Click Connect.
- Depending on the POS, authorize with one click (OAuth) or paste the credentials the form asks for (a token, or your POS API key and secret).
- If your POS supports webhooks, Xtarly registers them automatically or shows you a unique URL to paste into your POS settings.
- Done: the POS shows as Connected, and the Received sales section lists every payment with its status.
One-click connection (OAuth)
Some POS systems let you authorize without copying credentials. Mercado Pago is the most common case: click Connect with Mercado Pago, authorize with your account, and you're back in the panel already connected. Whenever the panel shows a Connect with… button for your POS, that's the short path; the "I'd rather paste my token" option is always available if you prefer to do it by hand.
POS with an automatic connector
There are 15 automatic connectors in the catalog today, plus the native XtarlyPOS integration.
| POS | How it connects | Identifies the customer? |
|---|---|---|
| XtarlyPOS | Native — sign in at pos.xtarly.com with your Xtarly account | ✅ |
| Alegra | Account email + API token | ✅ |
| Bsale | Access token (issued by Bsale) | ✅ by phone only† |
| CleanCloud | API token | ✅ |
| Clip | Key + secret | Via QR/signals* |
| Clover | Merchant ID + API token | ✅ |
| Epos Now | Key + secret | Via QR/signals* |
| Lightspeed (X-Series) | Store prefix + personal token | ✅ |
| Loyverse | API token | ✅ |
| Mercado Pago | OAuth (one click) or token | Via QR/signals* |
| Odoo POS | URL + database + email + API key | ✅ |
| Poster | Account name + integration token | ✅ |
| Shopify | Domain + token + secret (webhook) | ✅ |
| Square | Access token | ✅ |
| SumUp | API key | Via QR/signals* |
| Toast | Client ID + secret + restaurant GUID | ✅ |
* Payment terminals (Mercado Pago, Clip, SumUp) and Epos Now don't send the payer's identity. Use the QR match (below) to credit those sales; until then they appear as "Unmatched".
† In Bsale the link to your customer is the phone number on their customer record: Bsale has no free-text note field on the document, so a ticket issued to a walk-in or to a record without a phone is logged but credits no one.
Square, Lightspeed and Toast don't operate in Mexico. Their connectors are for businesses charging with those systems outside MX; in the catalog they're listed after the ones available in Mexico.
SICAR (with Xtarly Bridge, beta)
SICAR Punto de Venta is desktop software: it lives on a PC in your business and has no internet API Xtarly can connect to. That's why the integration works through Xtarly Bridge, a program of ours installed on the SICAR server PC (the one that stores the database), which reads the sales and sends them to Xtarly.
SICAR is in assisted beta: it isn't shown to everyone in the catalog yet. If you use SICAR, write to us and we'll walk you through installing Xtarly Bridge.
- In Settings → Integrations, open SICAR Punto de Venta and click Connect (no credentials needed).
- Xtarly shows you your pairing link. Download Xtarly Bridge (we send you the installer during the beta) and install it on the SICAR server PC.
- Paste the link into the Xtarly Bridge setup wizard. From then on, sales charged in SICAR arrive in the Received sales section.
What to know before you start:
- How to link the sale to the customer. Type the customer's mobile number or email, or scan her card, in the sale's Comment button. With cash you can also use the payment reference. With card or bank transfer, the reference belongs to the bank: use Comment. She doesn't need to be registered as a customer in SICAR, and anything else you write in the Comment isn't sent to Xtarly. During the beta we confirm with your first real sale that the Comment button reaches Xtarly, just like the real card with your scanner.
- Priority: the card wins; then the mobile number or email in the Comment; then the one in the payment reference; and if there's nothing, the customer assigned in SICAR with a phone number or email.
- It only credits people already in your program. If the number or email doesn't belong to any customer in your program, or the sale has no one, it's logged as "Unmatched" and credits no one. If the cashier mistypes a number and that number belongs to another customer, the purchase is credited to her: confirm the number before charging.
- Later cancellations don't take points back. If a sale is cancelled in SICAR after it was sent, points are adjusted by hand. A sale cancelled before it's sent doesn't earn.
- The server PC must be on and online for sales to reach Xtarly.
How to tell whether Xtarly Bridge is still connected
The SICAR connection in Settings → Integrations shows the status of Xtarly Bridge and the time of the Last signal:
| Status | What it means |
|---|---|
| Waiting for Xtarly Bridge | The first signal has not arrived yet. It still needs to be installed on the SICAR computer and the pairing link pasted. |
| Connected | Xtarly Bridge is sending signal. If you don't see new sales, none have been recorded in SICAR yet. |
| No recent connection | It has not sent a signal in the last few minutes. It may be the network; if it continues, check the SICAR computer. |
| No signal | It has not sent a signal for more than 30 minutes. Check that the SICAR computer is on and online. |
| Needs attention | It is running but not sending sales. Check the diagnostics or contact support. |
| Paused by plan | It is still sending signal, but your current plan does not include connectors: sales are not recorded until you change plans. |
Below it, the Diagnostics show the Xtarly Bridge version, which computer it runs on, whether it runs as a Windows service or in an open window, how many sales are waiting to be sent and when it last read SICAR.
How soon sales arrive
- With a webhook: the sale reaches Xtarly as soon as your POS reports it, almost instantly.
- Without a webhook (or while you set it up): Xtarly checks your sales every 10 minutes — every 15 for Alegra, CleanCloud and Epos Now. It's the only path for Clover, Epos Now, Odoo POS, Poster, SumUp and Toast, which don't use webhooks, and the main path for Bsale, where the automatic notification has to be requested from Bsale by email.
- Shopify is the opposite case: it works through webhooks only, with no periodic check.
You don't lose sales by skipping the webhook: they just arrive a little later.
When each connector starts counting: Clover, Toast and Lightspeed count from the moment you connect and don't import earlier sales; Bsale starts reading from the previous day. On Lightspeed that includes layaway or on-account sales opened before you connected, even if they're paid off later.
Which amount earns points
Tips don't earn points; tax does. When your POS separates the tip from the charge (Square, Clover and Toast do), Xtarly credits only the purchase. On systems that don't report the tip separately, the total is credited exactly as the POS delivers it.
QR match: credit sales from anonymous payments
When a payment doesn't carry the customer's identity, there's a simple way to credit it:
- At checkout, ask the customer for their loyalty card (the QR on their Wallet card).
- Scan that QR into the note or reference field of the charge in your POS.
- Xtarly detects the code inside the sale and credits their points or stamps automatically.
In Received sales every payment shows its status — Credited, Unmatched, Duplicate or Error — and, when credited, how it was matched: by phone, by email, via QR scanned at the POS, or through signals detected in the payment data.
Several accounts of the same POS
If you take payments with more than one account of the same system — three Clover merchants, two Toast restaurants, two Shopify stores, two Poster accounts — you can connect them all. On the card of the POS you already connected, use Connect another branch (Clover and Shopify) or Connect another account (everything else), and go back to the list with ← All connections.
- Each connection is tied to its branch. If your business has more than one branch, adding a second connection asks which one it belongs to: its sales are credited there.
- Name it however you recognize it. The Name to identify it field (for example “Downtown branch”) is optional and helps you tell them apart in the list.
- Disconnect one without touching the others. The disconnect notice tells you exactly which account stops sending sales; the rest keep working.
- The catalog card shows Connected · N, with the number of connected accounts.
If your branches live inside the same account of your POS, you don't need another connection: map them from the Branches tab of the connection you already have (below).
Authorizing the same account twice doesn't create a new connection: the dashboard tells you that account is already connected to this business and asks you to authorize a different one.
Branches: which store each sale lands in
If you have more than one branch, the connection's Branches tab lets you map each POS store or terminal to an Xtarly branch. Sales already received and future ones get recorded under that branch, so your per-branch analytics match reality.
- Stores and terminals show up on their own as the first sale from each arrives; until you map them they appear as Unassigned.
- When you assign one, Xtarly tells you how many past sales were reassigned by that change.
- Default branch is where sales that arrive with no identifiable store or terminal go.
Things to keep in mind
- Bsale: the access token isn't generated from your dashboard — you request it from Bsale by email. If your account is in Mexico or Peru, enter the country in its field: each country uses a different server. Credit notes, returns and quotes don't earn points.
- Clover: each location is a separate merchant with its own ID and token, so you connect them one by one — and they coexist in the dashboard, each tied to its branch. Clover reserves API tokens for testing and requires OAuth tokens in production; our App Market app is in progress, so if your Clover is a production account, write to us and we'll help you connect it.
- Toast: you need an RMS Essentials subscription or higher and the 8.4 Manage Integrations permission. When creating the credential, check orders:read, guest.pi:read and restaurants:read — without
guest.pi:readthe orders arrive with no guest phone or email and nobody can be credited. Only closed, paid checks earn points, and each location connects with its own GUID, as one more connection inside the same business. - Lightspeed: personal tokens only exist on the Plus plan and can only be created by an admin user.
- Odoo: on Odoo Online the external API is only available on the Custom plan; on self-hosted and Odoo.sh it always works.
- CleanCloud: the API requires the Grow or Grow+ plan, and the webhook is registered by hand from your account.
- SICAR (beta): requires installing Xtarly Bridge on the SICAR server PC, and we install it with you. To link the sale, the cashier types the customer's mobile number or email, or scans her card, in the sale's Comment button; with cash the payment reference also works, and with card or bank transfer the reference belongs to the bank. If nothing is entered, the customer assigned in SICAR with a phone number or email earns. The card takes priority, and the sale only credits if that customer is already in your program (otherwise it's "Unmatched"). We confirm the Comment button and the real card with your scanner during the beta. Later cancellations don't take points back: they're adjusted by hand. Available from the Shared plan, like the other connectors. More detail.
- Mercado Pago + XtarlyPOS: if you charge with the terminal from XtarlyPOS, that sale already comes in through the POS (with customer and branch) and the connector discards it — no duplicates. Payment links charged from your phone still come in through the connector.
Is your POS not on the list?
- If it shows a Coming soon badge, register your interest with Notify me when it's ready and we'll let you know when the connector goes live.
- If it's not listed, pick Other / my POS is not on the list. Xtarly works alongside any POS through the universal path: your customers show their card (QR or phone number) when paying and you record the sale with the cashier app or the partner API.
Disconnecting a POS
From the connected POS card, click Disconnect. We stop receiving sales and delete the stored credentials; the history of sales already received is kept.