Admin guide

Asset Discovery

Use Asset Discovery to create private ingestion candidates from source notes, contract data, token IDs, wallet evidence or manual asset metadata.

A candidate is not public and should not be treated as accepted.

• Record the source and search context.
• Add risk flags when rights, media or metadata are unclear.
• Use a conservative category until review is complete.

Import Candidates

Before importing, confirm source reliability, image rights, category, verification level, chain facts and public visibility. Only publish when the record is ready for visitors.

Do not mark a third-party record as Official or Self-issued unless EditionKey controls or officially issues it.

• Official or Self-issued status is justified.
• Description is factual and non-promotional.
• No fake owner, transaction hash, contract or metadata URI is entered.
• Visibility is intentional.

Registry Assets

Registry Assets are formal records. Keep names, issuer, creator, edition fields and display order consistent. Hidden assets can remain internal until source review is complete.

Manual Chain Sync

Use Chain Sync to record known chain fields and review timestamps. If a provider is unavailable or a record has not been minted, use Registry Only, Pending Mint, Not Minted, Not Synced or Sync Failed as appropriate.

• Verify the chain and contract before saving.
• Open explorer links before publishing them.
• Leave unknown fields blank.
• Record errors without exposing secrets.

Purchase-bound claim support

When a buyer asks about a claim email, search by Card ID, Certificate No., external order ID or masked purchase contact. Confirm the purchase-bound eligibility record before resending, correcting contact details, revoking after refund or retrying a transfer.

Resend invitations only to the original purchase email or phone unless a reviewed support correction has been recorded. Public Card pages intentionally do not send claim emails on demand.

If a link is expired, used or revoked, review the invitation history before issuing a new one. Each resend, contact correction, revocation and transfer retry must be auditable.

If the buyer entered the wrong wallet but transfer has not happened, follow the controlled correction flow. Once the NFT Certificate has moved to a personal wallet, EditionKey cannot move it again without that wallet's authorization.

• Check eligibility status, invitation status, send history and expiry.
• Use the original purchase contact for resend unless support correction is approved.
• Do not disclose full email, phone, claim token or private wallet details on public pages.
• Record refund, cancellation, contact correction, revocation and transfer retry actions in the audit trail.

Shop operations

Shop Theme creation defaults to shipping supported and self-pickup disabled. If self-pickup is enabled, an address is required before saving or publishing the theme.

Card Product publishing should check card images, price, edition quantity and signature details before making a physical-card SKU active.

Stripe webhook events, inventory locks, payment completion, shipment entry, pickup confirmation and refund-related actions must be idempotent or auditable. Payment success changes order payment status and inventory; shipment and pickup actions change fulfillment status only.

• Confirm self-pickup address before enabling pickup.
• Review front and back images, price, edition quantity and signature information.
• Record shipment carrier and tracking number for mailed orders.
• Mark pickup only after the paid pickup order is collected.
• Do not present the NFT Certificate as an investment product.