How this fits in the Trade flow

• Called by the Integrating System
• Used after:
  • Token Registry is deployed
  • DNS configuration is validated
  • Required registry roles (e.g., MINTER) are assigned
• Requires explicit End User approval
• Approval happens only via redirect URL and End User passkeys

Without End User approval, the ePN is not issued.

The Integrating System should store the created ePN identifiers and registry references in its own backend (BlockPeer is infra-only).

What happens next

1. The Integrating System redirects the End User to redirectUrl
2. The End User reviews ePN issuance details
3. The End User approves issuance using passkeys
4. The ePN is issued and recorded under the Token Registry
5. The Integrating System stores the issued ePN details for future lifecycle actions

Important notes

• Issuance requires End User approval via redirect + passkeys
• Network transaction fees apply (paid by the End User-controlled account)
• BlockPeer does not store ePN business data or customer records
• The Integrating System remains the system of record

Common use cases

• Issuing trade promissory notes
• Creating receivable instruments
• Enabling trade finance or discounting workflows
• Digitising post-dated payment obligations

This API returns a redirect URL with sessionId to sign the transaction.
Use the GET endpoint /auth/session-response?sessionId=<sessionId> to retrieve the session result.
The response will include an object under the key wrappedDocument, which contains the content of the .tt file.

If using MCP, enter shipperDomain, holderAddress, and beneficiaryAddress explicitly.