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
New getPaid tokenization setting and bug fixes
This release includes a new tokenization setting for the getPaid endpoint, as well as several bug fixes and enhancements across the web app, API, and embedded components. Here are the highlights:
Web app
Creator updates (beta)
- Removed erroneous console error messages
- Added copy button to color picker values in the editor
UI updates
- Added View Check button to the Bill Details screen for viewing check images
- Made navigation heading improvements
- General icon tweaks and enhancements
- Fixed several issues:
- Entering digits in Transaction report filters now works as expected
- Field display on boarding applications
- User status badge display
- 404 error when adding payment methods from customer records
- Date picker logic for operations with start/end dates
- Pagination in Residuals report
- Organizations report 500 error
Embedded components
- Fixed an issue that returned a 401 error when a customer tries to make multiple payments
API
New saveIfSuccess option
We’ve added a new option to the /getPaid endpoint that allows you to tokenize and save the payment method on any successfully authorized transaction with a card, device, or ACH payment method.
To tokenize a payment method while making a sale transaction, pass saveIfSuccess: true in the paymentMethod object. The new tokenized payment method will be returned in the response if the transaction is successful. If successful, the request returns the new method’s reference ID as methodReferenceId.
Other API fixes
- Fixed blank Billing & Fees column in exports
- Fixed 500 error when saving previously saved boarding applications
- Fixed Organizations query 500 error