Opinion
Decided at payment and notified in seconds, the benefit changes the habit.

Banks already have the hard part: cards, a core banking system, processors, participating merchants, and a significant rewards budget. What’s usually missing is a single flow that takes each promotion from setup all the way to the money landing where it belongs. In this article, we walk through how that flow works and what changes when the benefit is decided at the moment of payment.
The starting point: a benefit that depends on the payment path
At most issuers, the benefit depends on the path the payment takes. The processor settles it weeks later, the wallet credits it instantly but only for its own payments, and the merchant’s contribution is collected through separate channels.
The result repeats at almost every bank:
- 30 to 60 days before a processor-settled rebate shows up, with no notice to the customer.
- 2 or more setups of the same campaign, across processors, wallets, and the bank’s own channels, each in its own format.
- Manual recovery of each merchant’s contribution, through separate flows and reconciled in spreadsheets.
- Campaigns tied to the BIN and the merchant category, with little room to reward by customer, income, tier, or behavior.
A rebate that arrives weeks later isn’t linked to the purchase. Decided at payment and notified in seconds, it changes the habit.
Where it fits: an engine between the core and each network
The approach is to add a promotion engine between the bank’s core and each network. It doesn’t replace the core, process payments, or move money: it receives each transaction, decides the benefit using the bank’s rules, and orchestrates what happens next.
- Source: credit and debit card purchases, QR and NFC (wallets, Apple Pay, Google Pay), transfers, direct debits, and bank events such as missions or tiers.
- Rules: segments, income and tier, merchant and category, days and times, caps, budget, priority, and best benefit.
- Ledger: the contribution from the bank, the merchant, and third parties on every transaction, with immutable, idempotent entries.
- Destination: the core credits the benefit; processors and acquirers receive installment campaigns; settlement or DEBIN collects the contribution; the app, the website, and wallets publish the promotion.
The sale follows its usual authorization and settlement flow. The benefit and the contributions travel through a separate flow, on the issuer side.
There are two calculation models, and they coexist on the same platform. In the first, the processor calculates using the conditions the bank sets up, and the customer gets paid on its timeline, usually on the statement. In the second, the engine calculates on each transaction in real time, and the customer can get paid in seconds into their savings account. The first works for the installment plans that processors settle today; the second, for online cashback, customer-level campaigns, and co-funded promotions.
Campaign management: set up once, every channel
The commercial team sets up each campaign once in a single back office: cashback, installments, audiences, legal terms, and channels in the same form. An incomplete campaign can’t reach approval, and every action is logged by user and version.
The flow has four stages. The person setting it up creates the campaign as a draft and simulates it against recent real transactions, to see how many it would have rewarded and how much budget it would have used. A validator reviews the parameters, the simulation, and the legal terms, and no one approves what they set up themselves. Once published, the campaign goes into the engine, appears in the channels, and, if it includes installments, is sent to the acquirers. Every change creates a new version with an effective date.
You can configure a percentage or fixed amount, credit to the savings account or the statement, payment methods (including NFC only or QR only), days, times, and caps. Audiences go beyond the BIN: lists by file or API, and attributes such as income and tier queried in real time. If no legal terms are entered, the system builds them from the parameters on top of the base text approved by the bank’s Legal team.
For installments, the campaign is split into sub-campaigns by card brand, acquirer, and rate group, and the enrollments and cancellations are generated in each acquirer’s format. Each network is an independent adapter: adding a new one doesn’t change the engine.
Real-time engine: the benefit, decided within the payment
The engine receives every approved, canceled, or refunded purchase and decides on the spot which campaign applies, how much is due, and how the cost is split. The calculation belongs to the engine; the bank always executes the credit.
Here’s an illustrative example. A “Grocery Tuesday” campaign offers 25% cashback capped at $10,000, co-funded 60/40 between the bank and the merchant:
- 13:02:00. Lucía pays $80,000 with her card at the supermarket.
- ~150 ms. It’s Tuesday, it’s a supermarket, and her tier applies: she gets 25%, capped at $10,000.
- Instantly. The bank puts in $6,000 and the supermarket $4,000, recorded in the ledger.
- Seconds. The cashback is credited to her account and she gets the notification while still at the register.
- Friday. The supermarket’s contribution is collected through account settlement or DEBIN.
Amounts, percentages, and caps are illustrative: each bank defines its own.
If a payment qualifies for several campaigns, it’s resolved by priority, stacking, and highest benefit, and there’s a trace of why one won. Each operation carries a unique key: a resend or a duplicate transaction never generates a second benefit. If the core doesn’t respond, the call is retried with increasing backoff, and anything that can’t be resolved goes to a queue with its reason.
In production, the platform decides the benefit in ~150 ms per transaction, sustains ~3,000 requests per second, and has handled 17.3 million decisions in a single peak day.
Settlement: co-funded promotions, without spreadsheets
Each benefit can have several contributors: the bank, the merchant, a brand, or a third party. The platform records who puts in how much on every transaction, builds the weekly close by merchant and campaign, net of reversals, and tracks each collection until the money reaches the bank.
Collection depends on the type of contributor:
- Merchant with an account at the bank. The settlement instruction is sent; the bank executes it and returns the result.
- Merchant at another bank. A DEBIN (an Argentine immediate debit request) is issued against its CBU account number, in favor of the bank’s collection account. With prior enrollment, collection doesn’t depend on the merchant accepting each request.
- Government and other third parties. The contribution is calculated and recorded by campaign, without executing the collection, and reported in the dashboards.
If a DEBIN is rejected or expires, it’s retried at the next close according to the bank’s policy. Once retries are exhausted, the case is escalated to the commercial team with the details.
On the other side, the merchant has its own portal. It proposes benefits from the templates the bank enables, tracks their approval, and sees each close: contribution calculated, collected, pending, and reversed. Nothing is published without the bank’s sign-off.
Reconciliation: calculated versus executed, every day
Settling well means being able to explain every dollar. The platform reconciles daily what it calculated against what the bank credited and collected, and discrepancies show up the same day, with the transaction that caused them.
A cancellation or refund is linked to the original transaction. If the benefit was pending, it’s voided; if it was already credited, a debit is generated; if the refund is partial, it’s reversed proportionally. Nothing is deleted: a reversal is a new entry that offsets the previous one.
When something needs to be corrected retroactively, reprocessing is explicit and governed. The new parameters are defined, simulated with no effects, approved with dual control, and only then are the adjustments executed, each with its own idempotency key.
On security, sensitive card data never leaves the bank: the platform works with tokens and with the attributes the bank chooses to share. It’s deployed as dedicated SaaS or in the bank’s cloud (AWS or GCP), with ISO 27001 certification.
How to get started: three stages, one engine
Implementation moves forward by module, and each one goes into production separately, in 1 to 3 months depending on the integrations the bank enables.
- Online cashback. Campaign setup and approval, income and tier, real-time engine, crediting, customer notification, reversals, and dashboards.
- Settlement and channels. Weekly contribution recovery, merchant portal, publishing in the app, website, and wallets, and retroactive reprocessing.
- Installments with acquirers. Rate table, sub-campaigns, sending enrollments and cancellations, and status tracking.
To measure the change, it’s worth tracking six indicators: time to credit, setups per campaign, contributions recovered without manual intervention, reconciliation discrepancies, share of the budget co-funded by third parties, and benefit-related complaints.
The underlying question is simple: do your promotions reward customers when they buy, or weeks later, when they’ve already forgotten?
Frequently asked questions
At most issuers, between 30 and 60 days when the processor settles it, with no notice. With in-house calculation in a promotion engine, cashback can be credited in seconds.
No. It doesn’t process payments or move money: it decides the benefit using the bank’s rules and orchestrates the credit, which the bank executes.
Through a weekly close by merchant and campaign. If the merchant has an account at the bank, it’s settled to that account; if it banks elsewhere, a DEBIN is issued against its CBU account.
No. The platform works with tokens and with the attributes the bank chooses to share.


