Ankasum
Contact us
Menu

Offer and reward software for banks and credit unions

Every offer, checked before it pays.

Write a bonus offer once. Ankasum reads it back in plain English, checks it for gaps, routes it for approval, finds who qualified in your daily files and writes the payout file your core posts. Evidence is recorded at every step.

Book a demo See how it works
  • The disclosure and the payout follow one approved definition
  • Your data stays in an environment dedicated to your institution
  • You post the payout file and stay payer of record

Pre-launch checks 1 to fix

  • Every term appears in the readback
  • Per-member limit and budget cap set
  • Deposit on day 90 counts; day 91 does not
  • Disclosure has no early-end clauseThe offer can end early when the budget runs out.

Approval 1 of 2

JAJordan AlvarezMarketing, makerSubmitted
RCRiya ChenCompliance, checkerReviewing

Illustrative screens with sample data.

Offers shouldn't live in tickets and spreadsheets.

A new checking bonus moves through weeks of tickets between marketing, analytics, IT and compliance. The disclosure is written in one place and the payout logic in another, and over time they drift apart.

  • Money paid to people who didn't qualify, and owed to people who did.
  • Complaints and UDAAP risk when the terms and the payout disagree.
  • No evidence pack when an examiner asks how a bonus was paid.
How offers run today compared with Ankasum
TopicTodayWith Ankasum
Where the offer livesTickets, a spreadsheet, a PDFOne versioned offer definition
Who qualifiedA hand-written queryWorked out from the same definition, every day
DisclosureDrafted separatelyBuilt from your approved clauses and the same definition
Before payoutSpot checks, if anyEvery payout recomputed by an independent check
EvidencePieced together when askedRecorded at every step, ready to export

One offer. Every team on the same page.

Marketing, compliance and operations each see the offer the way they need to, and all of them work from the same approved definition.

For marketing and product

Launch your next offer without the ticket queue.

Start from a template, fill in the terms in plain language, and see who would qualify and what it could cost before anyone else touches it.

  • Templates for the bonuses you run: direct deposit, balance and debit-card goals, fixed or tiered rewards.
  • A preview on your own data of who would qualify and the worst-case cost.
  • No analyst query to write. The same definition decides who gets paid.

Illustrative, sample data.

For compliance and risk

What the disclosure says is what gets paid.

The disclosure and the payout logic come from the same approved definition, so they cannot drift apart. When an examiner asks, the evidence is already there.

  • Gaps caught before launch: missing caps, ambiguous terms, unclear deadlines and the worst-case payout.
  • Maker-checker approval with sign-in from your own identity provider. Any change resets approval.
  • An evidence pack per offer: approvals, readback, test results and every daily run, signed and exportable.

Illustrative, sample data.

For operations

A clean fulfilment file, every morning.

Ankasum reads the daily files you already produce, works out who qualified, and writes a fulfilment file in the format your core posts. Nobody writes a query.

  • Bad records are set aside, not guessed at. A late file holds only the payouts that depend on it.
  • Every payout recomputed independently before it goes in the file.
  • Paid against owed, reconciled for every offer, so nothing slips through.

Illustrative, sample data.

More on how each team works in Ankasum

From term sheet to posted credit in four steps.

Each step records its evidence. If a check fails, the offer goes back to be fixed before it can move on.

  1. Define

    Build the offer from a template. Ankasum reads every term back in plain English.

  2. Check

    Find gaps before launch: missing limits, edge cases, ambiguous wording and the worst-case payout.

  3. Approve

    One person builds, another approves. The approved version is frozen and signed.

  4. Pay and record

    Each day, Ankasum finds who qualified and writes the file your core posts.

Ankasum never moves money. Your institution posts the fulfilment file and stays payer of record, and only a named person at your institution can refuse a reward. Each step in detail

Built to stand up to an exam.

Your members' data, your decisions, and rules you can explain line by line.

Security and data custody

How reward integrity works

  • Your data stays yours

    Each institution runs in its own isolated environment, a dedicated AWS account in its own country. Customer records never leave it.

  • Rules you can reproduce

    Eligibility and payouts are decided by deterministic rules. No language model decides who gets paid.

  • Tamper-evident records

    Every action goes into a hash-chained audit log. Approvals and payout files are signed with a key held for your institution.

  • People make the calls

    Ankasum releases or holds a payout under a policy you approved. Your staff decide every exception.

What Ankasum runs

Deposit and checking bonuses paid as cash credits, for US and Canadian banks and credit unions. For credit unions, it says member, not customer.

Direct deposit goalsBalance goalsDebit card purchasesFixed and tiered rewardsPer-member limitsBudgetsClawback

What it leaves to you

Ankasum doesn't contact your customers, make credit decisions or replace your anti-money-laundering monitoring. It fits alongside the systems you already run.

Your core posts payoutsYour team approves all wordingYour daily files, as they are

See one of your own offers in Ankasum.

Bring a bonus you run today. In a 30-minute demo we build it in Ankasum and show you the readback, the checks and the payout file it produces.

Book a demo Other ways to reach us
  • No customer data needed for the demo
  • We can sign your NDA first
  • Bring marketing, compliance and operations together