Changelog

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 externalPaypointId to 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

February 24, 2025

New API fields

We’ve added several new fields to several endpoints.

Added the AchSecCode field to responses for the GET Query/transactions and GET MoneyIn/details/{transId} operations. SEC code is a three letter code that describes how an ACH payment was authorized. The Query/transactions endpoints also support filtering by AchSecCode and supports these operators: ct, nct, in, nin, eq, and ne.
Added a field that specifies what whether an accountholder is a person or a business to several request and response bodies. The field supports these values: personal and business.
Added the achHolderType field to the request bodies for the POST TokenStorage/add, POST Subscription/add, POST TokenStorage/update, and POST MoneyIn/getpaid endpoints.
Added AchHolderType field to the responses for the GET TokenStorage/{methodId}, GET Query/transactions and GET MoneyIn/details/{transId} endpoints.