Checkout Type in Reports 🛒 📊

We've added a new column, Checkout Type, to the Transactions, Payment Plans, and Scheduled Charges reports. This column mirrors the functionality found in the Customer Analytics report, aiding in identifying checkout types. It helps users determine whether a transaction was a regular instant payment or scheduled, full or partial, and whether it was related to a payment plan or a settlement.

Here are all possible Checkout Types:

1.  Suggested Payment Plan 
2.  Custom Payment Plan 
3.  Settlement Payment Plan 
4.  Payment in Full 
5.  Payment in Full Scheduled 
6.  Partial Payment 
7.  Partial Payment Scheduled 
8.  Settlement in Full 
9.  Settlement in Full Scheduled 
10.  Guest Payment in Full 
11.  Guest Partial Payment 
12.  Guest Settlement in Full 

Checkout Type is also available as a Group By column, allowing for new analytical breakdowns in your reports.

E-Sign Legal Policy on Email Change 📧

When the E-Sign Legal Policy is required for acceptance (found under Console Settings > Legal Policies) and a customer attempts to update their email on their profile, they will be prompted to re-accept the E-Sign Policy.

This checkbox 👆is optional and will only be visible if enabled for your organization upon request.

Customer’s Emails Exporting to Zip 📨

We continuously strive to enhance compliance and operational tools. To this end, we have introduced a feature that allows for the automatic export of all customer emails sent from the Tratta platform on a daily basis. Emails are exported in .eml format and archived in a .zip file named with the date (YYYY-MM-DD.zip).

Each email file is named using the following pattern: {date}_{org name}_{email}_{account number}_{notification type}.eml 

This feature can be enabled for your organization upon request.

Stay tuned for our next update in October! 🍁

Spanish Localization Updates 🌐

We've expanded the capabilities to add translations for dynamic content in Console Settings:

• Legal Policies

• Footer Text (Settings > Branding)

Update the translations for your organization today! 🚀

Custom Payment Disclosure 📋💳

We now offer the ability to customize the payment disclosure on the checkout page. Currently, this is an internal setting. Please contact help@tratta.io if you would like to modify the default disclosure text for your organization. Custom text supports both English and Spanish versions.

Scheduled Attempts Number for Declined Card Payments ⏲️💸

Customize the default maximum attempts number for scheduled card charges, which is set at 3 by default. This setting can now be changed upon your request to help@tratta.io

IVR Verification Improvements 📞

We've enhanced the IVR verification flow:

• Only allowed methods for the customer portal (DOB, Last 4 of SSN, ZIP Code) will be prompted by the IVR.
• If the debt account holder lacks information for some allowed methods, these will be skipped.

• If only one method is available for the current account, the IVR will automatically select it and prompt the caller to enter verification information for this method.

Additionally, we've updated the call forwarding feature. Previously, when callers pressed * to speak with a representative, calls were automatically directed to the primary organization phone number. Now, you can customize Forwarding Number to any designated line upon request.

API updates 🔗

• Added Disputes Webhooks.

• Added a payment_source attribute to the Payment Plans, Scheduled Charges, and Transactions webhooks.

For more details, check our webhooks documentation.

Payment Portal Now Available in Spanish! 🌐

To enhance the experience for our diverse customer base, we are pleased to announce that our payment portal is now available in Spanish. This update allows Spanish-speaking consumers to navigate, understand, and manage their payments more comfortably and efficiently. Debtors can easily switch to the Spanish version by selecting Spanish from the language options within the portal.

IVR updates 📞

• We've enhanced the IVR by introducing dynamic verification methods. After recognizing a debtor's account, the automated phone system will now only offer verification methods—such as ZIP, Date of Birth (DOB), and the last four digits of the SSN—for which there is corresponding data available in the system. This will help to increase the verification rate for customers paying via IVR.

API updates 🔗

• New Feature: Ability to Create Payment Methods: We've added functionality for storing payment methods, which can now be used in Charge endpoints. For detailed instructions on how to create payment methods, please visit the relevant pages on our API Documentation or Postman.

Disabling Payment Rules for Agent Payments 💳

In your Settings, you can control all aspects of payments (minimum amount for one time payments, maximum number of months for a payment plan, etc). These rules controlled both consumer-driven self service payments, as well as agent-driven payments on behalf of consumers.

• Following this update, you can now separate these - making it possible for your agents to go beyond these rules. This option can be enabled for your organization upon request.

Stay tuned for more updates in this direction!

Customer Portal Updates 🚀

• Consent Request Popup: We’ve enhanced the consent request popup to align with the latest compliance best practices. The E-Sign policy is now distinctly separated from other policies and includes the required legal wording. Additionally, we’ve introduced an optional feature: required checkboxes to ensure active consent from customers. These checkboxes can be enabled for your organization upon request.

• Payment Plan Page: We've added a brief payment plan summary block to a consumer’s payment plan page. This update allows customers to immediately see the number of payments, the dates of the first and last payments, and to open a popup with the full payment schedule.

IVR Works with Different Patterns of Account Numbers 📞

• We've enhanced our IVR account verification to accommodate numbers that may contain special characters, such as dashes (e.g., 12-21345, MKS-1231). Now, we can configure the IVR system to recognize the patterns your organization uses in account numbers. The IVR will prompt callers to enter their account number without special characters—making it much easier over the phone—while still accurately identifying and looking up such accounts.

Bug Fixes 🔧

• Various bugs were addressed 🐛🐞

Create Debt Account and Create Customer ☑️

Typically, data appears in the Tratta System via file imports or through API integration.

However, there are instances where manually creating new debt accounts and associated resources is beneficial.

We've added the ability to create Debt Accounts and Customers directly within their respective sections—making it easy and straightforward!

If your organization utilizes a Parent-Child account structure, child accounts can now be added directly on the Parent Account page.

Please check out our documentation for more details.

Locations Settings 💼

Creating a Debt Account requires not only connecting a Customer but also assigning Locations.

Locations refer to the categories within an organization to which a Debt Account is assigned. Each Debt Account has a primary location, typically the Original Creditor. Additionally, a Debt Account may be linked to multiple other locations, further classifying it into subcategories such as Current Creditor and Product Types.

We have added a locations management feature in the Settings section.

Now, you can review, add, and edit locations with ease. For more detailed guidance on using this feature, review our documentation.

Dynamic Verification Methods for 1-Step Verification ☑️

We've enhanced our 1-step verification process, used in session links, to only display verification methods for which data is available in the system. By default, customers can choose from three methods: ZIP code, Last 4 of SSN, and Date of Birth. With this update, only methods with existing data will be shown. If only one piece of data is available, it will be displayed immediately, eliminating the need for customers to select a method and potentially get stuck.

Users & Permissions related updates 👥

• Enhanced UI for Permission-Based Features: We've improved our user interface to make it easier for users to identify features they don’t have access to. Features that are not available due to permission restrictions now appear greyed-out, often accompanied by a lock icon. When users hover over these elements, a tooltip will appear, explaining that they lack the necessary permissions to access the feature and suggesting that they contact their organization's admin to request access. This update simplifies system usage for agents and other users with limited permissions.

• Updated Users Import Feature: We've enhanced our Users Import feature to support the import of recently added user roles. To import users with roles, simply fill an additional column in the source CSV file with the role names. Please ensure that these roles are created in the system before importing.

Bug Fixes & API Maintenance 🔧

• 🔗 Multiple updates have been made to the API to provide better error responses and make its use more intuitive for our clients' developers.

• 💳 Fixed several minor bugs in the Create Payment flow.

• 🐛 Addressed various other bugs.

During the last few months, we have been working on refining User Management. Today we released the biggest update yet - Roles - and we are happy to share it with you!

Roles for consistent and efficient permissions management 👥

The Roles feature enables you to attach a set of permissions to a role and assign it to one or multiple users.

For example: Your organization can have two roles: Admin (with full permissions) and Agent (limited access to settings and some features). The Agent role can be assigned to many users. If you need to change permissions for all these users, you only need to adjust the permissions for the Role itself.

To create and manage roles, navigate to Settings > User Management > Roles.

When you create or edit users, you can assign one of the existing Roles or Custom Permissions. Using Roles is the recommended approach.

We have migrated all users with the old admin user type to an Admin Role (full permissions), and users with standard to a Custom Permissions mode (to maintain the permissions previously assigned to them).

We invite you to create your first Role and assign it to users! This can bring significant value to organizations that have many users with a similar set of permissions.

Permissions Matrix ☑️

As our system expands and the number of permissions increases, we have redesigned the permissions list into a more user-friendly matrix format as part of the User Management update.

Permissions are categorized into groups such as Customer, Debt Account, Reports, Settings, etc. It is possible to toggle all permissions within a category by clicking the checkbox next to the category name.

Standard permissions are organized in a matrix format across four actions: View, Create, Update, and Delete.

Custom action permissions are listed separately with toggles.

Check out our help docs or reach out to us if you have any questions or feedback! 🚀

Payment Source in Console Reports 📊

We've added new columns to the Transactions, Scheduled Charges, and Payment Plans reports, relieving you of the burden of tracking where your payments are coming from and how they are made.

1. Payment Source now indicates the origin of the transaction’s creation:

•  Console: This data point summarizes all payments created on the Console side by a User (someone at your company), such as an agent or collector.

•  Collect: This data point summarizes all payments created by a consumer exclusively using Tratta’s self-service portal. This does not include guest payments or IVR payments. This includes payment plans, scheduled payments, and one-time payments. This is where the real bang for the buck is!

•  Guest: This category aggregates payments executed via our guest checkout feature for consumers unable or unwilling to establish an account.

•  IVR: Aggregates payments executed through our payment automated phone platform.

•  API: For those firms that have integrated their SOR, IVA, or another application to our platform via APIs, this data point will total payments processed by Tratta that were shared with us via your API.

2. Payment Source Name now allows you to track the payment source, whether a User or an API integration, by name. This feature is excellent for creating leaderboards for your agents and seeing how integrated partners perform.

Console Create Payment 💳

• Create Payment is now restricted to Parent Accounts only to maintain consistency with the overall system design (payments are allowed only toward parent accounts).

• Settlement Offers now allow for agents to set custom discount percentages and amounts. Custom parameters can be set within the default offer setup and full balance.

• We've optimized the calculation speed for long payment plans.

Bug Fixes & System Maintenance 🔧

• We removed Customer Status an available status.

• Further optimized the Users import flow.

• Optimized search performance across all pages within the Tratta eco-sphere.

• Addressed various minor bugs 🐛.

Enhanced Settlement Offer Metadata Integration 🏷️

• We've refined the flow for setting up Settlement Offers based on metadata amounts. This update enables you to specify a custom settlement amount for each debt account in your file, which can then be utilized in configuring offers.

• We updated the Offer Dates block to allow the setup of Start and End dates separately. Each date now supports three modes: Not Limited (Immediate for Start or None for End), Absolute date, and Based on Metadata date with a shift in days.

Waving Fees for Console Payments 🪙

• Now, agents can exclude fees for specific accounts in the Console Create Payment section. Simply uncheck the fee on the Payment Summary to waive it and see an instant update in the payment setup totals.

• This is a permission-based feature. It’s easy to grant or revoke access on the single User Page (under Transactions Permissions Group > Waive Fees).

Fixes & Maintenance 🔧

• A few bugs were fixed 🐛, and several minor improvements were added 🪴.

We added a new Settings section > Account Notices 🪧

This section enables you to set up and manage the notice content displayed for accounts with a closed status and specific External Statuses.

Creating notice and control notice content is easy now!

Please, find more information in Help Docs.

Console Settings > Notifications > Email Footer > State rules 📧

• Added new variable for customization of the inclusion of the Universal Footer in the State Specific text (more details in Help Docs)

Bug Fixes & Maintenance 🔧

• Various bugs 🐛 were fixed, and system improvements 🪴 were implemented.