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](https://ankasum.com/contact/form/) [See how it works](https://ankasum.com/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 Offers / **Spring checking bonus** SCSample Credit Union ### Spring checking bonus Version 3, edited by Jordan Alvarez In review Plain-English readback Members who open a new checking account between March 1 and May 31, 2027 earn $300 if they receive direct deposits totaling $2,000 or more within 90 days of opening. One bonus per member. Paid as an account credit within 30 days of qualifying. Recovered if the account closes within 180 days. Reward $300 Budget $450,000Enrollment closes at 1,500 Worst-case payout $450,000Within budget #### 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** | Topic | Today | With Ankasum | |----|----|----| | Where the offer lives | Tickets, a spreadsheet, a PDF | One versioned offer definition | | Who qualified | A hand-written query | Worked out from the same definition, every day | | Disclosure | Drafted separately | Built from your approved clauses and the same definition | | Before payout | Spot checks, if any | Every payout recomputed by an independent check | | Evidence | Pieced together when asked | Recorded 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. [Marketing](#marketing) [Compliance](#compliance) [Operations](#operations) 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. New offer / **Choose a template** Checking: direct deposit Balance goal Debit card spend Pay $300 when a new member receives $2,000 in direct deposits within 90 days of opening. Would have qualified last spring 1,184 Worst-case cost $450,000 Readback ready, 0 gapsSend for approval 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. Spring checking bonus / **Disclosure and rules** | Disclosure says | Payout rule | Match | |----|----|----| | $2,000 in direct deposits within 90 days | Direct deposits ≥ $2,000, days 0 to 90 | | | One bonus per member | Limit 1 per member | | | Offer may end when funds run out | Enrollment closes at 1,500 | | Evidence pack, version 3Signed - Approval recordApr 2 - Readback and test reportApr 2 - Daily run records42 runs Every action loggedExport for examiner 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. Daily run / **April 14, 2027**Complete - Accounts file6:02 AM - Transactions file6:05 AM - Enrollments file, 3 records set aside6:06 AM Qualified today 412 To credit $123,600 Held for review 2 Owed to date$1,086,300 Paid to date$1,086,300 Difference$0 **Fulfilment file ready**\ 412 credits for your core to postDownload Illustrative, sample data. [More on how each team works in Ankasum](https://ankasum.com/who-its-for/) ## 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](https://ankasum.com/how-it-works/) ## Built to stand up to an exam. Your members' data, your decisions, and rules you can explain line by line. [Security and data custody](https://ankasum.com/security/) [How reward integrity works](https://ankasum.com/reward-integrity/) - ### 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](https://ankasum.com/contact/form/) [Other ways to reach us](https://ankasum.com/contact/) - No customer data needed for the demo - We can sign your NDA first - Bring marketing, compliance and operations together --- Source: https://ankasum.com/ Updated: 2026-11-12