Merchant completion and signing

Let the merchant complete, review and sign without manufacturing approval or consent.

Open the active handoff URL in the merchant’s browser through your approved delivery flow. The initial grant lasts 30 days. Treat the URL as a credential, separate from your API key. Avoid analytics, chat, logs and shared screenshots that capture its token. Revoking an API key does not revoke this URL.

Partial prefill leads to the remaining merchant inputs. Complete prefill still requires applicable documents, editable Review before signing freeze, consent and the Owner 1 signature. API-supplied signer information is unverified prefill; it is not evidence that the merchant opened, verified, reviewed or signed.

Protected information

Saved bank information displays masked values. During editable intake, the merchant can replace the complete bank group from scratch using the existing Bank/Review controls. Saved account numbers are never filled into replacement inputs. Replacement is not available after signing input is frozen. No additional Bank checkbox, full-number reveal or partner signing shortcut is required.

Recover an existing handoff

Using APPLICATION_ID from a successful creation:

curl --silent --show-error --fail-with-body \
  "$PAYLINE_API_BASE/applications/$APPLICATION_ID/handoff" \
  --header "Authorization: Bearer $PAYLINE_API_KEY" \
  --output handoff.json

Check handoff.state, handoff.url, expiresAt and purpose. The URL may be null when access is expired, revoked or unavailable. GET does not issue or renew access. After signing, recovery does not create another ceremony; a usable handoff has confirmation purpose. Do not convert finalization failure into a re-sign request.

Signing is separate from artifact completion

Signing acceptance is durable even if PDF finalization is pending or fails. Use status polling to distinguish those states and wait for immutable artifacts. Contact Payline with a safe support reference when recovery needs review; this API does not expose a finalization-retry operation.

All four pricing models remain supported. Known PDF pricing-field omissions do not mean pricing was rejected, and the API does not promise complete PDF mapping. Current pricing and immutable signed evidence are separate retrieval surfaces.