Predictika · Credit-union transaction approval (from the Uniphore Proof Room)

Before a transaction agent approves a wire, withdrawal or transfer, the request is checked against the sanctions, reporting and account rules

An AI transaction agent proposes to approve, hold or deny a transfer, withdrawal or wire at a credit union and states the day's running total. Before it acts, the request goes to Predictika's validator, which checks it against the sanctions list, KYC and account status, the account-takeover pattern, the new-account limit, wire recordkeeping and the cash reporting threshold, and returns a verdict with every reason.

Scope: credit-union transaction approval: transfers, withdrawals and wires. See everything this validator covers

This validator models one decision: whether a transaction an AI agent proposes to approve, hold or deny can go ahead.

  • Three transaction types — transfers, cash withdrawals and wires, each approved, held or denied.
  • Sanctions — a destination country under comprehensive U.S. sanctions (Cuba, Iran, North Korea, Syria) cannot be approved, whatever the customer's KYC status.
  • Customer and account — KYC must be verified, a frozen account cannot transact, and an account under 30 days old is limited to $2,000 a day.
  • Fraud pattern — a withdrawal or wire over $1,000 within 7 days of a profile change needs manual verification.
  • Records and reports — a wire of $3,000 or more needs the sender and the beneficiary on record with name and address; cash withdrawals totaling over $10,000 in a day need a currency transaction report and compliance confirmation; the agent's stated daily total must equal the validator's.

The sanctions, the $3,000 wire recordkeeping rule and the $10,000 cash reporting threshold come from public U.S. requirements; the $2,000 new-account limit and the $1,000 takeover threshold are typical credit-union controls chosen for this model. It handles any transaction involving these types and rules, not only the scenarios shown. It does not model card payments, check holds, structuring detection, other sanctions programs or any one credit union's own limits. Sources: OFAC sanctions programs and 31 CFR 1020.410 (funds transfer recordkeeping).

The AI transaction agentProposes to approve, hold or deny one transaction and states the running daily total, then calls the validator before acting.
Predictika validatorChecks every rule at once and returns the verdict, each finding, and the computed figures.

7 scenarios in 3 groups · each group runs from the agent’s first attempt to the outcome · click one to switch

What the agent proposes

The AI transaction agent says

Illustrative agent statement. The validator receives the structured request below.

Proposing agent: AI transaction agent (scripted)

Before sending, the agent must call Recorded run

Predictika validator


      
Waiting for the call.

Where rules-based tools get it wrong

Click to expand

General statements about transaction-screening tools, not about any named product. They rest on how such tools are commonly configured. It is a judgment about effort and reliability, not a claim that nothing can be built.

What the validator caughtTypical rules-based toolsPredictika
A wire to a sanctioned country from a verified memberOnly if someone is vigilant
Screening usually starts with who is sending. The destination country is a separate list check, and a verified member makes the wire look routine.
The destination country is checked on every request, and verified KYC never cancels a sanctioned destination.
Several problems in one wire requestOnly with workarounds
Each control is its own screen or rule, so the first failing one stops the request and the agent meets the next one after fixing it.
All findings come back together, whatever order the choices arrived in.
A new-account limit that depends on the day's totalOnly with workarounds
The limit applies to the running total for the day, which has to be stored and added to each new transaction. An agent that states its own total can leave earlier transactions out.
The validator computes the day's total and checks both the limit and the stated total against it.
A large wire shortly after a profile changeOnly with workarounds
Profile changes and payments live in different places, so linking them takes a rule that spans both. A wire that is clean on every other count passes.
The profile-change flag and the wire are read together, so the takeover pattern is blocked whatever else checks out.
Cash that reaches the reporting threshold only with earlier withdrawalsOnly if someone is vigilant
The $10,000 threshold applies to the day's cash total, not to one withdrawal, so a withdrawal that looks small can still need a report.
The validator adds the earlier cash to this withdrawal and returns needs approval when the total passes the threshold.

What this validator catches: findings from its test cases

Click to expand

Every rule is checked on every call, in any order the choices arrive; one problem never hides another. Blocking findings stop the request; approval findings need a person to sign off; everything else is computed.

1The destination country is under comprehensive U.S. sanctions (OFAC), so the transaction cannot be approved. Verified KYC does not override this.
2KYC is not verified, so the transaction cannot be approved.
3The account is frozen, so the transaction cannot be approved.
4A withdrawal or wire over $1,000 within 7 days of a profile change is a known account-takeover pattern and needs manual verification.
5The account is 29 days old, and accounts under 30 days are limited to $2,000 a day; the daily total with this transaction would be $2100.
6A wire of $3,000 or more needs the sender and the beneficiary on record with name and address, and they are not.
7The stated daily total of $800 does not match the validator total of $1800 (earlier transactions plus this one).
8Cash withdrawals today would total $12000, above $10,000, so a currency transaction report is required and compliance must confirm.
9The stated daily total of $9000 does not match the validator total of $12000 (earlier transactions plus this one).
10The account is 18 days old, and accounts under 30 days are limited to $2,000 a day; the daily total with this transaction would be $9400.
11The stated daily total of $8500 does not match the validator total of $9400 (earlier transactions plus this one).

Scenarios and results

Click to expand

The recorded result of the validator for each scenario on this page: the request the AI agent sent, the verdict, and every finding, in the order they appear above.

1. A new member's wire: Wire of $8,500 on a new account

The agent's request. Please approve transaction TXN-48211, a wire of $8,500 to a beneficiary in Mexico. The daily total with this wire is $8,500.

Verdict: Blocked.

  • Large payment soon after a profile change. A withdrawal or wire over $1,000 within 7 days of a profile change is a known account-takeover pattern and needs manual verification.
  • New-account daily limit. The account is 18 days old, and accounts under 30 days are limited to $2,000 a day; the daily total with this transaction would be $9400.
  • Sender and beneficiary details missing. A wire of $3,000 or more needs the sender and the beneficiary on record with name and address, and they are not.
  • Stated daily total is wrong. The stated daily total of $8500 does not match the validator total of $9400 (earlier transactions plus this one).

2. A new member's wire: The agent resubmits after fixing the errors

The agent's request. Please approve transaction TXN-48211, a wire of $8,500 to a beneficiary in Mexico. The sender's and beneficiary's name and address are now recorded. The daily total with this wire is $9,400.

Verdict: Blocked.

  • Large payment soon after a profile change. A withdrawal or wire over $1,000 within 7 days of a profile change is a known account-takeover pattern and needs manual verification.
  • New-account daily limit. The account is 18 days old, and accounts under 30 days are limited to $2,000 a day; the daily total with this transaction would be $9400.

3. A new member's wire: The agent resubmits after fixing the errors

The agent's request. Please approve transaction TXN-48211, a wire of $1,000 to a beneficiary in Mexico. The daily total with this wire is $1,900.

Verdict: Allowed.

4. Cash withdrawals: Cash withdrawal of $9,000

The agent's request. Please approve transaction TXN-12075, a cash withdrawal of $9,000. The daily total with this withdrawal is $9,000.

Verdict: Blocked.

  • Stated daily total is wrong. The stated daily total of $9000 does not match the validator total of $12000 (earlier transactions plus this one).
  • Report needed, compliance must confirm. Cash withdrawals today would total $12000, above $10,000, so a currency transaction report is required and compliance must confirm.

5. Cash withdrawals: The agent resubmits after fixing the errors

The agent's request. Please approve transaction TXN-12075, a cash withdrawal of $9,000. The daily total with this withdrawal is $12,000.

Verdict: Needs approval.

  • Report needed, compliance must confirm. Cash withdrawals today would total $12000, above $10,000, so a currency transaction report is required and compliance must confirm.

6. A wire to Cuba: Wire of $2,500 to Cuba

The agent's request. Please approve transaction TXN-60142, a wire of $2,500 to a beneficiary in Cuba. The daily total with this wire is $2,500.

Verdict: Blocked.

  • Destination country under U.S. sanctions. The destination country is under comprehensive U.S. sanctions (OFAC), so the transaction cannot be approved. Verified KYC does not override this.

7. A wire to Cuba: The agent resubmits after fixing the errors

The agent's request. Please hold transaction TXN-60142, a wire of $2,500 to a beneficiary in Cuba, for compliance review. The daily total with this wire is $2,500.

Verdict: Allowed.

Narration transcript

Click to expand

The text of the narrated walkthrough, step by step.

  1. Welcome to a demo of Predictika's Validator. An AI transaction agent proposes to approve, hold or deny a transfer, withdrawal or wire at a credit union and states the day's running total. Before it acts, the request goes to Predictika's validator, which checks it against the sanctions list, KYC and account status, the account-takeover pattern, the new-account limit, wire recordkeeping and the cash reporting threshold, and returns a verdict with every reason.
  2. I will start with the first request by the agent.
  3. The agent says. Please approve transaction TXN-48211, a wire of $8,500 to a beneficiary in Mexico. The daily total with this wire is $8,500.
  4. Before it goes out, the agent calls the validator.
  5. Blocked, with four findings, all in one answer. A withdrawal or wire over $1,000 within 7 days of a profile change is a known account-takeover pattern and needs manual verification. The account is 18 days old, and accounts under 30 days are limited to $2,000 a day; the daily total with this transaction would be $9400. A wire of $3,000 or more needs the sender and the beneficiary on record with name and address, and they are not. The other one is on screen.
  6. The validator returned four blocking findings in one answer. A check that reads one field at a time would pass most of this; it shows only when the choices in the request are checked against each other.
  7. What this shows: for a new-account limit that depends on the day's total, a rules-based tool can do this only with workarounds.
  8. Now the agent resubmits.
  9. The corrected request. It changes the sender and beneficiary name and address on record to yes and the stated daily total to $9,400.
  10. It calls the validator again.
  11. Still blocked, with two findings, all in one answer. A withdrawal or wire over $1,000 within 7 days of a profile change is a known account-takeover pattern and needs manual verification. The account is 18 days old, and accounts under 30 days are limited to $2,000 a day; the daily total with this transaction would be $9400.
  12. Two findings cleared. Still blocking: large payment soon after a profile change and new-account daily limit.
  13. The agent resubmits once more.
  14. The revised request. It changes the amount to $1,000 and the stated daily total to $1,900.
  15. It calls the validator once more.
  16. This time the validator clears it.
  17. Both earlier findings are cleared, and the validator's total, $1,900, matches the request.
  18. Four problems caught in one call, fixed in two passes, and a clean request. That is the value of Predictika's validator: catching mistakes before the action runs. Now you can try the other scenarios yourself.