Getting access to Quantum

Quantum works integrated with SSO Azure AD. So to get access to Quantum, the user will use a corporate mail.

↑ Back to top

Request access to Quantum groups via Sailpoint

↑ Back to top

First Login – tenant association

↑ Back to top

First Login

↑ Back to top

Homepage

An overview of the Quantum homepage — the central monitoring screen for payment operators and managers to track current-day activity.

Step 1: Homepage Overview

The Homepage is the first screen you see when you log in to Quantum. Its purpose is to allow payment operators and managers to monitor current-day activity at a glance.

The homepage displays payments processed from midnight today to the current time. The date picker on this screen is not selectable — data is always for today only.

All values on the homepage are governed by the selected tenant (shown in the top-right corner) and the flow filter tabs.

Step 2: Payment Totals and Breakdown

At the top of the homepage, you can see the Total Payments count along with a split between:

• Emission — payments sent out

• Reception — payments received

Each shows the count and percentage. These numbers represent all payments processed during the current day.

Step 3: Flow Filters

Below the totals, you will find three filter tabs: All flows, Emission, and Reception.

Clicking on any of these tabs updates the entire screen — the status buckets, bar charts, and all other values adapt to show data for the selected flow only.

Step 4: Payment Status Buckets

The homepage displays four main status buckets representing the core processing states of a payment:

• In Flight — payments currently being processed (transitory state)

• Parked — payments that require attention or manual intervention (transitory state)

• Accepted — payments that have been successfully processed (final state)

• Rejected — payments that have been declined or failed (final state)

In Flight and Parked are transitory statuses — payments remain there temporarily before moving to a final state. Accepted and Rejected are the two main final statuses.

Step 5: Bar Charts and Breakdown

Each status bucket includes a bar chart that provides a breakdown by important attributes. For example, the Rejected bucket breaks down rejected payments into sub-categories such as Finalized vs. Sent to scheme.

These charts give you a quick visual understanding of the distribution within each status category.

Step 6: Interacting with Chart Elements

Every element on the homepage is clickable:

• Clicking on a status bucket (In Flight, Parked, Accepted, Rejected) navigates you to the Payment List pre-filtered by that status

• Clicking on a specific bar in a chart navigates to the Payment List filtered by that particular sub-status

Hovering over chart bars shows a tooltip with the exact count for that category.

Tip: Use the clickable elements to quickly drill down from the homepage overview into specific payment lists.

Step 7: Navigating to the Payment List

When you click on any clickable element (a status count, a bar, or a percentage), the system navigates you directly to the Payment List with the appropriate filters already applied.

For example, clicking on the "Finalized" bar in the Rejected chart takes you to a payment list showing only finalized rejected payments.

Quick Reference

↑ Back to top

Service Insights and Notifications

Monitor automated insights about your tenant's payment processing trends, and access notification alerts from the homepage.

Step 1: Service Insights Panel

On the right side of the homepage, you will find the Service Insights panel. This is a new feature that provides automated insights about your tenant’s payment processing trends.

These insights are triggered by alerts configured in the system and give you important information about changes in your payment activity. For example:

• "Payments volume has increased by 3% over the last month"

• "Total amount volume has increased by 8% over the last month"

• "Rejected payments volume has increased by 95% from yesterday"

Tip: Service Insights are generated automatically based on system-configured alert thresholds. They help you spot trends and anomalies without manual analysis.

Step 2: Reviewing Insight Details

Each insight card shows a summary of the trend including the metric name, the percentage change, and the comparison period (e.g., "over the last month" or "from yesterday").

The insights update automatically as new data is processed throughout the day, giving you a real-time view of how your payment processing compares to historical patterns.

Step 3: Notification Bell

Next to the Service Insights, you will find the notification bell icon in the top-right area of the homepage. Clicking on it opens a Notifications panel.

When there are new notifications, they will be displayed here. From this panel, you can access more details about each notification.

Tip: If the panel shows "There are no data to display", it means there are no pending notifications for your tenant at this time.

Quick Reference

↑ Back to top

Assigning Payments

Assign parked payments to yourself or team members for tracking and resolution, and monitor assignment activity.

Step 1: Assigned Payments on the Homepage

When you log in to the homepage, you will see an Assigned payments box on the right side. This shows:

• The total number of payments currently assigned to you

• A breakdown by parked status type (for example, "Accounting Exception")

Clicking on a specific status type (e.g., "Accounting Exception") takes you directly to the payment list filtered to show only those assigned payments.

Step 2: Viewing the Assign Column in the Payment List

In the Payment List, parked payments that are in the exception handler display an assignment column. This column shows:

• A grey icon — the payment is not assigned to anyone

• A dark blue bubble with initials — the payment is assigned to you

• A light blue bubble with initials — the payment is assigned to a colleague

Note: Not all parked payments can be assigned. Only payments in the exception handler show the assignment icon.

Step 3: Assigning a Payment to Yourself

To assign a payment to yourself, simply click the grey assignment icon on any unassigned payment in the list. The system immediately assigns the payment to the currently logged-in user.

After clicking, the icon changes to a dark blue bubble showing your initials, confirming the assignment.

Tip: You can assign or unassign a payment in one click directly from the payment list.

Step 4: Understanding Assignment States

Once payments are assigned, you can visually distinguish between different assignment states:

• Dark blue bubble with your initials — assigned to you

• Light blue bubble with another person’s initials — assigned to a colleague

• Grey icon (no initials) — unassigned

• No icon at all — the payment is parked but not in the exception handler and cannot be assigned

Step 5: Assignment Activity in Payment Details

When you open a payment’s detail view, you can see:

• The "Assigned to" label showing who the payment is currently assigned to

• In the User Activity section at the bottom, a log entry recording when the payment was assigned or unassigned

Every assign and unassign action is recorded in the user activity, providing a full audit trail of payment assignments.

Quick Reference

↑ Back to top

Payment List

Use the Payment List to monitor, filter, select, and export payments — the main operational tool within Quantum.

Step 1: Payment List Overview

The Payment List is one of the main tools within Quantum. It is the central place where you can see, monitor, and filter payments for your tenant.

By default, the system shows a list of 25 items per page, along with the total number of payments retrieved for the current filters and time range.

Step 2: Toolbar Controls

At the top of the Payment List, you will find the following toolbar controls:

• Histogram toggle — Show or hide the histogram chart above the list

• Refresh button — Reload the payment data

• Date range picker — Select the time period (default: last 7 days)

• Filters — Add or modify filters to narrow down payments

• Columns — Choose which columns to display in the list

Step 3: Selecting Individual Payments

You can select payments individually by clicking the checkbox next to each payment row. When you select a payment, a selection bar appears at the bottom showing:

• The number of payments selected

• The total amount of the selected payments

Step 4: Multiple Payment Selection

Select multiple payments by clicking additional checkboxes. The selection bar updates in real time, showing the cumulative count and total amount of all selected payments.

This is useful for reviewing a batch of related payments or preparing a bulk action.

Step 5: Bulk Actions on Selected Payments

When you have parked payments selected that support actions, the selection bar displays available bulk actions. For example, you may see a Reprocess button that lets you reprocess all selected payments at once.

Bulk actions save time when you need to perform the same operation on multiple payments simultaneously.

Tip: Bulk actions are only available for payments in specific statuses (e.g., parked). The available actions depend on the payment type and status.

Step 6: Exporting Payments to Excel

To export the current payment list to an Excel file, click the Export button in the toolbar area. The system generates an Excel file containing the payment data based on your current filters and visible columns.

Step 7: Exported Excel File

The export generates an Excel file that is automatically downloaded to your computer. The file contains the same data visible in the Payment List, including all the columns you have selected.

Step 8: Reviewing Exported Data

Open the downloaded Excel file to see the payment data in spreadsheet format. This is useful for:

• Offline analysis — work with the data in your preferred tools

• Reporting — share payment information with stakeholders

• Record keeping — maintain a snapshot of payment data at a specific point in time

The Payment List now shares the same filter experience as dashboards. Add these steps to the Payment List article (after “Step 2: Toolbar Controls”).

Advanced Filtering — Step 1: Open the Filters Panel

Click Filters in the top-right of the Payment List. The filter experience has been homogenized with dashboards and redesigned around three columns: Field, Operator and Value. The Total payments count at the top-left always reflects the filters currently applied.

Advanced Filtering — Step 2: Choose a Field

Open the Field dropdown to see every attribute available from the payment data model — Amount, Client ID, Product, Scheme, Flow, and many more. Start typing to search the list and quickly jump to the field you need.

Advanced Filtering — Step 3: Pick an Operator (including negative operators)

After selecting a field, choose an Operator. The available operators depend on the field’s data type. For a text field you can choose:

• Is — keep records that match the value.

• Is not — exclude records that match the value (negative filter).

• Not exists — keep records that have no value in that field.

For other field types, like amounts or dates, other operators like less than, bigger than or range dates selection operators are available.

Advanced Filtering — Step 4: Set the Value and Add More Conditions

Enter or select the Value for the condition. Click + to add another Field / Operator / Value row — conditions compound together, so you can mix positive and negative filters. Click Apply filters to update the list.

In the example below, Product Is not correspondentbanks reduces the total from 194,297 to 145,164 payments, and the applied filter appears as a chip at the top.

Advanced Filtering — Step 5: Work with Filter Chips

Applied filters appear as chips above the list (for example, Product IS NOT correspondentbanks and Flow: emission). Each chip shows the value being applied. Click a chip to edit its value, or click its × to remove that condition. The Total payments count updates instantly as you add or remove filters.

↑ Back to top

Custom Views

Create, save, duplicate, export, import, and delete custom views in the Payment List to personalize your monitoring workflow.

Step 1: Understanding Views

The Payment List supports custom views — saved configurations of filters, columns, and display settings that you can switch between using tabs at the top of the list.

Views allow you to quickly switch between different perspectives of your payment data without having to reconfigure filters and columns each time.

Step 2: Default and Custom Views

The system provides default views that are available to all users. In addition, you can create your own custom views tailored to your specific monitoring needs.

Both default and custom views appear as tabs at the top of the Payment List. Click on any tab to switch to that view.

Step 3: Using a Custom View

When you select a custom view, the Payment List automatically applies the saved filters and column configuration for that view. For example, a "Parked Payments" view might pre-filter to show only parked payments with specific columns relevant to exception handling.

Step 4: Creating a New View

To create a new custom view, click the Add View button (+ icon) in the tabs area. A dialog appears where you can enter a name for your new view.

Type a descriptive name and click Create. The new view starts with the default configuration, which you can then customize.

Step 5: Configuring View Filters

After creating a new view, customize it by adding filters. Click the filters button in the toolbar and configure the conditions you want. For example, you might filter by processing status, payment scheme, flow direction, or any other available attribute.

Step 6: Configuring View Columns

You can also customize which columns are displayed in your view. Click the columns button in the toolbar to open the column selector. Add or remove columns such as payment code, message ID, or other fields relevant to your workflow.

Step 7: Unsaved Changes Indicator

When you make changes to a view’s filters or columns without saving, an amber dot appears next to the view tab name. This indicator tells you that you have unsaved changes.

Tip: Always save your view after making changes to ensure they persist for your next session.

Step 8: Saving a Custom View

To save your changes, click the three-dots menu (⋯) next to the view tab and select Save. A confirmation message appears indicating that the view has been successfully saved.

From now on, every time you select this view, it will load with the saved filters and column configuration.

Step 9: View Options Menu

The three-dots menu (⋯) on each custom view tab provides several options:

• Save — Save the current filter and column configuration

• Duplicate — Create a copy of the view with the same configuration

• Export — Export the view configuration as a JSON file

• Delete — Permanently remove the view

Step 10: Duplicating a View

Select Duplicate from the view options menu to create an exact copy of the current view. The duplicated view appears as a new tab with a new name.

This is useful when you want to create a similar view with slight modifications without losing the original configuration.

Step 11: Exporting and Importing Views

To share a view configuration, select Export from the view options. The system generates a JSON file containing the complete view configuration.

To import a view, click the Add View button and select Import instead of typing a name. Browse to the JSON file, select it, and click Import. If the view name already exists, you will be prompted to rename it.

Step 12: Imported View Created

The imported view appears as a new tab with the same configuration as the original export. It will have the filters, columns, and all settings from the exported JSON file.

Step 13: Deleting a Custom View

To remove a custom view, click the three-dots menu (⋯) on the view tab and select Delete. Confirm the action when prompted.

You can also delete duplicate or imported views that are no longer needed to keep your tabs clean and organized.

Note: Deleting a view is a non-reversible action. Consider exporting the view first if you might need it later.

Quick Reference

↑ Back to top

Payment Details

Explore the Payment Details view — one of the most important views within Quantum — to review payment information, statuses, audit events, and perform actions.

Step 1: Opening a Payment

From the Payment List, click on any payment row to open the Payment Details view. This is one of the most important views within Quantum, providing a comprehensive view of all information related to a specific payment.

Step 2: Payment Details Overview

The Payment Details view displays the following main sections:

• Payment amount and currency — displayed prominently at the top

• Status chips — colored labels showing the payment’s processing status, sub-status, and functional status

• Assignment information — shows whether the payment is assigned and to whom

• Key dates — settlement date, starting time, finishing time, and total processing time

Step 3: Status Chips and Tooltips

The status chips at the top provide a quick summary of the payment’s state. Hovering over a chip shows a tooltip with additional details.

For example, hovering over a status chip may reveal the functional status (e.g., "Functional status: Parked") along with any associated codes such as payment codes or rejection codes.

Tip: Status codes and rejection codes provide important context for understanding why a payment is in its current state.

Step 4: Times and Assignment Section

Below the status chips, you will find key timing information:

• Settlement date — when the payment is scheduled to settle

• Total processing time — how long the payment took to process

• Starting time — when the payment entered the system

• Finishing time — when processing completed

The "Assigned to" label shows the current assignment status of the payment.

Step 5: Payment Detail Fields

The Payment details section contains all the technical and business information about the payment, organized in a grid layout:

• Message ID, Original message ID, Instruction ID

• Parent payment ID, Internal ID, Payment information ID

• E2E ID, Payment code, Netting reference

• Reference, Delivery channel, Client ID

• Payment Hub ID (the main identifier, shown in a grey chip)

Most fields have a copy icon next to them — click it to copy the value to your clipboard for use elsewhere.

Tip: The Payment Hub ID is the primary identifier used across the system. It is displayed in a grey chip for easy identification.

Step 6: Debtor and Creditor Information

Further down the page, you will find separate sections for:

• Debtor — the party sending the payment (client name, bank account, etc.)

• Creditor — the party receiving the payment (client name, bank account, etc.)

• FX — foreign exchange information (if applicable)

Each section displays the relevant details for that party, including names, bank accounts, and identification numbers.

Step 7: Audit Events

The Audit section shows the chronological events that have occurred during the payment’s lifecycle. Each event includes a timestamp and a description of what happened.

The audit trail is essential for understanding the full history of a payment and troubleshooting any issues that may have occurred during processing.

Step 8: Related Payments and User Activity

Additional sections include:

• Related payments — shows linked payments, for example, a return payment will display the original payment it was created from

• User Activity — shows actions performed by users on this payment, such as assignment/unassignment events and any manual actions taken

Step 9: Payment Action Buttons

When a payment has available actions, action buttons appear at the top-right of the Payment Details view. The available actions depend on the payment’s status. For example, a parked payment with accounting exceptions may offer:

• Reprocess — retry processing the payment as-is

• Reprocess with changes — modify payment data before retrying

• Return — return the payment to the sender

Tip: Action buttons are only displayed when there are valid actions available for the payment’s current status.

Step 10: Reprocess with Changes

Clicking Reprocess with changes opens a sidebar panel on the right. This panel displays the payment’s current data and provides editable fields where you can modify values before reprocessing.

Available fields may include creditor bank account, creditor name, debtor information, BIC codes, and other relevant payment attributes. After making your changes, click the Reprocess with changes button at the bottom to submit.

Step 11: Confirming a Reprocess Action

When you execute any action (Reprocess, Reprocess with changes, or Return), the system displays a confirmation dialog. You may be asked to provide a reason or comment for the action.

After confirming, the system processes the request and displays a success message: "The action has been successfully requested."

Note: All payment actions are recorded in the audit trail and user activity sections for compliance and traceability.

Quick Reference

↑ Back to top

↑ Back to top

Filters in Custom Dashboards

How to use dashboard-level and widget-level filters, set default filters for consumers, and resolve incompatible filter warnings.

Step 1: Open an Existing Dashboard

Open an existing custom dashboard. On the top-right area of the dashboard, you will see the new Filters button. This button allows you to apply filters that affect the entire dashboard.

Step 2: Open the Filters Panel

Click the Filters button to open the filters section. This displays a panel where you can choose any field from the data model to use as a filter. The Filter dropdown contains every filterable field available in the data model.

Step 3: Select a Filter Field

Click on the Filter dropdown to browse and select a field from the data model. For example, you can select Scheme to filter the dashboard by payment scheme. The list includes fields such as Product, Product family, Scheme, Scheme ID, Channel, Status, and many more.

Step 4: Choose Filter Values

After selecting a filter field, choose the values you want to filter by in the Value column. In this example, the values sct and correspondentbanks are selected for the Scheme filter. You can select multiple values for the same filter.

Step 5: Apply Filters and View Results

Once the filter values are selected, the dashboard data updates immediately to reflect the applied filters. A filter chip appears below the toolbar showing the active filter — for example, “Scheme is one of sct, correspondentbanks”. This chip provides a quick visual indicator of which filters are currently active.

Step 6: Edit an Applied Filter

To edit an existing filter, simply click on the filter chip. This reopens the filters panel with the current filter field and values pre-selected. From here, you can modify the values, change the filter field, or remove the filter entirely.

Step 7: Set Filters as Default (Dashboard Creator Only)

As the creator (editor) of the dashboard, you have the option to click “Set as default”. When you set filters as default and publish the dashboard, all consumers who open the dashboard will see these default filters applied automatically.

Step 8: Clear Default Filters

To remove default filters, clear all active filters and then click “Set as default” again with no filters selected. The next time the dashboard is opened, no default filters will be applied.

Step 9: Consumer Experience: Default Filters

When a consumer opens a dashboard that has default filters set by the creator, those filters are automatically applied. The consumer sees the filtered data as defined by the dashboard creator. However, consumers are free to change, remove, or add additional filters to customize their view during the session.

Step 10: Consumers Can Add Additional Filters

Consumers of the dashboard can add additional filters beyond the defaults. For example, a consumer could add a Message definition filter on top of the existing Scheme filter. These additional filters are session-specific — when the consumer leaves and returns to the dashboard, only the default filters will be applied again.

Step 11: Apply Additional Filters

In this example, the consumer has added a Message definition filter with the value pacs_008_v08 in addition to the existing Scheme filter. After clicking Apply, the dashboard data will be further narrowed to show only payments matching both filter criteria.

Step 12: Understanding Filter Levels: Dashboard vs. Widget

It is important to understand that there are two levels of filters in custom dashboards:

• Dashboard-level filters — Applied via the Filters button at the top of the dashboard. These govern all widgets and data displayed across the entire dashboard.

• Widget-level filters — Each individual widget (count cards, tables, bar charts) can also have its own filters. These are configured within the widget settings and can be used to apply additional, widget-specific filtering.

Step 13: Widget-Level Filter Configuration

When you open a widget configuration (e.g., a Count widget), you can see its Applicable filters section. Here you can define widget-specific filters. For instance, a widget named “Recepción” may already have a Flow filter set to “reception” to show only inbound payment data.

Step 14: Filters in Table Widgets

Table widgets also support their own filters. You can apply filters at the table level to further narrow the data displayed within that specific table, independent of the dashboard-level filters.

Step 15: Filters in Bar Chart Widgets

Similarly, bar chart widgets support widget-level filters. You can define specific filter criteria for each chart to control what data is visualized, in addition to the dashboard-level filters.

Step 16: Incompatible Filters Warning

When a dashboard-level filter conflicts with a widget-level filter, an “Incompatible filters” warning is displayed on the affected widget. For example, if a widget is configured to show only “reception” flow data but you apply a dashboard-level filter for “emission” flow, the widget will display: “Incompatible filters — The following filters are not compatible with this widget: Flow”.

Step 17: Resolving Incompatible Filters

To resolve an incompatible filter warning, you can either:

• Remove the conflicting dashboard-level filter, or

• Remove or adjust the widget-level filter to make them compatible.

Once the conflict is resolved, the widget will display data correctly again.

Important: Only the dashboard creator/editor can set default filters. Default filters define the initial view, but consumers can still modify or add their own filters on top.

Quick Reference

Key Takeaways:

• Dashboard-level filters apply to the entire dashboard and affect all widgets.

• Widget-level filters apply only to individual widgets (count cards, tables, charts).

• Dashboard creators can set default filters that are applied automatically when consumers open the dashboard.

• Consumers can add, modify, or remove filters during their session, but only the defaults persist between sessions.

• If a dashboard-level filter conflicts with a widget-level filter, an “Incompatible filters” warning appears on the affected widget.

• Filters provide great flexibility to analyze payments across multiple dimensions — by scheme, flow direction, message type, client ID, and more.

↑ Back to top

Manual Payment Creation

Use the Mandates section to search, create, update, cancel, activate, delete, and approve payment mandates in the Operations Portal. Access and available actions depend on the role assigned to the user.

Roles and permissions

Access Mandate Store

1. Open the main menu and expand Mandate Store.

2. Select Mandate Store to open the mandate list, or Mandate Review to manage approvals.

3. Choose the payment scheme tab: FED, SEPA, SWIFT, or BACS. Each tab displays its own columns and filters.

Search and filter mandates

The mandate list includes filters above the results table. The available filters change according to the selected scheme. Common examples include debtor account type, debtor account, creditor account type, creditor account, sender or receiver identifier, tenant, status, and mandate ID.

1. Enter or select the criteria to apply.

2. Click Apply filters to update the result set.

3. Click Clear filters to reset the filter bar.

4. Use the pagination controls at the bottom of the table to move across result pages.

Create a mandate

Users with the Mandate Store Operator role can create a new mandate from the selected scheme tab. The creation flow is displayed as a stepper. The Continue button becomes available as the mandatory fields for the current step are completed.

1. Open Mandate Store and select the required payment scheme tab.

2. Click Create.

3. Complete the mandatory fields in each step.

4. Review the Summary step before submitting the mandate.

View mandate details and audit information

Select a mandate from the results table to open its detail page. The detail view shows the mandate identifiers, tenant, debtor and creditor data, current status, source, creation date, and user audit information.

Actions from the detail page

Depending on the user role and mandate status, the detail page can display actions such as Activate and Delete. From the table row action menu, operators can also access actions such as Edit, Cancel, Activate, or Delete.

Review pending mandate changes

Users with the Mandate Store Approval role can use Mandate Review to access mandates with pending approval actions. The review list is separated by the same scheme tabs and includes filters so reviewers can narrow down pending items.

1. Open Mandate Store > Mandate Review.

2. Select the relevant scheme tab.

3. Use the filters to find a pending request.

4. Open the request detail and review the proposed action and mandate data.

5. Click Approve or Reject. The user who approves or rejects must be different from the user who requested the action.

Mandate lifecycle actions

Four-eyes approval control

Some mandate actions may require approval before they are completed. When approval is required, the requested action is displayed in Mandate Review and must be approved or rejected by a different authorised user. This ensures sensitive mandate changes follow a four-eyes approval process.

↑ Back to top