Subscribe to our changelog RSS feed: https://docs.payabli.com/changelog.rss
2025
- April 2 Updates - New endpoint for downloading chargeback attachments
- March 3 Updates - New query parameters for export endpoints
- February 24 Updates - New API fields
- February 21 Updates - Improved error message for transaction amount limits
- February 5 Updates - API updates
- January 14 Updates - API updates
- January 1 Updates - Custom batch times and enhanced refund flow
2024
- December 29 Updates - Added
externalPaypointIdto boarding application endpoints - December 27 Updates - DeviceID added to API responses
- December 23 Updates - New query parameter
- November 26 Updates - New status page
- November 20 Updates - Improved error messages for managed payables
- November 19 Updates - New user language field in the API
- October 22 Updates - Playground, boarding and API enhancements
- October 10 Updates - Support for Apple Pay payments
- July 23 Updates - Enhanced batches and funding
- May 22 Updates - Bug fixes for web apps and APIs
- April 22 Updates - Chargeback notification enhancements and bug fixes
- March 20 Updates - Fixes to application statuses and transfer notifications
- March 6 Updates - Web app fixes and BIN data enhancements
- February 15 Updates - Boarding and UI enhancements
- January 31 Updates - Export, query, and boarding API enhancements
2023
- December 7 Updates - UI and reporting enhancements
- November 9 Updates - New split funding functionality
- October 20 Updates - Notes & Events, embedded components versioning, and numerous enhancements
- September 19 Updates - New getPaid tokenization setting and bug fixes
- August 24 Updates - Creator payments and improvements across apps
- August 1 Updates - Persistent Creator columns and API improvements
- July 26 Updates - Enhanced bill and invoice screens, Creator updates, and new webhook notifications
- June 29 Updates - Canadian postal codes, batch report enhancements, and webhook headers
- June 1 Updates - Batch report enhancements, and webhook headers
Chargeback notification enhancements and bug fixes
This release includes several bug fixes and enhancements across the web app, API, and embedded components. Here are the highlights:
Notifications
These changes impact notifications received via webhooks, SMS, and email.
We’ve added a new field to webhooks, email, and SMS notifications for new chargebacks and ACH returns. Now, when you have notifications enabled for new chargebacks or ACH returns, the notification includes the chargeback ID.
In the ReceivedChargeBack and ReceivedAchReturn webhook payloads, the ID is returned as chargebackID.
In email and SMS notifications, the field appears as Chargeback ID.
Web app
These changes impact PartnerHub, PayHub, or both.
- Fixed a bug that prevented customers from entering alphanumeric ZIP codes on mobile devices. Now, alphanumeric ZIP codes are supported on mobile Virtual Terminals, payment pages, embedded components and more.
- Fixed a bug that prevented header from being displayed on some new invoices. Headers now display as expected.
API
- Improved handling for special characters in fields related to ACH. Before, non-standard characters would cause the error “Narrative value is invalid”. Now, Payabli transliterates these values to accepted characters.
- Fixed an issue with transfer notification emails that caused reason messages to be cut off. Now, reason messages display as expected.
- Fixed an issue with bulk payment files that caused all custom field names to be changed to lowercase. Now, Payabli preserves the original capitalization.
- Fixed validation on some endpoints that caused them to return a 500 response instead of a 200 response with success details or a 400 response with error details. Affected endpoints now function as expected.
- Fixed an issue with the
MoneyOut/captureAll,MoneyOut/capture, andMoneyOut/cancelAllendpoints that prevented successful operations.