Changelog

Changes for September 15, 2025

API changes

Enhanced transfer query response data

GET /query/transfers: Added parentOrgEntryName to the response. This field provides the entryname for the parent organization associated with the transfer.

New error code

Added a new 5004 error code “Invalid Service Fee value” that occurs when a service fee is less than zero. See 5000 codes for more information.

Enhanced chargeback response data

GET /ChargeBacks/read/{Id}: Added the ReplyBy field to the response. This is the date and time by which a response to the chargeback must be submitted. This field helps track chargeback response deadlines and manage dispute timelines more effectively.

Webhook notification changes

We’ve updated how Payabli handles webhook notification retries, and we’ve added new API endpoints to help you monitor and retry sending webhooks on your own, without having to contact Payabli support.

Changed retry behavior

We’ve updated webhook notification retry logic to resend failed notifications up to 2 times in 5-minute intervals instead of 5 times in 5-minute intervals.

New endpoints to support notification log searching and retries

We’ve added comprehensive notification logging and retry functionality to help manage webhook delivery and troubleshoot notification issues.

• POST /v2/notificationlogs: Search notification logs with filtering and pagination. Filter by date range (max 30 days), event type, success status, organization, and paypoint.
• GET /v2/notificationlogs/{uuid}: Get detailed information for a specific notification log entry, including request/response headers and content.
• GET /v2/notificationlogs/{uuid}/retry: Retry sending a specific notification.
• POST /v2/notificationlogs/retry: Bulk retry multiple notifications (maximum 50 IDs per request).

These new endpoints help provide:

• Comprehensive logging: Track notification delivery attempts, response status, success/failure, and timing information
• Detailed debugging: Access request and response headers, content, and error details for failed notifications
• Flexible retry options: Retry individual notifications or process up to 50 notifications in bulk
• Permission-based access: Requires notifications_create or notifications_read permissions

Documentation updates

As part of an ongoing effort to better align the documentation with the API, we’ve updated the chargeback response schema. These changes affect the documentation only—the API itself was already returning this data.

Enhanced chargeback query response documentation

GET /ChargeBacks/read/{Id}: Updated response schema documentation to accurately reflect the data structure returned by the API:

• Reorganized chargeback record fields to match actual API response structure
• Standardized field naming conventions (for example: id → Id, caseNumber → CaseNumber)
• Enhanced field documentation for better clarity
• Added comprehensive documentation for chargeback messages and additional metadata
• Updated examples to show realistic chargeback data with proper field values
• Added comprehensive sample responses demonstrating the full data structure
• Replaced placeholder values with actual data examples

We also enhanced chargeback records with additional organizational and integration data. These were already returned by the API, but weren’t documented yet:

• ParentOrgId: The ID of the parent organization
• ServiceGroup: Service group classification
• DisputeType: Type of dispute classification
• ProcessorName: Name of the payment processor
• messages: Array of chargeback-related messages with detailed message properties