Skip to content

Bank card promotions, decided at the point of payment and settled automatically

Banks and fintech · Card promotions

Every bank promotion ends in a reward to the customer. Qurable is the promotion and cashback engine between the bank's core and every network: the team sets up each campaign once, cashback is decided inside the payment and credited instantly or whenever the bank decides, the ledger records who funds what, and each merchant's share is collected and reconciled automatically. Qurable Autopilot proposes, simulates, and measures; the bank approves.

Updated · 13 min read

See what changes

In production

The same engine that already decides rewards inside the payment across the region: 18M users on the platform, 13M active, and ISO 27001 certification.

  • ~150 msTo decide cashback inside the payment
  • ~3,000Requests per second in production
  • 17.3MDaily decisions in production
  • 600+Merchants integrated

Key takeaways

  1. Efficient: one setup, decided inside the payment and reconciled daily, with the merchant's share collected automatically.
  2. Personalized: rate and cap by income, tier, and behavior; when a payment qualifies for several promotions, the best cashback for the customer wins.
  3. Co-funded: bank, merchant, brand, or third parties fund their share under clear rules that Qurable Autopilot fine-tunes.

What changes

Faster, simpler, and with less manual work.

What a team now splits across processor forms, emails to merchants, IT requests, and reconciliation spreadsheets moves into a single flow. The team defines and approves; the platform and the agents do the rest.

How bank card promotion management changes with Qurable
TodayWith Qurable
Campaign setupOne setup per processor, wallet, and channelOne setup, published to every network
Cashback by income and tierOne campaign for each combinationOne setup generates every variant
Merchant co-fundingEmails, sign-up forms, and spreadsheetsClear funding rules; the merchant proposes and the bank approves
AudiencesAn IT request and a list per campaignReusable segments built by the commercial team
Collecting the merchant's shareCalculated and chased by hand, merchant by merchantAutomatic weekly close, by account debit or direct debit
ReconciliationSpreadsheets, days or weeks laterDaily, with every difference and its source
OptimizationManual analysis when the campaign endsQurable Autopilot proposes, simulates, and measures

An example

From checkout to collection: a co-funded grocery Tuesday.

A bank, a participating grocery store, and a Tuesday campaign they co-fund. The cardholder gets rewarded before putting the card away, and the store's share is collected at the weekly close.

Lucía: pays $80 at the supermarket with her bank card

No activation and no coupon: the card identifies her.

Qurable receives the purchase from the processor, inside the authorization

LLucía$80 · card0 msAuthorization · supermarketPurchase$80CardBank · debit
01 / 05

Illustrative case and values.

Merchant collection

How is each merchant's share collected?

Each reward can have several funders. Qurable builds the close by merchant and campaign, net of refunds, and tracks every collection until the money reaches the bank. The bank always executes the collection.

  • Merchant with an account at the bank

    Account debit: Qurable sends the settlement instruction by merchant and campaign, and the bank executes it.

    Result
    Collected at the weekly close.
  • Merchant at another bank

    A direct debit request against the merchant's account, in favor of the bank's collection account (DEBIN in Argentina); recurring direct debits don't depend on approving each request.

    Result
    Retried if rejected or expired.
  • Government and other third parties

    Record and report: the share is calculated and recorded per campaign, without executing a collection, and shown on the dashboards.

    Result
    Visible by campaign and funder.

Six components

Five modules and Autopilot, on one engine and one ledger.

Qurable sits as the promotion and cashback engine between the bank's core and every network. Each module goes live on its own, with Qurable Autopilot at the center. The bank keeps the account, the money, and the final say.

  • 01 · Campaign management

    One back office for cashback, installments, and merchant proposals, with role-based approval (no one approves what they set up), terms generated from the parameters, and simulation before launch.

  • 02 · Installments, processors, and publishing

    Each campaign splits into sub-campaigns by card brand, acquirer, and rate; every network gets setups and removals in its own format, and the app, website, and wallets show them through an API. Reference acquirers in Argentina: Payway and Fiserv; publishing to wallets such as MODO.

  • 03 · Real-time engine

    Evaluates every transaction against live campaigns, picks the best reward in ~150 ms, and records why. A retry never pays twice.

  • 04 · Ledger, settlement, and contribution recovery

    An accounting ledger, not a reward counter: every contribution has its own account, and the balance closes when the core confirms. A weekly close by merchant, collected by account debit or direct debit. Cashback, points, miles, discounts, and coupons follow the same logic.

  • 05 · Reconciliation, reversals, and control

    Calculated against credited and collected, every day. Refunds reverse proportionally, and backdated corrections go through a governed reprocess. Dashboards, alerts, a merchant portal, and export to the data lake.

  • 06 · Qurable Autopilot

    AI agents that analyze, propose, simulate, run what's approved, measure, and recommend. They run the promotion grid end to end; no rule runs without the bank's approval.

What you configure

What you configure in each campaign.

Everything that defines a bank card promotion, in one form that validates its fields before it goes to approval.

SettingWhat it lets you do
Percentage or fixed amountCashback to the account or a statement credit, with per-customer caps and a budget.
Crediting timeInstantly (~150 ms) or days later, at the weekly close or on the statement, per the bank's rules.
Reward destinationMoney in the account, a statement credit, program points, or miles; each instrument with its own account, conversion rate, and expiration.
Payment methodsCard, QR, or NFC, including NFC-only or QR-only options.
Days, hours, and validityFor example, grocery Tuesdays from 8 a.m. to 8 p.m.
BIN groupsCard, brand, credit, or debit, saved once and reused.
Lists by file or APINew customers, payroll customers, or a partner's base.
Dynamic audiencesIncome, tier, and other bank attributes, checked online with every payment.
Suggested by AutopilotSegments based on spending behavior, with a control group to measure them.
ScopeBy merchant category code (MCC), merchant, location, or terminal, and by acquirer.
FundersBank, merchant, and third parties in the same transaction; shares always add up to 100%.
Role-based flowSetup, approval, and publishing by different users, with the bank's single sign-on.
Automatic termsIf no terms are uploaded, they're generated from the parameters using the base text approved by Legal.
VersioningEvery change creates a new version; what's already processed only changes through an approved reprocessing.
Best rewardWhen a payment qualifies for several campaigns, priority, stacking, and the highest reward decide, with a record of why.

Qurable Autopilot

The bank sets the goal; Autopilot runs the promotions.

Every promotion multiplies by income, tier, merchant, and payment method, and a large bank can run 100,000 promotion combinations a year. The agents run that matrix end to end: they propose, simulate, and measure against a control group. The team sets the goal and approves; only approved rules run on transactions.

  • 01

    Analyzes

    What drives spend, in which segments, merchants, and payment methods.

  • 02

    Proposes

    Who gets which reward, with what cap, at which merchants, guided by business metrics.

  • 03

    Simulates

    Reach, cost, and each party's share against real transactions, before launch.

  • 04

    Runs what's approved

    In the engine, in real time. Every proposal goes through the bank's approval flow and is audited.

  • 05

    Measures

    Incremental sales against a control group, by campaign, segment, and funder.

  • 06

    Recommends

    Where more budget would pay off and what to cut, for the next approval.

For every team

What every team at the bank gets.

One flow for every promotion, from setup to collection, with a record of every decision.

  • Payments and marketing

    One setup for every rail, campaigns by customer and not just by BIN, and results in real time.

  • Operations and finance

    Merchant shares collected through one flow, daily reconciliation, and every claim answered with the decision record.

  • Merchants and brands

    They propose offers from their portal, with estimated reach and cost, and see every rewarded sale and every collection.

  • Cardholders

    The reward at the moment of payment, with a notification, the same with a card, QR, or NFC.

The platform

Built on the Qurable platform.

The offering combines modules of the same platform that runs energy, restaurant, and airline programs across the region, with Qurable Autopilot as the layer that operates them. It rolls out in three stages: in-payment cashback, installments and publishing, and Autopilot.

  • Promotion engine

    Campaigns, rules, caps, role-based approval, and publishing to every network.

    See the promotion engine
  • Cashback in the payment

    The reward decided inside the authorization, in ~150 ms.

    See cashback
  • Ledger and wallets

    Contributions by party and accounts by instrument, in immutable entries.

    See the ledger
  • Customer data

    Profiles and audiences ready at payment: BINs, lists, and bank attributes.

    See customer data
  • Settlement and reconciliation

    Collecting each merchant's share and reconciling daily.

    See settlement
  • Qurable Autopilot

    An expert agent per module that proposes, simulates, and measures, with the bank's approval.

    See Qurable Autopilot

FAQ

What banks ask about their card promotions.

Processors, money flows, merchants, refunds, AI, and implementation.

It's the flow from setting up a promotion to having the money in the right place: set up the campaign once, publish it to every network, decide the reward at payment, credit it, collect each merchant's share, and reconcile. Qurable brings it together in one engine and one ledger, run with AI agents.

Because neobanks arrive with rewards, tiers, and in-app perks that improve with use. Revolut already operates as a bank in Mexico, has a license in Colombia, received Argentina's central bank approval to acquire Banco Cetelem with a launch planned for 2027, and has applied for a license in Peru. The question is no longer whether to add rewards, but how to keep customers with what the bank already has.

No. Campaigns the processor settles today can stay there: Qurable sets them up once, approves them, and publishes them to each acquirer. Campaigns that need to be decided by customer, income, or tier move to Qurable's engine, and cardholders get rewarded in seconds.

It depends on the campaign, and both models run on the same platform. At the processor, Qurable sets up, approves, and publishes, and the customer gets paid on the statement: ideal for installments. In the Qurable engine, everything runs through settlement and reconciliation, and the customer gets paid instantly or when the bank decides.

No. Crediting time is a business rule: as fast as ~150 ms or days later, at the weekly close or on the statement. The reward is decided and recorded in the payment, even if it is credited later.

Yes. If the bank or neobank runs a loyalty program, the same promotion can return money in the account, a statement credit, points, or miles. Each instrument has its own account, conversion rate, and expiration in the ledger.

Always the bank. Qurable doesn't replace the core, process payments, or move money: it calculates, records, and triggers. The core credits the cardholder, and the bank collects each merchant's share.

At every close, Qurable builds the settlement by merchant and campaign, net of refunds. Merchants with an account at the bank are debited; merchants at other banks are charged by direct debit. Each collection has one ID tying together what was calculated, requested, and paid.

The refund is linked to the original transaction. A pending reward is canceled; a credited one is debited back. Partial refunds reverse proportionally, and if the merchant's share was already collected, it's offset at their next close.

Yes. The team sets the base value, and the system builds every variant by income and tier with a single approval. On each payment, the engine checks those attributes through the bank's API and applies the matching variant.

No. Qurable Autopilot analyzes, proposes, simulates, and measures; every proposal goes through the bank's approval flow and is audited. Only rules the bank approved run on transactions.

Through services and files with the core, processors, acquirers, collections, and channels, without touching the authorization flow or the flow of funds. It runs in the bank's cloud (AWS or GCP) or in Qurable's, with ISO 27001 certification. Qurable doesn't store full card numbers: it works with identifiers and tokens the bank provides, which limits PCI scope.

The pilot goes live in 1 to 3 months, depending on the integrations the bank enables. Banks usually start with real-time cashback and then add installments, publishing, and Qurable Autopilot on the same engine.

Last reviewed

Further reading

Cashback, audiences, installments, calculation models, agents, and settlement.

How many promotions does your bank run today?

In a short meeting, we'll review your campaigns and rails, and where it makes sense to start.

Read the documentation