Skip to content

Loyalty built into your POS, processor and checkout

Payments is Qurable’s module that brings your program into the payment: it decides with AI and applies discounts, cashback and points inside the authorization, in ~150 ms, at your POS, on your card or in your web and app checkout.

See how it works

Banks and fintechs, in production

Our banking and fintech clients already deliver cashback at payment with Qurable.

Pomelo, Santander Peru, Banisi and Konfío, among others. With Pomelo, banks, fintechs and companies that issue cards turn on loyalty and cashback without a separate technical project.

  • ~150 msReward decisionInside the authorization
  • < 50 msMember identificationp95, server-side
  • 99.5%SLACommitted availability
  • 18MMembersIn programs running on Qurable

Before and after

Payment-linked loyalty: next to the payment or inside it.

Most programs calculate points after the purchase, in batch. Qurable decides and applies the reward while the payment is being authorized.

Loyalty alongside the payment vs. loyalty inside the payment
Next to the paymentInside the payment
When it decidesAfter the purchase, in batchInside the authorization, in ~150 ms
How it picks the benefitThe same rule for every customerAI picks the best one for each customer, within the rules and the budget
Where the reward showsOn the next statement or in the appOn the same receipt or at checkout
Paying with pointsA separate redemption, on another screenAt the POS or checkout, with hold and reversal
Who funds itA single funderBank and merchant, each contribution on the ledger

Camila’s case

Camila pays with her card. Cashback, then the bank’s points.

A bank, a participating merchant and a cashback campaign co-funded by both: each step, with its timing.

Camila: pays USD 120 with her card at a participating running store

She doesn’t need to show anything else: the card identifies her as a member of the bank’s program in under 50 ms.

Qurable receives the purchase from the bank’s processor, inside the authorization

CCamilaUSD 120 · card0 msAuthorization · running storeRunning shoesUSD 120CardBank · credit
01 / 05

Simulation based on a hypothetical case.

Payment methods

Pay with money, points or coupons, in the same authorization.

Members pay however they want and the reward applies at that moment. Every transaction is recorded on the ledger, with its hold, capture and reversal.

  • Money

    Card, wallet or cash: the discount, cashback or points apply to the same payment.

    Example
    10% cashback at payment with the bank’s card.
  • Points

    Points pay for all or part of the bill: they’re held at authorization and confirmed at capture.

    Example
    Paying with points at the POS or at checkout.
  • Coupons

    Cash-value or product coupons, single-use, validated at the POS with a QR.

    Example
    A USD 10 QR coupon for the next purchase.

Payment cycle

Authorize, capture or reverse, like any other payment.

  • AuthorizePoints are held when the payment is authorized.
  • CaptureThey’re confirmed at capture, together with the payment.
  • ReverseIf the payment is canceled or returned, they come back entry by entry.
  • Split paymentPoints plus another method in one purchase, in the web and app checkout and in connected ecommerce.
  • ClawbackIf Camila returns the item after spending the cashback or points, the balance goes negative with the debt recorded.
See the ledger in detail
Camila’s receipt · web checkoutUSD 135
Authorized
  • CardUSD 105
  • PointsUSD 20
  • CouponUSD 10
Ledger entries
  • HoldAt authorization
  • ConfirmAt capture
  • ReverseIf canceled
Campaign budget71% used
Illustrative figures.

Where it plugs in

At the POS, on the card and at checkout.

Three integration points on the same rules engine and the same ledger. What you already have connected keeps working.

  • Identification at the POS

    A QR that changes every 30 seconds or an Apple Wallet and Google Wallet pass.

  • Reward on the receipt

    Discounts, gifts and points applied to the same sale, in ~150 ms.

  • Pay with points at the POS

    Members pay the bill with points: they’re held at authorization and confirmed at capture.

  • Your POS, via API

    Napse (TOTVS), already live with clients, and other POS systems via API with signed webhooks.

  • Cashback at payment

    In production with Pomelo, Santander Peru, Banisi and Konfío.

  • Campaigns by merchant

    By merchant type, country, channel and customer segment.

  • Balance on every payment

    The points balance, visible in real time on every transaction.

  • Own or co-branded

    Points and cashback in your program or in a partner brand’s.

  • Ready-made checkout

    For web and app, where members earn and pay with points.

  • Split payment

    Points plus a card or another method in one purchase.

  • Connected ecommerce

    VTEX, Shopify and Tiendanube, already live with clients.

  • Payment methods

    MODO, Mercado Pago and Stripe, already live with clients.

Want to see it with your POS or checkout? We’ll walk you through the flow with your payment methods in a call.

Own or co-branded card

Your program or your partner brand’s.

If you issue cards, loyalty comes with the payment. You choose where the reward lives: in your own program or in a partner brand’s.

  • Own program

    Points or cashback are credited in Qurable and customers see their balance in your app. You control the rules and the experience.

    Example
    A bank that rewards card usage with its own program.
  • Co-branded program

    Qurable calculates the reward and sends it to the partner brand’s program. Customers earn where they already earn.

    Example
    A card that earns miles in an airline’s program.

Operations

If something fails, the sale goes on.

Loyalty never holds up a payment. Every transaction is recorded, can be reversed and is reconciled with your core.

  • The sale is never blocked

    If the platform doesn’t respond, the payment closes and points are credited once service is restored. Redemption does need a connection.

  • Every entry, reversible

    Returns and cancellations reverse the reward and the points on the ledger, with a full trail.

  • Reconciled with your core system

    Hash-chained ledger with automatic reconciliation audits and a daily export to your data warehouse.

  • Certified security

    ISO 27001 and a 99.5% availability SLA.

Questions

Questions about loyalty at the POS and checkout.

It means applying program rewards (discounts, cashback or points) inside the payment itself, at the POS, on the card or at checkout, instead of calculating them afterwards. Qurable decides the reward inside the authorization, in about 150 ms.

A real-time loyalty program decides and applies the benefit while the customer pays, not in a later batch. In Qurable, the member is identified in under 50 ms, the rules and AI choose the benefit and it is applied inside the payment authorization in ~150 ms, at the POS, processor or checkout; every effect is recorded on the ledger.

It’s Qurable’s module that connects your program to the payment: the POS, the card processor or issuer and the web and app checkout. It uses the same rules engine and the same ledger as the rest of the platform.

AI Decisioning, Qurable's decision engine: it combines the member's profile, the purchase context and each campaign's rules, and chooses the best benefit in about 150 ms, without going over budget. You build the campaigns yourself or AI builds them from a prompt, and nothing goes live without your approval.

When the member pays by card, Qurable evaluates the purchase in the authorization and credits cashback under the campaign: the bank can fund it or co-fund it with the merchant, and the member then earns the bank program’s points. It’s in production with Pomelo, Santander Peru, Banisi and Konfío.

Yes, via API with signed webhooks; Napse (TOTVS) is already live with clients. At the POS, members identify with a QR that changes every 30 seconds or with an Apple Wallet or Google Wallet pass.

The sale is never blocked: the payment closes anyway and points are credited once service is restored. Redeeming points does require a connection.

Yes. Points are held at authorization, confirmed at capture and returned if the payment is canceled. In Qurable’s web and app checkout and in connected ecommerce, they can also be combined with another method in the same purchase.

Yes. With an issuer like Pomelo, points or cashback are credited in your own program, or Qurable calculates the reward and sends it to a partner brand’s program, for example a frequent flyer program.

It’s already live with clients with Pomelo, MODO, Mercado Pago and Stripe, and with the ecommerce platforms VTEX, Shopify and Tiendanube. Other processors and POS systems connect via API.

Every transaction is recorded on a double-entry ledger. A return reverses the reward and the points from that purchase, with a trail of what was applied and why.

Every transaction is recorded on a hash-chained, double-entry ledger with automatic reconciliation audits. It’s exported daily to your data warehouse to reconcile against your core, and liability is visible in real time. In co-funded campaigns, the ledger records and computes the bank’s contribution, the merchant’s contribution and the points issued; your team then posts the accounting entry and runs the clearing for each campaign from Qurable Manager.

Updated

How we start

With your POS, your card or your checkout.

We start with one payment touchpoint: a store, a channel or a card. The pilot goes live in 1 to 3 months; full integration depends on how many payment touchpoints you connect.

  1. A call with your teamWe map your payment touchpoints, your payment methods and your members.
  2. IntegrationWe connect your POS, your processor or your checkout via API.
  3. A measured launchWe start in one store, channel or card and measure against a control group.