Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Portal (Version 24.11.0)

New Features

  • Multi-Factor Authentication Enablement page has been added to the Portal to to provide an additional layer of security when signing into the Portal or other sensitive API operations.

  • New Users that are created in the Portal for accounts with MFA set as “required” will now display a “Multi-Factor Authentication Enabled?” field to allow the active user creating the new user to automatically configure MFA for the user being created.

  • Users that attempt to access the Portal after having MFA enabled on their login will be required to enroll and confirm with an authenticator app.

  • Users can now enroll in MFA using their preferred Authenticator app, such as Microsoft or Google Authenticator.

  • Users that enroll in MFA will now see a “Confirmation” response when the code they submit from their Authenticator app is either valid, allowing access, or invalid, denying access.

  • Facilitators and Referrers may search the Multi-Factor Authentication Enablement page for users and their MFA Enrollment and Enabled status. (Note: Referrers access is “read-only”).

Improvements

  • The Risk Score tile shown on the Merchant Profile page has been improved with new logic to improve load time and accuracy.

  • Compliance Overrides role resource has been added to User Roles and Access Templates to allow AML Ratings, shown on their Merchant Profile pages, to be manually updated when needed.

  • Tax Exempt Organizations, Partnerships, and Limited Company have now been added to signup form business types to properly accommodate Canadian businesses.

  • GIACT Smart Card for Transactions has been updated to adopt gVerify and gAuthenticate logic for Referrer-level users to align with GIACT bank and transaction verification processes for faster results.

  • “Security” tab has been added to Partition and Division Details pages to allow quick overall security options for all members within for faster enablement of security features.

  • Bridger Smart Card has been updated to consolidate Politically Exposed Persons, Adverse Media and OFAC Sanctions for faster viewing.

  • “Boarded Today” Smart Tile has been updated to display a miniature graph to see a high level of the data at a glance without clicking on the tile.

  • The Gross Sales graph on the dashboard has been updated to improve loading times and prevent scroll blocking when loading takes place.

Reporting

  • Monthly Statements generated on the Monthly Statements page has been updated to offer print and download options to allow users more record-keeping options.

  • Monthly Statements now allow Referrers to while-label the Merchant experience of the page and it’s generated content including colors and contact information.

  • Balance Detail Reports now offer Disbursement Payout, Payout Status, Line Item, Line Item Status, and Disbursement Entry Status Description report field columns to help more easily identify details about a disbursement.

  • Balance Detail Reports now offer Fee Interchange Assessments, Assessments Rate and Assessment Amount report field columns to more quickly identify fee interchange information.

  • Statement Detail Reports now offer Disbursement Payout and Payout Status report field columns to help more easily identify Disbursement payout info from a statement.

  • Balance Detail Reports now offer Fee Interchange Assessments, Assessments Rate and Assessment Amount report field columns to more quickly identify fee interchange information.

Issues Resolved

  • Issue resolved where txn.settled event web alert resource would not display as an option when setting up the alert in the Portal.

  • Issue resolved where the Risk Management page would not display RecordStatus values.

  • Issue resolved where the “Security” tab for the Multi-Factor Authentication Enablement page would not display.

  • Issue resolved where User could enable or disable their own Multi-Factor Authentication configuration.

API (Version 23.11.0)

New Features

  • Multi-Factor Authentication (MFA) is now shown as a field for each Login (User) record on the API server to provide an additional layer of security when signing into the Portal or other sensitive API operations.

  • Users that attempt to access the Portal after having MFA enabled on their login will be required to enroll and confirm with an authenticator app.

  • Users can now enroll in MFA using their preferred Authenticator app, such as Microsoft or Google Authenticator.

  • Users that enroll in MFA will now see a “Confirmation” response when the code they submit from their Authenticator app is either valid, allowing access, or invalid, denying access.

Improvements

  • No labels