Filter transactions by card type
We’ve added a binCardType filter to the transactions query endpoints. Use it to narrow card transactions by card type, accepting CREDIT, DEBIT, or PREPAID (case-insensitive). The filter supports the eq, ne, in, and nin operators.
This applies to List transactions for a paypoint and List transactions for an organization.
New payout_transaction_duplicated webhook event
We’ve added a new Pay Out webhook event, payout_transaction_duplicated, triggered when Payabli’s duplicate detection flags a payout transaction as a potential duplicate. The payload identifies the affected transactions (affectedIds, duplicateCount) along with the anomaly details (anomalyType, anomalyStatus, gateway, createdAt) and the paypoint and vendor.
See Pay Out Transaction Duplicated in the webhooks reference.
Payout capture-failure webhooks now carry a reason
When you use autoCapture, Payabli now emits a notification for every capture outcome, including internal validation failures that went unreported before. The capture-failure webhook events now include a Reason field describing why the capture didn’t succeed, alongside FundingSource and PaymentStatus.
Affected events
- Pay Out Transaction Declined
- Pay Out Transaction Technical Decline
- Pay Out Transaction Error
- Pay Out Transaction Rejected
Check payouts validate the remit address at authorization
For check payouts, Payabli now validates the vendor’s remit (mailing) address at authorization, before the payout is charged. If the address fails validation, Authorize a payout returns a 422 response and doesn’t charge the paypoint. Correct the address and re-authorize. Other payout methods (ACH, RTP, virtual card, wire, and managed payables) aren’t affected.
Query payouts response reference now matches the API
We’ve aligned the response reference and examples for the payout query endpoints with what the API returns. The reference now documents fields that were previously missing, corrects the Summary pageidentifier field name, and the examples reflect a real response.
Affected endpoints
Newly documented response fields
Corrections
- The Summary
pageidentifierfield is now documented with its correct all-lowercase name.