> ## Documentation Index
> Fetch the complete documentation index at: https://developers.paylinedata.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Explicitly reissue unsigned access

> Replace an eligible predecessor once, preserving the same Application and merchant progress.

Reissue requires `applications:handoff:reissue` and fresh current authorization.
It can replace active, expired or explicitly revoked access on an eligible
unsigned, unfrozen Application. It creates a fresh 30-day grant on the same
Application and authoritative session; it does not revive the old URL or cookie.
Answers, protected records, pricing and documents remain intact.

## Prepare a deliberate replacement

First recover the [current handoff](https://developers.paylinedata.com/merchant-completion.md). Use its `handoff.id`
as `expectedHandoffId`. Generate and persist a **new UUID v4 for this reissue
operation**, then save the original body. The identifiers below are illustrative;
replace both before the first attempt and keep them unchanged for retries.

Save as `reissue.json`:

```json theme={null}
{
  "requestId": "6e037ebc-8094-4dc9-83e3-dcf3b9bb7505",
  "expectedHandoffId": "71a6b94b-e538-494f-a7cb-e61dbe9a9871"
}
```

```bash theme={null}
curl --silent --show-error --fail-with-body \
  --request POST "$PAYLINE_API_BASE/applications/$APPLICATION_ID/handoff/reissue" \
  --header "Authorization: Bearer $PAYLINE_API_KEY" \
  --header 'Content-Type: application/json' \
  --data-binary @reissue.json \
  --dump-header reissue-headers.txt --output reissue-response.json
```

This example passed the [identified Sandbox run](https://developers.paylinedata.com/index.md#example-verification).
Successful responses use `disposition: reissued` or `recovered`. Deliver only the
current usable URL through your approved merchant flow. Predecessor links, cookies and
delayed writes lose authority after replacement.

## Retry and eligibility boundaries

After response loss or `503 operation_unconfirmed`, back off and retry the same
operation ID and original body. Receipt identity includes environment, tenant,
stable caller, Application, operation and request ID. Changing the expected
predecessor under the same identity returns `request_conflict`. Competing new
operations on one predecessor return `handoff_changed` to the loser; reconcile
current state before deciding whether another deliberate replacement is needed.

Same-operation recovery returns the current handoff projection without renewing
expiry, including after later reissue or signing. Ordinary create retries and GETs
also never renew access.

Reissue denies archive, linked Merchant, ambiguous session authority, building or
active signing input, and accepted signing. Only canonical machine-created
`draft`/`in_progress` Applications qualify. `signing_input_locked`, `already_signed`
or `reissue_ineligible` must not trigger an automatic new ceremony. Failed artifact
finalization is not permission to reopen signed input.

Reissue bodies are limited to 1,024 UTF-8 bytes with an 8-second body-read deadline.
There is a separate limit of 30 attempts per stable caller per 60-second window.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.