Before you start
Make sure you have access to the Fiskil Console with appropriate permissions for Product Portal.
Access control is determined by a user’s role in the Team Settings / Members menu.
All product changes follow a controlled workflow: create or edit in Staging, review and approve, then publish to Production.
Some actions, like publishing changes to Production immediately, are available only to team owners.
Product lifecycle overview
Every product in Product Portal follows a consistent lifecycle:Create or edit
Add a new product or make changes to an existing one. All changes start in draft mode.
Review and validate
Review your changes in the Console. Validation errors are shown inline before you can proceed.
Deploy to Staging
During review, your changes are deployed to Staging environment. Verify the product data through the corresponding Staging API endpoint.
Creating a new product
Navigate to Product Portal
In the Fiskil Console, go to Product Portal from the main navigation.
Complete required fields
Fill in the mandatory product details:
| Field | Description |
|---|---|
| Product name | Product display name shown to customers, e.g. Credit Loan |
| Product category | Category from the regulated specification |
| Description | Short public description of the product |
| Brand name | Institution brand managing the product, typically official Bank name |
See the Products API reference for a complete list of all available fields.
Add optional details
Expand additional sections to configure:
- Features — capabilities like digital banking, offset accounts
- Eligibility — who can apply for the product
- Constraints — application constraints such as minimum balances or limit thresholds
- Fees — charges and optional discounts
- Rates — deposit or lending rates with tiers
- Bundles — group products together
Editing an existing product
Find the product
Use the search or filter options in Product Portal to locate the product you want to edit.
Testing in Staging
Before publishing to production, you should validate your changes in Staging. Upon change request creation, the draft version is deployed to Staging API. Use the built-in Test API feature to verify your product appears correctly:- Click Test API in the top-right corner of Product Portal
- Select Staging as the environment
- Click Send Request to view your products
Approving and publishing to Production
Once your product is validated in Staging, you can publish it to Production.Approve changes
An authorised approver reviews and approves the changes.
Approval workflows are configurable. Contact the Fiskil team to set up approval rules for your organisation.
Scheduling product updates
Product Portal supports scheduling changes to go live at a future date and time.Set effective date
When deploying, select Scheduled time and choose the date and time for the changes to take effect.
Confirm schedule
The Product Portal homepage shows overview of scheduled deployments. You can cancel or modify the schedule before it executes.
Scheduled changes are applied automatically at the specified time. No manual action is required once scheduled.
For team owners, it is possible to bypass scheduled time selection and apply approved changes immediately with
Approve and Apply button on review page.Discontinuing products
When a product is discontinued or no longer offered, first you need to update the Effective To date to indicate when the product is no longer available for new applications. Once ensured the new Effective To date is live in Production, go to Product Portal and select Delete from the Actions column to delete product from active listings immediately. All deleted products are retained by Fiskil for historical reference.Best practices
Test in Staging first
Always verify products in Staging before publishing changes to Production.
Review before publishing
Use the diff view to confirm changes before publishing to Production.
Document changes
Add notes when editing products to maintain a clear audit trail.
Validation rules
Product Portal validates your data against the regulated specification. Common validation errors include:| Error | Cause | Solution |
|---|---|---|
| Missing required field | A mandatory field is empty | Complete all required fields |
| Invalid enum value | Value not in allowed list | Select from the dropdown options |
| Invalid URI format | URL is malformed | Ensure URLs start with https:// |
| Conditional field required | A dependent field is missing | See the field’s conditional rules |