📽️ Video overview

🛒 Abandoned Checkout Recovery, Now Self-Serve

Some consumers open your payment portal, start a payment, and leave before finishing. Abandoned Checkout Recovery (ACR) is a Tratta campaign that follows up with them automatically by email or SMS, bringing them back to complete the payment they already started.

You can now turn on ACR yourself in Console, with no involvement needed from Tratta staff. Find it under Suggested campaigns on the Campaigns dashboard, pick your channel and start date, preview the message exactly as consumers will see it, and send yourself a test before going live. To change the message wording, contact Tratta support. Turning on ACR adds it to your Campaigns plan.

You can also set up your own email sending domain (for example, campaigns@yourdomain.com) right in Console, so your campaigns come from an address consumers recognize.

How to set up ACR in Console

How to set up your sending email domain

💬 Two-Way SMS in Contact Center

When a consumer texts back after a notification or a campaign message, the reply now lands in Contact Center as a conversation on the right consumer and account. Agents answer by text from the same inbox they use for email, and replies go out from your usual sending number, so the thread on the consumer's phone stays one conversation. Replies to payment requests reach Contact Center once your Tratta team turns them on for your payment request number. Two-way SMS requires Contact Center.

• Easy to spot: text conversations show "SMS" in the Source column and filter, titled by what the consumer replied to (for example, "Reply to payment request").
• A reply box built for text: a counter shows characters and the number of SMS segments, and your message templates work here too.
• Compliance stays in place: opt-out and help keywords work exactly as before. If a consumer has opted out, the conversation says so and the reply box is hidden. Your setting that limits two-way communication to selected accounts applies to text as well.
• Unmatched replies: a reply that can't be matched to an account still reaches an agent, who can link the conversation to the right consumer and account.

The whole exchange sits on the account history next to email.

✍️ Tratta Sign API

Send signature-ready documents to Tratta Sign straight from your system of record (SOR). Over the API, you attach a document (DOCX with a signature placeholder) to an account using the account identifier you already use, choose where the consumer sees it, and optionally email the consumer right away. Documents can appear in the consumer's document list at login, or at full payment, payment plan, settlement offer, or guest checkout.

Once the consumer signs, a webhook tells you which signed document just came in. Download each signed copy, with its Certificate of Completion, over the API. Pass your own document reference so a retry never creates a duplicate signature request.

Run the whole round trip (send, sign, and file back into your SOR or document system) without anyone touching Console. API docs: docs.tratta.io/signature-documents.html.

📜 Policies & Consents

Console > Settings > Legal policies is now Policies & Consents, redesigned with a list of all your policies and a detail page for each. You can now add new policies yourself, right from Console.

• Policy types: each policy is a Legal Policy, a Payment Authorization (Portal), or a Payment Authorization (Console). The type decides which fields apply, so every policy shows only what's relevant.
• Consent popup on autopilot: the consent prompt at login appears whenever at least one Legal Policy uses the "Consent prompt at login" context. No separate toggle to manage.

🚫 Auto-Block ACH After Repeated Returns

Set a threshold in Console payment settings and Tratta blocks a consumer from paying by ACH after that many consecutive returns. The block follows the consumer, not a single bank account, so entering a new account number doesn't get around it. A successful payment resets the count, and agents can lift a block from Console with a reason. The setting is off by default (opt-in, with a default threshold of 2).

🧾 Custom Account Details in Collect

Show consumers the account details that matter to your business. Add custom lines to the account details in Collect, filled from your account metadata. They appear next to creditor name, balance, account number, and visible locations, both at checkout and on the Account Detail page.

🎨 Console Redesign: Dashboard, Login, Emails, Account & Customer detail

The new Console look now reaches the Dashboard, the full login flow (sign in, organization picker, create password, and reset password), and transactional emails. Same workflows, cleaner and more consistent screens.

Account and Customer detail pages got the biggest refresh. Content is now organized into tabs, so agents get to what they need faster. Accepted policies are laid out more clearly, so it's easy to see which policies a consumer has accepted.

🛠️ Minor Updates

• Security update: on October 21, a critical vulnerability affecting widely used web server software was publicly disclosed. We applied the fix within minutes of its release during a short, pre-announced maintenance window, and had already added extra protections at our firewall earlier that morning as a precaution. Tratta has not experienced any known security incidents related to this vulnerability.
• Autopay keeps the agreed amount: each charge before the last stays at the installment amount the consumer agreed to. The final charge collects whatever balance remains, and minimum payment rules never raise a charge above the agreed amount.
• Quieter customer.update webhooks: the API now sends customer.update webhooks only when customer data actually changes, not when only activity timestamps change. Less noise for integrations that sync to your SOR.
• Clearer API error for duplicate external IDs: updating a customer to an external ID another customer in your organization already uses now returns a validation error (422) instead of a server error.

• Plus ongoing bug fixes and stability improvements 🐛

More updates on the way. Stay tuned! 💫

If you want any of these walked through for your team, reach out to your Tratta contact. More updates are on the way. You can see the full list anytime at https://whatsnew.tratta.io/announcements 💫

📽️ Video overview

🖼️ MMS for SMS Campaigns

SMS campaigns can now carry an image. Ask your Tratta team to add an image (JPEG, PNG, or GIF, up to 1 MB) to any SMS template, and every message from that template goes out as MMS. Templates without an image keep sending as plain SMS, so the campaigns you already run stay exactly as they are.

Use it to put your logo, a QR code that opens your payment portal, or a visual payment reminder in front of consumers. An image stands out in a busy inbox and helps consumers recognize a message from your agency at a glance.

• Previews: the template preview in Console shows the image above the text, so you see what consumers will receive.
• Reporting: MMS sends are reported separately from SMS.
• Credits: each MMS uses 3 credits. Plain SMS stays at 1 credit per 160 characters.

🤝 Send Custom Settlement Offers by Email or SMS

When an agent agrees on a settlement with a consumer, they can now send that exact offer straight to the consumer by email or SMS. The agent doesn't need a payment method on the call. In Console, create a custom offer as a one-time payment or a payment plan. Set the discount as a percentage (for example, 10% off) or as a fixed payoff amount (for example, $100 to resolve $122.34), choose an offer expiration date, and send.

The consumer gets a payment link with a summary of the offer, opens it in Collect, adds a payment method, and accepts. Collect shows only the agreed terms, with nothing to change or reselect, so what the consumer sees matches what was discussed.

Until the consumer accepts, the account shows a Pending settlement offer badge. Agents can see the offer details and when it was sent, and cancel it if plans change. Once the consumer accepts, the offer becomes active automatically. If they don't accept by the expiration date, the offer closes.

📊 A New Campaigns Dashboard

The Campaigns dashboard in Console has a fresh design that puts all of your campaigns in one overview. See at a glance what's running and how each campaign is performing, without opening them one by one.

Filter the dashboard by date to focus on any period you need, whether that's last week's outreach or a full quarter. By default it shows the last 3 months, so your most recent activity is always front and center. From there, open any campaign to dig into its runs and results, or activate and pause campaigns right from the dashboard.

🧪 Campaign Launch Controls

When you send a test email or SMS, you can now pick an account in the Send test drawer. The template fills in with that account's details (name, state, balance, and external ID), the preview updates, and the test message goes out with that data. See exactly what a consumer will receive before a campaign goes live.

Building a campaign and activating it are now separate permissions. One user can prepare and edit a campaign, while only users with the activate permission can put it live, so a campaign can go through review before it reaches consumers. Each campaign also shows who published it and who last activated or paused it.

🎨 Console Redesign: Documents and Settings

The Console redesign continues. These pages now have the new look:

• Documents: a cleaner list and signed document view, with Download.
• Settings/Settlement offers: create and edit offers in a side drawer, and filter offers by status.
• Settings/Report columns: updated to the new design.
• Settings/Locations: search and filter your locations.
• Settings/User account: profile, security, and notifications in one place under Settings.
• Settings/Security and Audit logs: updated to the new design.

✍️ Tratta Sign: Duplicate Templates

Every Tratta Sign document template now has a Duplicate action that opens a new template already filled in from the original. Templates that have already been signed are read-only, so every signed document stays tied to the exact version the consumer saw. Need changes? Duplicate the template and edit the copy. Signed templates you no longer use can be deleted to keep your list tidy.

🛠️ Minor Updates

• Contact Center attachment indicator: tickets now include a has_attachments flag in the API and in the ticket.create and ticket.update webhooks. Your system of record can spot tickets where a consumer sent a file and route them to an agent first. The files themselves stay in Console.
• Minimum discount for custom offers: set a minimum discount for custom offers, alongside the existing maximum. It defaults to 1%, so nothing changes unless you adjust it. Set it to 0% to allow very small discounts, which comes in handy on high-balance accounts.
• API: settlement offer cancellation webhook: when a settlement offer is canceled, the debt-account-settlement-offer.update webhook now includes the canceled scheduled charge reference, so your system of record can match the cancellation to the right payment.
• ACH batch close date: ACH payments now carry their batch and its close date, which you can filter on in the transaction report. The close date is calculated, so it can differ by a day from your processor's batch email.
• ACH blocklist permissions: viewing, blocking, and unblocking bank accounts are now separate permissions. Users with view access see the list with actions locked.
• Tratta Sign emails: the document-to-sign email now comes from your own sender address instead of Tratta support.
• Plus ongoing bug fixes and stability improvements 🐛

More updates on the way. Stay tuned! 💫

If you want any of these walked through for your team, reach out to your Tratta contact. More updates are on the way. You can see the full list anytime at https://whatsnew.tratta.io/announcements 💫

💳 Autopay Plans, Now with Tiers

Autopay plans can now step up over time. Set the first three months at $150, the next three at $250, then $500 a month until the balance is paid, all on a single plan with no fixed end date.

Tiers give agents a real negotiating lever. A consumer who balks at $300 a month will often agree to start at $100 and step up from there, and the plan still handles interest correctly on interest-bearing files. Build the tiers directly in the Create Payment flow, and review or adjust them from the payment plan details screen.

Create Payment also picks up the latest Console design in this release, so the whole flow (one-time payments, settlement offers, and payment plans) is quicker to move through.

🛡️ Cap ACH Payments at an Amount You Choose

Each organization can now set a maximum amount for a single consumer-initiated ACH payment. Set it once and it applies to one-off ACH payments on the consumer portal. Leave it unset and nothing changes.

A consumer whose payment lands above the cap is not dead-ended. They are offered a payment plan for the same balance with installments that fall under the cap, so the money still moves and the account keeps progressing. Card payments and existing payment plans are unaffected, and agents can still take a larger ACH payment from Console.

Why this matters for debt collection:

• Overall return rate level: a large debit is likelier to come back unpaid, and every return counts toward the 15% overall return rate level NACHA asks originators to stay under. Capping the largest payments is a direct lever on that number.
• Processor relationships: an agency sitting near a return-rate threshold risks a notice from its ACH processor. A cap brings the rate down without turning ACH off.
• Keeps the cheap rail: ACH is still the low-cost option. Capping a payment keeps the consumer on ACH through a plan instead of pushing the balance to card.

🔍 Console Search, Redesigned

Search in Console now opens as a full modal over whatever page you are on, with results laid out for scanning instead of squeezed into a dropdown. It stays on top on Customer and Settings pages rather than slipping behind the overview bar.

Searches containing an ampersand return correct results too, so an account like "Smith & Sons" finds what you expect.

🚫 ACH Block List, Cleaner

The ACH block list now shows only the blocks tied to your own accounts, and every row links straight to the transaction that triggered the block and the account behind it. Routing numbers are visible, and the full bank account number can be revealed with the eye icon by users whose permissions allow it.

📊 Customer Metadata in Reports

Report columns can now pull customer metadata alongside debt account metadata. Add attributes that belong to the person rather than the account, a co-debtor number for example, to your Transactions report and the other reports that support column customization, in Console > Settings > Report columns.

📱 State-Specific SMS Disclosures

Disclosure text can now vary by the consumer's state. For example, California may require an agency's license number on every text to a California consumer, so you can set that wording for California alone while every other consumer keeps your default. It covers both transactional and campaign SMS.

🛠️ Minor Updates

• Batch ACH from your own FTP: Tratta can pull Batch ACH files from an FTP you host, matching how import and campaign files already work. Ask your Tratta account manager to set it up.
• Default expiration for payment request links: set your own default expiry instead of the standard 90 days. It prefills one-time payments, settlement offers, and payment plan requests, and agents can still change the date on any individual request.
• Payment settings, redesigned: Console > Settings > Payment settings now follows the new Console design.
• Contact center settings, redesigned: Console > Settings > Contact center now follows the new Console design.
• Decline reasons in charge webhooks: succeeded and failed charge events now carry the payment's error code and error description, matching the Error and Error Code you see for that payment in the Transactions report, across every gateway. If you build your reporting on the API, failed payments now explain themselves without a second lookup. The new fields are documented at docs.tratta.io.

More updates on the way. Stay tuned! 💫

If you want any of these walked through for your team, reach out to your Tratta contact. More updates are on the way. You can see the full list anytime at https://whatsnew.tratta.io/announcements 💫

✍️ Tratta Sign, Now Pay As You Go

Tratta Sign no longer needs a subscription tier. Any organization can send a document for signature ad hoc and pay a flat cost per signed document, with pay-as-you-go documents shown as their own line on the invoice. If you already hold a Tratta Sign tier, nothing changes: you stay billed under that tier only, never both.

Why this matters for debt collection:

• Signature volume arrives in bursts: settlement agreements, hardship letters, and payment authorizations are episodic per client and arrive unevenly across a large book. The blocker was never the signature, it was committing to a tier sized for a volume that is uneven by nature.
• Same document either way: pay-as-you-go documents carry the same Certificate of Completion and audit trail as tiered ones.
• Costs you can see: per-document charges sit on their own invoice line, so you can tie signing spend back to the accounts that generated it.

📊 Campaign Detail, Redesigned

Campaign detail has a new design in Console, and it now covers SMS as well as email. Items in the SMS campaign list are clickable and open the same detail view, so both channels report the same way.

• Email and SMS in one view: SMS campaigns now get the same detail view and the same reporting as email.
• Filter by date range or run: narrow campaign data to any window, or to a single run. Clicking a run in the Runs list opens the detail with that run already filtered.
• Preview the template: see exactly what goes out, for pre-defined templates and custom ones alike.
• Send a test: send yourself a test email or SMS before a campaign reaches consumers.

Send yourself a test SMS, not just a test email, and read the message a consumer would get before the campaign runs.

🔔 Payment Reminders Follow Rescheduled Payments

When a scheduled payment moves to a new date or amount, the earlier reminder is invalidated and a fresh one goes out ahead of the updated date, on your configured notice period.

Why this matters for debt collection:

• The notice period survives the change: a rescheduled payment no longer means a consumer holds a reminder for a date that has moved, or gets no reminder at all.
• Agents can reschedule without a workaround: an agent can move a payment for a consumer and the required notice still lands on time, automatically.

⚙️ Console Settings, Redesigned

The Console redesign continues through Settings. Notifications, Account notices, Properties, Tratta Payments, and Branding all move to the new design, matching the layout, navigation, and controls already in place across the rest of Console.

🛠️ Minor Updates

• Open Any List Row in a New Tab: Cmd+click on Mac, or Ctrl+click on Windows, opens any row in a Console list in a new tab. Work an account, a transaction, or a campaign without losing the list you were reading, and queue up several at once.
• Account security in Console: changing a Console user's email now requires the current password, and the address does not change until a confirmation link sent to the new address is opened, with a security notice going to the old one. Password rules are shown upfront, masked fields have a reveal toggle, and the account security page now shows when a password was last changed and how many recovery codes are outstanding.
• Guest dispute webhooks: disputes submitted by guests now fire a webhook the same way verified disputes already did, so an integration no longer misses that event class.
• Folder path on SFTP export targets: Reports now shows the folder path on each SFTP export target, so several targets on one server are no longer indistinguishable labels.
• Multiple billing invoice recipients: billing invoice emails now accept a comma-separated list of addresses.
• Batch ACH from your own FTP: Tratta can now pull Batch ACH import and campaign files from a client-hosted FTP server. Contact support to set this up.
• Signed document exports over SFTP: signed Tratta Sign documents already export nightly, and we can now issue an SFTP credential scoped to that folder so your team can collect them. Contact support to set this up.
• IVR follows your partial-payment rule: IVR payments now honor the organization's configured partial-payment setting, so IVR behaves the same way the rest of the platform does.

🔧 Maintenance, Bug Fixes, and Improvements

• Portal timestamps in your organization's timezone: consumer portal timestamps rendered in UTC, so a ticket opened late in the evening could appear to a consumer as the small hours of the next day. They now show in the organization timezone.
• Clearer permissions on customer details: a user without Notifications View saw an empty emails section that read as "no emails" rather than "not visible to you." The permission requirement is now shown.
• Ongoing technical updates and bug fixes to keep things fast, stable, and reliable.

Every item above is live now. Nothing to enable, and nothing to schedule.

If you want any of these walked through for your team, reach out to your Tratta contact. More updates are on the way. You can see the full list anytime at https://whatsnew.tratta.io/announcements 💫

🚫 ACH Block List: Stop Repeat Returns on Bad Bank Accounts

When an ACH payment comes back with a non-retriable return code, Tratta now blocks that bank account automatically, on the first qualifying return. The saved payment method is detached from the consumer, any active plan riding on it is broken, and further attempts are declined everywhere: Collect, guest checkout, agent payments in Console, and IVR. Nothing to switch on.

Blocks come in two scopes. Codes that mean the account itself is unusable (R02: Account Closed, R03: No Account, R04: Invalid Account Number Structure, and similar) block that routing and account number across every organization. Codes that mean the consumer has objected to the debit (R07: Authorization Revoked by Customer, R08: Payment Stopped, R10: Customer Advises Not Authorized, and similar) block it inside your organization only, so the same account still works elsewhere.

You can see and manage the list in Console > Settings > ACH blocklist.

Why this matters for debt collection:

• ACH cost control: every attempt against a dead account carries a return fee. Blocking on the first non-retriable return stops the second, third, and fourth.
• Return rate exposure: returns count against the thresholds your bank and the ACH network monitor. Blocking the account after the first non-retriable return stops repeat attempts from stacking up against those limits.
• Authorization integrity: once a consumer revokes authorization, no further debits go out on that account, in Collect, in Console, or over IVR. That is the record you want if the debit is ever challenged.
• Agent efficiency: the block reason sits in Console, so an agent can explain the decline on the call and an org admin can lift it without opening a ticket.
• Consumer experience: a blocked saved account drops out of the payment method picker, so the consumer picks another method instead of watching a payment fail at submission.

You can find more information about ACH block list in our docs.

🔑 Send a Password Reset from Console

When a consumer calls in locked out of the portal, an agent can send the reset email straight from Console. It goes out as the "Username found!" email, so it carries both their username and a password reset link, which covers the callers who cannot remember either one. The email address pre-fills from the consumer's profile, and the agent can correct or add an address and save it to the record in the same step. Access is permission based, so you decide which roles can send it.

Why this matters: a lockout is a high-volume, low-value interrupt on a staffed agent floor. Handling it inside the call, on the same screen, keeps the conversation on the balance instead of on account recovery.

🗺️ State-Specific Wording in Automated Campaigns

Campaign templates can now reference the consumer's address state, so a single template can carry state-specific language. If California requires your license number on messages to California consumers, condition that line on the state and let the template handle the rest. The same applies to state-mandated disclosures anywhere else you collect.

Why this matters: if you collect across state lines, disclosure language is a per-state obligation and template sprawl is how it gets missed. One template that reads the consumer's state is one artifact to review and approve, not fifty.

📋 Customer Updates Report Shows Exactly What Changed

The Customer Updates report has a new Updated Columns column listing the field names that changed on each row, for example "Address Line 1, Phone Number". Push just those fields into your system of record. You still get one row per consumer per day with same-day edits combined, and the column comes through on scheduled exports.

Why this matters: when you keep your own system of record, a change feed that names the changed fields is the difference between a targeted update and a full-record overwrite. Your developers write only what actually moved.

📄 Name Exported Files to Match Your System

In Console > Settings > Export file naming, pick which account attribute leads the filename on Tratta Sign documents and exported emails. Choose any account-level attribute, including account metadata and your external account number, and the rest of the pattern (template name, date, and time) stays in place so filenames stay unique. Set it once at the org level.

Why this matters: filenames are how documents get matched back to accounts in your system. Leading with your own account number removes the rename step between Tratta and wherever the file lands.

🧾 Print or Save a Receipt at Checkout

Consumers get a Print receipt button on every Collect confirmation page, covering one-time payments as a guest or signed in, scheduled charges, and payment plans. From the print dialog they can print or save a PDF.

Why this matters: a consumer who can produce their own proof of payment does not call an agent to get one. That request lands most often on the accounts your team can least afford to spend a call on.

🛠️ Minor Updates

• Routing number on the Scheduled Charges report: a new Routing column shows the full bank routing number on ACH payment methods. Filterable, and blank on card payments.
• Payment method last 4 on scheduled charges: a new Payment Method Last 4 column, off by default and switched on from column selection. It comes through in CSV exports too.
• Military state codes: AA, AE, and AP are selectable everywhere states appear in Console and Collect, including fee rules, so military addresses save cleanly and can be set as no-fee states.
• Variables in API campaign email subjects: the variables you already use in the email body now render in the subject line of API campaign emails.
• Ongoing technical updates and bug fixes 🐛

If you want any of these walked through for your team, reach out to your Tratta contact. More updates are on the way. You can see the full list anytime at https://whatsnew.tratta.io/announcements 💫

📊 A Redesigned Report Detail View

Opening a report in Console now lands you in a refreshed Report detail view. The layout has been rebuilt so large reports are easier to read and act on, with a cleaner structure that matches the new Console design. Filtering is much simpler too, so narrowing a report down to the accounts you care about takes fewer clicks.

Reports are where a lot of collection work happens, whether you are reviewing transactions, checking payment plans, or reconciling scheduled charges. A clearer report view means your agents and ops team spend less time hunting for the row or account they need, and more time acting on it.

🧩 Custom Metadata Columns in Reports

You can now add your own columns to the main transactional reports, mapped to any metadata property on your accounts. In Console > Settings > Report columns, choose a metadata property, give it any display name, and it appears on the report for everyone in your org. It is available on the Transactions, Payment Plans, and Scheduled charges reports to start. Effectively, any field you send us in your file can be surfaced as a column on these reports. Paired with the ability to rename report columns that we recently launched, you now have full control over the structure of your exported reports.

📈 SMS Campaign Metrics in the Dashboard

The Campaigns dashboard in Console now covers SMS alongside email, with dedicated SMS runs and SMS campaigns tabs. You get the same metrics you rely on for email: delivery and delivery rate, clicks, unsubscribes, total and verified sessions, sessions with payment, and dollars paid and promised, down to amount paid per SMS and sent-to-conversion rate. It is one place to see how your text outreach is performing, and how it stacks up against email at driving payments.

📨 Payment Portal Invitations Report

The new Payment portal invitations report gives you full visibility into the invites your agents send from Console: payment requests, payment plan requests, settlement requests, and document invites, across both SMS and email. See who sent what and when, group by agent to compare activity (for example, one agent sent 50 invitations in a day while another sent 10), and filter by type, channel, or account.

🧭 A Cleaner Console Layout

Console has a refreshed layout with a redesigned sidebar and top navigation bar, giving the whole app a cleaner, more modern look. The new sidebar also puts the Customer portal one click away, with a direct link so your team can jump straight into the consumer-facing experience.

🛠️ Minor Updates

• Audit Log user export now includes Last Active and Status: the monthly users CSV in Console > Audit Log now carries Last Active and Status (active or deactivated) columns, matching the User Management screen. Deactivated users are clearly distinguishable, which keeps the export dependable for compliance and exam reviews.
• More billing and account columns on transactional reports: the Transactions, Payment Plans, and Scheduled charges reports now support billing payer details (payer name and billing address) plus account balance and account number columns, with consistent naming across all three so your exports line up.

More updates are on the way. You can see the full list anytime at https://whatsnew.tratta.io/announcements 💫

✍️Tratta Sign: Cryptographic Certificate of Completion (PAdES)

Every completed Tratta Sign envelope now includes a Certificate of Completion with an embedded cryptographic signature that follows the PAdES standard (PDF Advanced Electronic Signatures, ETSI EN 319 142, aligned with eIDAS). The signature, signer certificate, and a trusted timestamp are baked into the PDF itself, so anyone can verify it in a standard PDF reader without pinging Tratta. Change a single byte after signing and verification fails immediately.

Why this matters for debt collection:

• Court defensibility: settlement agreements, payment authorizations, and hardship letters can be validated years later, even without an audit log from an eSign vendor. Long-Term Validation data is embedded, so the signature stays provable after certificates expire.
• CFPB and state exam readiness: examiners open the PDF in their own reader and confirm integrity independently. No dependency on a vendor portal that may be gone or paywalled.
• Portability: transferring servicing, selling paper, or handing files to counsel doesn't break provenance. The signed PDF stands on its own.
• Tamper evidence: a click log can be challenged. A cryptographically bound document cannot.

📄 Payment Auth PDFs to SFTP

Every Payment Authorization can now be exported as a PDF to your SFTP folder on a schedule. Compliance and audit archives land in your own systems automatically. Ask your Tratta account manager to enable it.

📊 Rename Report Columns Your Way

Every org has its own naming rules, and so does every downstream System of Record (SOR). If your SOR expects “AccountRefID” and Tratta defaults to “Account Number”, rename the Tratta column to match, in Console > Settings > Report columns. Set it once per report type and the new name follows everywhere: view, filter, group by, edit columns, search, and export. Reset a single column, or a whole report, any time.

💳 Collect: Smarter Payment Amount Validation on Custom Plans

Setting up a custom payment plan in Collect is smoother now. When consumers enter their own plan amount, live validation guides them toward valid values before they hit submit. Clearer errors, less back and forth, fewer abandoned checkouts.

📡 Real-time API Campaigns

Fire a Tratta campaign to a specific consumer the moment an event happens in your workflow (new account, missed payment, promise-to-pay follow-up, anything you build), no waiting for the next scheduled run. See the API docs on docs.tratta.io for the endpoint reference.

🛠️ Minor Updates

• Portal crawling toggle per org: each org can now decide whether to allow web crawlers to index their Tratta portal. Turn it off if you'd rather your consumer portal stays out of search results.
• Plans: last day of the month frequency: payment plans created from Console now support a “last day of the month” cadence, and the edge case around 30th vs 31st monthly plans (short months, February) is fixed. Charges land on the day you expect.

More updates on the way. Stay tuned! 💫

💸 Autopay (Open-Ended) Plans for Agents

Agents can now turn on Autopay right when creating a Payment Plan in Console. When an account balance can change in the future (interest, fees, or extra costs not yet reflected in the balance), agents can create an open-ended (Autopay) plan from Console > Create Payment Plan. These plans keep running until the account balance hits zero, so any future interest, fees, and costs are automatically covered.

Why it matters: balances do not always hold still. Once a judgment is entered, interest and costs keep accruing, so the amount a consumer agreed to pay is no longer the amount they owe. As one operations manager at a national creditor rights law firm told us: "We don't allow those files to make payment plans on the portal, because if judgment gets entered, then interest will start accruing, costs will be added to the file. So basically the balance of what the consumer is going to be paying is going to change." Open-ended Autopay plans cover that moving balance automatically, with no need to re-create the plan each time it changes. Just toggle “Autopay” when creating the plan, and that's it!

Help docs: Autopay (see the new "Creating an Autopay plan from Console" section).

💬 Contact Center: Templates and Auto-Assignment

• Message templates: save your most common replies and drop them into tickets in one click. Faster responses, consistent wording.

1. Just create your message templates in Settings > Contact Center:

2. and use them with ease on ticket replies:

• Auto-assign by account metadata: when a ticket comes in, it routes automatically to the agent whose email is listed on the account's metadata. The agent email acts as the identifier that ties the account to a Console user, so the right person picks it up without any manual triage. Faster first response, no hand-offs.

📬 Campaigns: Better Visibility

• Campaign run file name in Reports: every report row now shows the source file that triggered the campaign run. Tie outcomes back to the exact file you dropped, and audit results down to the upload level.
• SMS campaign columns in transaction reports: Transactions, Plans, and Scheduled Charges now carry SMS campaign columns alongside the existing Email ones. See which payments, plans, or schedules a consumer started from an SMS campaign link, and measure SMS performance next to Email. Multichannel outreach only pays off when you can attribute results, and now SMS sits side by side with Email on every report that matters.

• SMS Contact Tracker: every SMS interaction with a consumer (campaigns or payment requests), in one tab on the Customer page. Useful for engagement reviews and contact-attempt audits.

🔐 Stronger MFA on Console

Each organization can now enable Multi-Factor Authentication (MFA) on Console. Once turned on, every user in the org is prompted to link their account to an authenticator app (Google Authenticator, Microsoft Authenticator, Authy, or similar) and enter the rotating 6-digit code from that app on login. The code is generated on the user's device, rotates every 30 seconds, and never travels over email, so even if a password is leaked the login is still protected.

An important security step to keep your organization's data safe.

Help docs: Settings > Multi-factor Authentication.

🎨 Console Redesign: More Pages Refreshed

The new Console design now covers the Contact Center ticket page, the Dispute page, and a reordered account overview sections that puts the most-used info at the top.

🛠️ Other Improvements

• Tratta events as webhooks (API): subscribe to internal Tratta events via webhook and pipe them into your CRM, BI, or anywhere else in real time. See API docs > Tracking events for the available events and payloads.
• BIN blocker now on Console and IVR: the same live errors for blocked card networks and types that already run in Collect (Customer Portal) are now in place on Console and IVR card entry. Agents catch the issue right when the card is entered instead of waiting on a decline, and consumers calling IVR don't waste the call entering a card that was never going to work. Cleaner experience on both sides.

More updates on the way. You can see the full list anytime at https://whatsnew.tratta.io/announcements 💫

✍️ Tratta Sign: Ad Hoc Document Signing

Previously, Tratta Sign required setting up filters and templates to get documents signed at scale. Now agents can upload a signature-ready document on the fly and assign it to a specific debt account, right from Console.

Useful for one-off documents like settlement agreements, custom payment authorizations, hardship letters, or any account-specific paperwork that doesn't fit a reusable template.

How it works:

• Open the account page in Console and go to the new Signature Documents tab
• Upload your prepared document with the [Signature] placeholder (plus optional ones like [Sign Date] if needed)

• Send a portal invite email from the same section. The consumer follows the session link, reviews, and signs the document.

• Track status (new, viewed, signed) right on the account page, and across the org under Documents > Signed documents.

• Daily exports of signed documents to an SFTP folder are also available.

📚See our help documentation page with all the details.

🚀 Available now in Console. Go ahead and try it or contact us if you have any questions.

📝 Pop Up Authorization: Full Plan Schedule Variable

Pop Up Authorization templates now support a {{payment_schedule}} variable that renders the full plan schedule (each payment's date and amount). Plus an {{is_tiered_plan}} boolean flag so templates can conditionally show the full schedule for Tiered plans and a shorter summary for flat plans.

Helps you describe any plan structure accurately in authorization popups, especially for Tiered Payment Plans where first and last payment amounts no longer tell the full story.

Open your authorization templates and add {{payment_schedule}} to any tiered plan pop-ups.

🎨 Console Redesign: Chargeback & Batches

The Chargeback and Batches pages in Console have been refreshed with our new design system: cleaner layout, better readability. Continues the ongoing Console redesign (Customer, Account, Payment Plan, Transaction, and now Chargeback & Batches pages all shipped).

No action needed.

📊 Other updates

• Email Events now distinguishes unsubscribe scope: Transactional, Campaigns, or Both. Visible in your Email Events report.

💳 Default Payment Method per Checkout Type

Reduce card processing costs by steering consumers toward ACH on the checkouts where it makes sense. You can now choose which payment method (Card or Bank) is pre-selected by default per checkout type: Guest, Payment Plan, Partial Payment, Settlement, and Full Payment. Card stays the default unless you configure otherwise, and both methods remain available to consumers either way.

🚀 Reach out to your account manager to configure defaults for your organization.

🔗 Contact Center API

Contact Center ticket data is now accessible through API and webhooks. Sync tickets (account number, customer details, content, replies, status) into your CRM, collection system, or internal tools so your team can manage Tratta tickets from existing workflows.

Webhooks fire on ticket events to keep your system in sync in real time.

🚀 Available now. Check the API docs for more details.

📬 Email Campaigns Updates

• One-click unsubscribes (RFC 8058) added to campaign emails. Keeps deliverability strong with Gmail and other inboxes that enforce bulk sender requirements, while giving consumers a clearer opt-out path.
• Transactional email unsubscribes are now tracked in the Email Events report. See which consumers opted out of transactional emails and sync opt-outs with your system of record to keep lists clean.

📧 Contact Us form: custom request categories

Customize the Request Category dropdown on the Contact Us form. Add, edit, reorder, or remove categories per organization so consumers see options that match how your team triages tickets. Spanish translations are supported alongside English.

⚙️ Manage categories in Console > Settings.

🎨 Console Redesign: Transaction page

The Transaction page in Console has been refreshed with our new design system: cleaner layout and better readability.

We also added Checkout type, Checkout, Source, and Source name fields, so you can quickly identify the origin of any payment processed on Tratta (Portal or Agent side, which checkout was used, or which agent ran it).

More updates on the way.