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.
The reissue request doesn’t accept a service fee. Payabli always charges the fee configured in the paypoint’s ACH payout pricing, even when the pricing allows fee overrides. The new transaction keeps the original payout’s total amount. The vendor receives that amount minus the configured fee.
Authentication
Bearer authentication of the form Bearer <token>, where token is your auth token.
Long-lived API token sent in the requestToken header. See API token authentication.
Headers
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
Request
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
Boolean indicating whether the operation was successful. A true value
indicates success. A false value indicates failure.
Code for the response. Learn more in API Response Codes.
Response text for operation: ‘Success’ or ‘Declined’.