Reissue payout
Reissues a payout transaction with a new payment method. This creates a new transaction linked to the original and marks the original transaction as reissued.
The original transaction must be in **Processing** or **Processed** status. The payment method in the request body is used directly. The endpoint doesn't fall back to vendor-managed payment methods.
The new transaction goes through the standard authorize-and-capture flow automatically. Both the original and new transactions are linked through their event histories for audit purposes.
Authentication
requestTokenstring
API Key authentication via header
Headers
idempotencyKey
Optional but recommended A unique ID that you can include to prevent duplicating objects or transactions in the case that a request is sent more than once. This key isn’t generated in Payabli, you must generate it yourself. This key persists for 2 minutes. After 2 minutes, you can reuse the key if needed.
Query parameters
transId
The transaction ID of the payout to reissue.
Request
This endpoint expects an object.
paymentMethod
Payment method for reissuing a payout transaction. The reissue endpoint uses the payment method details directly. It doesn’t fall back to the vendor’s managed payment method.
{ method: "vcard" }- Reissue as a virtual card{ method: "check" }- Reissue as a paper check{ method: "ach", achHolder: "...", achRouting: "...", achAccount: "...", achAccountType: "...", achHolderType: "..." }- Reissue as ACH with bank details
Response
Success
isSuccess
Boolean indicating whether the operation was successful. A true value indicates success. A false value indicates failure.
responseCode
Code for the response. Learn more in API Response Codes.
responseText
Response text for operation: ‘Success’ or ‘Declined’.
responseData
Errors
400
Bad Request Error
401
Unauthorized Error
403
Forbidden Error
500
Internal Server Error
503
Service Unavailable Error
