Backoffice Banking 8.1
August 28th, 2026
This release gives you more control over how quotes move to contracts, with the ability to configure the setDecisionBindableOffer API directly from Product Admin without custom workarounds. You can also now identify the main customer when evaluating bindable offers with multiple participants, ensuring offers are processed with the correct customer context.
What's New
Bindable Offer API Configuration
You can now configure the setDecisionBindableOffer API directly from Product Admin, giving you more control over how quotes transition to contracts when your core system is external.
Why this matters:
If you manage products outside FintechOS or use an external servicing system, you no longer need custom workarounds to finalize quotes and generate contracts. This streamlines your end-to-end offer-to-contract flow for both banking and insurance.
What's new:
-
New Product Admin attributes: serviceBSC, generateContractRoute, and adminIsExternal (Servicing system is external);
-
Banking products use the new configuration in Contract Settings;
-
The API extracts current functions as routes and updates the existing PAC based on product type.
Identify Main Customer in Offers
When you call the Get Bindable Offers Evaluation API with multiple participants, you can now flag which one is the main customer of the offer.
What changed:
-
A new
mainCustomerfield is available on each offer participant in the request body -
If you include only one participant, the field is optional
-
If you include more than one participant, at least one must have
mainCustomerset to true -
Only one participant can be marked as the main customer; setting more than one returns a validation error
-
The payment frequency from your request is now captured and stored at the offer product level
Why this matters:
When evaluating bindable offers with multiple participants, there was no way to distinguish who the primary customer is. This update lets you clearly identify the main customer, ensuring offers are evaluated and stored with the correct customer context.