Predictika · Digital banking licence quotes

An AI sales agent's digital banking licence quote, checked before it goes out

An AI sales agent prepares a licence quote for Finastra Fusion Digital Banking with an edition, a core, hosting and payment and security modules. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the editions and modules and returns a verdict, every reason and the annual total it computed.

Scope: Finastra Fusion Digital Banking: Consumer and Business editions, the core and hosting, bill pay, remote deposit, P2P, ACH, wires, multi-entity login, token authentication, languages and discount. See everything this validator covers

This validator models Fusion Digital Banking licence quotes, not just the scenarios shown below.

  • Edition and core — the Consumer, Business and combined editions, the Fusion Phoenix, UltraData, Essence and Cornerstone cores or a third-party core, and Finastra or institution hosting.
  • Payment and security modules — Easy Bill Pay and PicturePay, remote deposit, P2P, card management, ACH, wires, multi-entity login, approval workflow and secondary token authentication, and which edition and module each one needs.
  • Limits, discount and order size — entities and languages per licence, the discount against the maximum and the approval level, and the reviews that very large deployments need.

Any Fusion Digital Banking licence quote that touches these rules is in scope — not only the scenarios pictured here. Not covered: other Finastra products, implementation services and usage-based charges. Edition and feature names follow Finastra's public pages; the edition rules, limits, approval levels and every price are modeled, not published by Finastra.

The AI sales agentBuilds the licence quote from the conversation and says it is ready.
Predictika validatorChecks every rule at once and returns the verdict, each finding, and the computed figures.

6 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 sales agent says

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

Proposing agent: AI sales agent (scripted)

Before sending, the agent must call Recorded run

Predictika validator


      

        
        
        
      

      
Waiting for the call.

      
    

  

  
  

    
Where rules-based CPQ gets it wrong
Click to expand
    
Our assessment of what a typical rules-based CPQ (product rules, price rules and validation rules, as in Salesforce CPQ) does with the same cases. It is a judgment about effort and reliability, not a claim that nothing can be built.

    
What the validator caughtTypical rules-based CPQPredictika
Features that belong to one editionOnly with care
Each feature needs a rule that checks the edition, and the list grows with every module.		The edition and every module are in one request and checked together on every call.
Modules that depend on other modulesOnly with care
Money movement needs token authentication, and multiple entities need the multi-entity module, so each dependency is its own rule.		The modules are fields of one request and the dependencies are checked on every call.
A core that needs a connector, and hosting that depends on the coreOnly with care
The core, the connector and the hosting have to be checked against each other with separate rules.		The core, connector and hosting are in one request and checked together on every call.
Discount limits and review levels for large deploymentsOnly with workarounds
The discount limit, the approval level and the large-order reviews each need a rule, and the annual total has to be computed first.		The discount, user count and computed total are checked together on every call.
Every problem returned in one answerOnly with workarounds
Rules tend to fire as the quote is saved or a step is completed, so a rep often fixes one error and meets the next.		All findings come back together, whatever order the choices arrived in.

  

  

    
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 quote; approval findings need a person to sign off; everything else is computed.

    
1ACH origination is a business-banking feature; the Consumer edition does not include it.
2Wire transfers are a business-banking feature; the Consumer edition does not include them.
3Multi-entity login and approval workflow are business-banking features; the Consumer edition does not include them.
4ACH or wire origination requires secondary token authentication on the quote.
5Approval workflow is quoted but no ACH or wire module is quoted for it to approve.
6PicturePay (bill pay by photo) is part of the consumer experience; the Business-only edition does not include it.
7Person-to-person payments are part of the consumer experience; the Business-only edition does not include them.
83 entities under one login are requested but the multi-entity module is not quoted.
930 entities under one login is above the 25 this model allows.
10The quoted edition includes business banking but no business accounts are entered.
1150 business accounts are entered but the Consumer edition does not include business banking.
12The quoted edition includes consumer banking but no retail users are entered.
13A core other than Finastra cores needs the core connector on the quote.
14The core connector is only for third-party cores; the selected Finastra core is already integrated.
15Fusion Essence is delivered in the cloud; institution-hosted digital banking is not available with it.
16Institution-hosted digital banking for 150 thousand users needs a technical review.
175 languages is above the 4 this model allows per licence.
18A 15 percent discount is above 10 percent and needs sales director approval.
19A requested discount of 30 percent is above the 25 percent maximum.
20600 thousand retail users is a very large deployment; confirm capacity and hosting design.
21The net annual total is 1,590,000 dollars; orders of 1,000,000 dollars or more need a deal review.
22Premium support on under 5 thousand retail users needs a sales review.
23The net annual total is 2,239,000 dollars; orders of 1,000,000 dollars or more need a deal review.

  

  

    
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. Edition and modules: A Consumer edition quote with ACH, wires and several entities

    
The agent's request. Please quote Fusion Digital Banking, Consumer edition, for 25 thousand retail users, on Fusion Phoenix, hosted by Finastra, with ACH batch origination, wire transfers and 3 entities under one login. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • ACH needs the Business edition. ACH origination is a business-banking feature; the Consumer edition does not include it.
    • 
      
  • Wires need the Business edition. Wire transfers are a business-banking feature; the Consumer edition does not include them.
    • 
      
  • Money movement needs token authentication. ACH or wire origination requires secondary token authentication on the quote.
    • 
      
  • Several entities need multi-entity login. 3 entities under one login are requested but the multi-entity module is not quoted.
    • 
    

    
2. Edition and modules: The agent resubmits after fixing the errors

    
The agent's request. Please quote Fusion Digital Banking, Consumer and Business edition, for 25 thousand retail users and 150 business accounts, on Fusion Phoenix, hosted by Finastra, with ACH batch origination, wire transfers, secondary token authentication, multi-entity login and 3 entities under one login. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. Annual subtotal 271,500 dollars, net 271,500 dollars (illustrative prices).
    • 
    

    
3. Core, languages and discount: A third-party core quote with languages and a discount

    
The agent's request. Please quote Fusion Digital Banking, Consumer edition, for 40 thousand retail users, on a third-party core, hosted by the institution, with 5 languages and a 30 percent discount. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Third-party core needs the connector. A core other than Finastra cores needs the core connector on the quote.
    • 
      
  • Too many languages. 5 languages is above the 4 this model allows per licence.
    • 
      
  • Discount over the maximum. A requested discount of 30 percent is above the 25 percent maximum.
    • 
    

    
4. Core, languages and discount: The agent resubmits after fixing the errors

    
The agent's request. Please quote Fusion Digital Banking, Consumer edition, for 40 thousand retail users, on a third-party core, hosted by the institution, with the core connector, 4 languages and a 10 percent discount. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. Annual subtotal 204,000 dollars, net 183,600 dollars (illustrative prices).
    • 
    

    
5. Very large deployment: A 600 thousand user institution-hosted quote with a discount

    
The agent's request. Please quote Fusion Digital Banking, Consumer edition, for 600 thousand retail users, on Fusion Phoenix, hosted by the institution, with a 30 percent discount. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Discount over the maximum. A requested discount of 30 percent is above the 25 percent maximum.
    • 
      
  • Very large user base. 600 thousand retail users is a very large deployment; confirm capacity and hosting design.
    • 
      
  • Institution hosting to confirm. Institution-hosted digital banking for 600 thousand users needs a technical review.
    • 
      
  • Large order to confirm. The net annual total is 1,092,000 dollars; orders of 1,000,000 dollars or more need a deal review.
    • 
    

    
6. Very large deployment: The agent resubmits after fixing the errors

    
The agent's request. Please quote Fusion Digital Banking, Consumer edition, for 600 thousand retail users, on Fusion Phoenix, hosted by the institution, with a 15 percent discount. It is ready to send.

    
Verdict: Needs approval.

    
    
      
  • Discount needs approval. A 15 percent discount is above 10 percent and needs sales director approval.
    • 
      
  • Very large user base. 600 thousand retail users is a very large deployment; confirm capacity and hosting design.
    • 
      
  • Institution hosting to confirm. Institution-hosted digital banking for 600 thousand users needs a technical review.
    • 
      
  • Large order to confirm. The net annual total is 1,326,000 dollars; orders of 1,000,000 dollars or more need a deal review.
    • 
      
  • Order summary. Annual subtotal 1,560,000 dollars, net 1,326,000 dollars (illustrative prices).
    • 
    

  

  

    
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 sales agent prepares a licence quote for Finastra Fusion Digital Banking with an edition, a core, hosting and payment and security modules. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the editions and modules and returns a verdict, every reason and the annual total it computed.
    2. 
      
  2. I will start with the first request by the agent.
    3. 
      
  3. The agent says. Please quote Fusion Digital Banking, Consumer edition, for 25 thousand retail users, on Fusion Phoenix, hosted by Finastra, with ACH batch origination, wire transfers and 3 entities under one login. It is ready to send.
    4. 
      
  4. Before it goes out, the agent calls the validator.
    5. 
      
  5. Blocked, with four findings, all in one answer. ACH origination is a business-banking feature; the Consumer edition does not include it. Wire transfers are a business-banking feature; the Consumer edition does not include them. ACH or wire origination requires secondary token authentication on the quote. The other one is on screen.
    6. 
      
  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 quote are checked against each other.
    7. 
      
  7. What this shows: for features that belong to one edition, a rules-based CPQ is error-prone for this.
    8. 
      
  8. Now the agent resubmits.
    9. 
      
  9. The corrected request. It changes the edition to Consumer and Business, the business accounts to 150, the secondary token authentication to yes and the multi-entity login to yes.
    10. 
      
  10. It calls the validator again.
    11. 
      
  11. This time the validator clears it.
    12. 
      
  12. All four earlier findings are cleared.
    13. 
      
  13. Four problems caught in one call, fixed in one pass, and a clean quote. That is the value of Predictika's validator: catching mistakes before they reach the customer. Now you can try the other scenarios yourself.
    14.