Skip to content

Bank card promotions at the issuer processor or in a promotion engine? How to choose the calculation model

Resources · Guide

A bank can calculate its card promotions at the issuer processor, which settles them on the statement, or in a promotion engine that decides the reward inside the payment, per customer, and credits it when the bank decides. It isn't an either-or choice: installments usually stay at the processor, and personalized cashback moves to the engine.

Updated · 4 min read

See the comparison

Key takeaways

  1. At the processor: rules by BIN and merchant, and the customer gets paid on the statement. Ideal for installments.
  2. In the engine: rules by customer, income, and tier, cashback instantly or when the bank decides, and the merchant's share settled and reconciled.
  3. Both models can run side by side on the same platform, campaign by campaign.

Two models

How do the processor and the engine differ?

The processor calculates by BIN and merchant at settlement; the engine decides per customer inside the payment and carries everything through settlement and reconciliation. Both run on the same platform.

Promotions calculated at the issuer processor compared with a promotion engine
At the issuer processorIn a promotion engine
Where it's calculatedAt the issuer processor, at settlementIn the engine, inside the authorization, in ~150 ms
When the customer gets paidOn the statementInstantly or when the bank decides
PersonalizationBy BIN, card brand, and merchantBy customer, income, tier, and behavior
Overlapping promotionsPer the processor's rulesThe best reward wins, with an audit trail
Merchant contributionCalculated and collected separatelyRecorded per transaction in the ledger and collected at the close
ReconciliationAgainst the processor's fileDaily: calculated against credited and collected
Best forInterest-free installments and mass discountsPersonalized, co-funded cashback

How to choose

What to look at to choose the model.

The question isn't which one, but which campaigns go to each. Four questions frame the decision.

  • When does the customer need to get paid?

    If the statement is enough, the processor. If they need to see it right away or on a date of the bank's choosing, the engine.

  • Does the reward vary by customer?

    By BIN and merchant, the processor. By income, tier, or behavior, the engine.

  • Do merchants fund a share?

    If the merchant pays its share, the engine records it per transaction and collects it at the close.

  • What does reconciliation cost?

    If reconciliation is manual today, the engine runs it daily, with every difference and its source.

With Qurable

Both models, on the same platform.

Qurable sets up, approves, and publishes the campaigns that stay at the processor, and decides in the payment the ones that move to the engine. The bank chooses campaign by campaign.

FAQ

What banks ask about calculation models.

Processors, integration, and running both.

It is the company that processes cards on the bank's behalf: it authorizes transactions, produces the statement, and, in many cases, settles promotions by BIN and merchant.

No. Campaigns the processor settles today can stay there: Qurable sets them up once, approves them, and publishes them. The ones that need per-customer, income, or tier decisions move to the engine.

The engine receives every transaction in real time from the processor (approved, declined, canceled, or refunded), decides the reward, and orchestrates the credit in the core. It doesn't touch authorization or the flow of funds.

Yes. That is the usual setup: installments at the processor and personalized cashback in the engine, in the same back office and with the same approval workflow.

Last reviewed

Go deeper

The offering, installments, and settlement.

Which of your bank's campaigns should move to the engine?

We review your campaigns and map which model each one belongs in.

Read the documentation