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
API updates
We’ve released several enhancements and bug fixes to our API. Here are the highlights:
Pay In
-
Added the ability to skip a subscription payment by setting
totalAmountto zero. See Pause a subscription or skip a payment for more details. -
Added the
expectedProcessingDateTimefield to the responses for these endpoints:- GET /MoneyIn/refund/{transId}/{amount}
- GET /MoneyIn/reverse/{transId}/{amount}
- POST /MoneyIn/refund/{transId}
When a paypoint has Enhanced Refund Flow enabled, the
expectedProcessingDateTimefield shows the date and time that a queued refund is expected to be processed.
Pay Out
Added the parentOrgId filter with (eq, neq, in, nin) operators to these endpoints:
- Query/batchesOut/{entry}
- Query/batchesOut/org/{orgId}
- Query/payouts/{entry}/{orgId}
- Query/payouts/org/{orgId}
- Query/bills/{entry}
- Query/bills/{entry}/org/{orgId}
- Query/vendors/{entry}
- Query/vendors/org/{orgId}
Pay Ops
- All instances of EIN values returned in API responses are now masked.
- Added a
UpdatedMerchantwebhook notification for paypoint updates. You can now get a notification when a paypoint’s address, banking information, or funding configuration is updated. See Webhook Notification Response Reference for the webhook payload. - Added the
ReplyByfield to responses from the Query/chargebacks endpoint. The ReplyBy field is the deadline by which a merchant must respond to a dispute. By default, this field is exactly 10 days after theCreatedAttimestamp, in UTC. - Added the
replyDatefilter to the Query/chargebacks endpoint which allows filtering disputes by deadline.replyDatehas the following conditions:(gt, ge, lt, le, eq, ne). See the Filters and Conditions Reference for more information.