v4.1.2 Release

Leave a Comment
/
Platform Updates
/
By
Cody Eddings

SnapRefund v4.1.2 is Live

Sales Tax Visibility, Invoice API Improvements, Reliability Fixes

AgentSnap Updates ‍

Manual Entry for Date and State Fields

Date and state fields now accept typed entry in addition to picker and dropdown selection, while keeping existing validation so invalid values still cannot be submitted.

Payment Link Returned from Create Invoice

The AgentSnap public API’s Create Invoice endpoint now returns the same payment link emailed to the policyholder when no payment method is provided on a finalized invoice. Draft invoices continue to return a null payment URL.

Platform-Wide Updates ‍

Sales Tax Column in Transaction History

Transaction History now includes a Sales Tax column showing the correct amount per transaction across ClaimsSnap and AgentSnap, including in the exports that mirror that data.

Bug Fixes ‍

Recipient Phone Number for FedEx® Check Shipping

Choosing the FedEx® shipping method on the paper check Direct Payment address step now surfaces a required recipient phone number field, since expedited delivery requires one. Standard shipping methods hide the field.

Clearer Handling of Checks Not Yet Printed

Viewing a check PDF before the check has been printed no longer returns a server error. The interface now waits until the check is ready, and early requests return a clear not-ready response.

Bank Creation via Public API Key

Public API keys can now add a bank account through the documented bank creation endpoint instead of receiving a 403 Forbidden response.

Summary

Version 4.1.2 improves billing transparency and API ergonomics. Sales tax is now visible per transaction in Transaction History and the exports that mirror it, the AgentSnap Create Invoice endpoint returns the policyholder payment link directly, and date and state fields accept manual entry. Reliability fixes round out the release across paper check shipping, check PDF retrieval, and public API bank creation.

← Previous Post
No more post

Leave a Comment

Your email address will not be published. Required fields are marked *

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.