All Announcements

Default Payment Methods, Contact Center API, and One-Click Unsubscribes

New Feature
Improvement

💳 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.

image

⚙️ 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.

image

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.